Fun run and charity walk WiFi: planning internet for registration, timing results and the finish village

What needs internet at a fun run or charity walk?

Most of the course can run without any network at all. The connected points are usually clustered around the start, the finish and the event village:

Timing is usually supplied by a specialist timing provider with its own equipment. The event network's job is to give that provider a reliable, separate connection for uploading results, not to replace their system. Our sporting event WiFi page covers the broader picture for community sport.

How many devices and how much bandwidth does a fun run need?

Plan from staff and fixed devices, not from total entrants. Spectators and runners mostly use their own mobile service. A worked example for a community run with on-the-day registration:

• Registration: 10 volunteers at 1.5 to 2 devices each, plus 4 printers, is about 19 to 24 devices.
• Start and finish: timing, announcer and 2 results screens, about 5 devices.
• Event village: 8 card terminals for merchandise, food and donations.
• Operations: 15 organiser and lead volunteer devices.

That is roughly 47 to 52 devices, which fits within about 50 devices per access point on paper. In practice registration and the finish line are often 100 metres or more apart, so plan at least one access point per zone. In open parkland, allow about 900 m² per access point.

Bandwidth is driven by the stream more than anything else. Each live stream needs 10 to 20 Mbps of stable upload, with 1.5 to 2 times that as headroom. Registration, results and payments together use very little, but they must not be slowed by the stream. Our bandwidth calculator can help with the totals.

Why is race morning the hardest part to plan for?

Fun runs concentrate almost all their network load into a short window:

1. Early bump-in. Summer events often start early to avoid the heat, so the network has to be installed and tested before registration opens, sometimes before sunrise.
2. Registration peak. Late entries, bib collection and name changes cluster in the 60 to 90 minutes before the start. Slow lookups at this point create long queues.
3. Start line surge. Thousands of participants post photos and start tracking apps at the same moment, which loads nearby mobile capacity. Devices relying on one phone hotspot often slow down right when they are needed.
4. Finish wave. Most participants finish within a short window, so results uploads, finish photos and village payments all peak together.

A practical approach is to give registration, timing and payments their own networks with a fixed or dedicated mobile connection, and to keep a second internet path ready. Our 4G and 5G router hire page explains how a separate mobile path is set up.

How should participant data and payments be protected?

Registration systems hold names, contact details, ages, emergency contacts and sometimes medical notes. The Office of the Australian Information Commissioner explains that health information is a type of sensitive information, and APP 11 describes the reasonable steps organisations covered by the Privacy Act should take to protect personal information from misuse, loss and unauthorised access.

• Keep registration and timing devices on a private network, never on an open guest network.
• Put card terminals on their own payment network, separate from volunteer phones and any public access. See EFTPOS payment networks.
• Follow the Australian Cyber Security Centre's basics: change default router passwords, use current WiFi security settings and update firmware before the event.
• Lock laptops when unattended and remove printed participant lists from desks at pack-down.

Our guide to separate networks for events explains how to split these uses.

Do checkpoints along the course need internet?

Usually not. Drink stations, turnaround points and marshal positions run on radios and mobile phones. A checkpoint needs its own connection only when it does something online:

• Intermediate timing points that publish split times live. The timing provider will normally specify what they need.
• Remote first aid or information tents that log incidents or look up participant details.
• Camera positions sending video back to the stream at the finish.

For these, a small mobile router at each point is simpler and safer than running cable along the course. Cables crossing paths used by runners are a trip hazard, so where cabling is needed in the event village, use cable ramps or route it overhead. For a stream camera on the course, a point-to-point wireless link back to the finish can work where there is clear line of sight.

What should organisers send when planning a fun run network?

1. A site map showing registration, the start and finish, the event village and any remote tents.
2. The run sheet, including bump-in time, registration opening, start times and expected finish window.
3. Expected entrants and whether there is on-the-day registration.
4. The number of payment points and any donation stations.
5. Whether you plan a live stream, and from which positions.
6. Power available at each zone.

You can send these details through our contact page and we will come back with a network plan for registration, timing upload, payments and streaming. For streaming specifically, see our live streaming internet service.

Sources

1. OAIC: What is personal information?
2. Office of the Australian Information Commissioner: Chapter 11, APP 11 Security of personal information
3. Australian Cyber Security Centre: Secure your Wi-Fi and router
4. business.gov.au: Choose payment methods

Event dates, prices and product details can change. Check the organiser or manufacturer before you plan around them. Planning figures are starting points; every network is confirmed against the actual site.