Jog-a-thon lap counter
Totals
Counts and names are saved only in this browser on this device, so a refresh doesn't lose them. Nothing is sent anywhere. Use one device per counting lane, and keep a paper backup at the checkpoint.
Quick answer. Open this jog-a-thon lap counter on a phone or tablet, enter the runner numbers your lane covers (up to 200), and tap a number each time that runner crosses. A repeat-tap guard ignores a second tap on the same runner within a set number of seconds, so double taps don't inflate counts. When the wave ends, copy the totals as CSV or print them.
How to use the jog-a-thon lap counter
This jog-a-thon lap counter turns any phone or tablet into a tap-to-count board. Nothing to install, no account. Set it up before runners arrive, then tap a number every time that runner crosses your line.
- Set your number range. Enter the first and last runner numbers this device will count. One device handles up to 200 numbers. If your range is longer, the counter shows the first 200 and tells you which numbers to set up on a second device.
- Add names if you want them. One name per line, in number order. The first line goes with the first number, the second line with the next, and so on, so a blank line shifts every name after it.
- Set the repeat-tap guard. A second tap on the same runner within this many seconds is ignored and flagged on screen. The default is 45 seconds.
- Tap as runners cross. Each button shows the runner's number and lap count. Undo last tap removes the most recent lap recorded on this device, whichever runner it was, and you can press it more than once.
- Watch the totals. Runners with laps, total laps, most laps, and crossings in the last minute update as you go.
- Get the results out. Copy totals (CSV) puts every number, name and lap count on the clipboard for a spreadsheet. Download CSV saves the same file, which helps when the browser blocks copying, and Print totals gives you a clean table. Start over asks for a second tap, then clears laps and names. It keeps your number range and guard.
Counts are saved in that browser after every tap, so an accidental refresh doesn't wipe the heat. Nothing leaves the device. Lock the number range before the first runner starts: laps tapped for numbers you later remove from the range drop out of the CSV and printout.
When a lap counter app beats lap cards, and when it doesn't
A tap counter shines when exact per-runner laps matter and runners can be told apart at a glance. Our jog-a-thon lap counting methods guide compares every option; here is the short version.
| Tap-counting works well | Stick with paper |
|---|---|
| Grades 3 and up, who can wear a bib and hold a lane | K–2, where numbers get covered, swapped or lost |
| Numbered bibs big enough to read from a few meters away | No bibs, or numbers only on a card in a pocket |
| Per-lap pledges, where every lap is money and totals must reach the pledge sheet fast | Flat-donation events where a rough count is fine |
| Lanes of a manageable size, one counter per lane | One huge wave funneling past a single table |
The big win is the end of the day. Instead of volunteers counting punches on hundreds of cards, each device hands you a finished list. The math for setting rates is in the pledge rate planner.
Setting the repeat-tap guard from your fastest lap
The guard catches a thumb that lands twice, or two volunteers tapping the same kid. It must be shorter than your fastest realistic lap, or it will throw away real laps. A good rule: no more than about half of the fastest lap time.
Get the fastest lap from the jog-a-thon lap calculator: pick your lap length and age group, and use the high pace. Lap minutes = lap length ÷ high pace.
Worked example: a 400 m track and a grades 3–5 wave. At the calculator's high pace of 150 m a minute, the fastest lap is 400 ÷ 150 ≈ 2.7 minutes, about 160 seconds. A guard of 60 to 90 seconds is safe: it can't block a real lap, and it still catches every double tap.
| Course and group | Fastest lap (high pace) | Suggested guard |
|---|---|---|
| 400 m track, K–2 (120 m/min) | about 200 s | 60–100 s |
| 400 m track, grades 3–5 (150 m/min) | about 160 s | 60–80 s |
| 400 m track, high school/adult (190 m/min) | about 126 s | 45–60 s |
| 200 m loop, high school/adult (190 m/min) | about 63 s | 20–30 s |
On a short loop with fast older runners, the 45-second default is too long and will discard real laps. Lower it before the heat starts, and treat any "ignored" message for a strong runner as a sign the guard needs to come down.
One device per counting lane
Give every counting lane its own device and its own number block: lane 1 counts 1–60, lane 2 counts 61–120, and so on. Assign bib numbers by lane so no runner's number lives on another lane's phone. The course setup guide shows where a laned chute fits on your field.
- One counter per browser. The tool saves to the browser it runs in. Don't open it in two tabs on the same phone; the tabs will overwrite each other.
- Use the crossings-per-minute stat. If one lane keeps showing more crossings than its counter can calmly handle, split that lane's numbers onto a second device for the next wave. The wave planner helps you size waves so this doesn't happen.
- Save before you clear. Copy or print totals, then Start over for the next wave.
Event-day habits for anyone who will count laps on a phone
- Keep a paper backup. Phones die and crack. Run lap cards or a tally sheet alongside, at least the first year. The printable lap cards and pledge sheets are sized for this.
- Charge everything. Start at a full battery, bring a power bank, and turn screen brightness up for outdoor glare.
- Stop the screen from locking. Lengthen auto-lock in the device settings so the board stays up between crossings.
- Load the page before you walk out. Tapping works without a signal once the page is open, but reloading needs one.
- Use a regular browser window. Private or incognito windows may block saving, and then a refresh loses the counts.
- Numbers, not full names. For privacy, leave names blank or use first name and last initial. On a volunteer's personal phone, copy the totals to the organizer and then clear them with Start over.
Merging totals from several devices into one jogathon lap tracker
Each device copies a CSV with five columns: runner_number, name, laps, first_tap and last_tap. The two tap times come from the device clock and help settle a disputed count: a first tap before the heat started or a last tap after it ended points to a mistyped number. To build one master list:
- Paste the first device's CSV into a blank spreadsheet. If it lands in one column, split it on commas.
- Paste each other device's totals underneath and delete the repeated header rows.
- If lanes had separate number blocks, sort by runner_number and you're done. If a runner could appear on two devices, add a summary column with SUMIF on runner_number, or use a pivot table that sums laps by runner.
- Look up each runner's laps against your pledge records to calculate what every donor owes. Our guide to collecting jog-a-thon pledges picks up from there.
Every free planner is on our tools page, and the full event walkthrough lives in our complete jog-a-thon guide.
Frequently asked questions
Can I count jog-a-thon laps on my phone?
Yes. Open the lap counter in your phone's browser, set the runner numbers you are covering, and tap a number each time that runner crosses. Counts save in the browser after every tap, and you can copy the totals as CSV or print them when the wave ends.
Is there a free lap counting app for a fun run?
This lap counter is free and runs in any phone or tablet browser with nothing to install and no account. It handles up to 200 runner numbers per device, so larger events use one device per counting lane.
What happens if I tap the same runner twice by mistake?
If the second tap lands inside the repeat-tap guard window, the counter ignores it and shows a message. If it gets through anyway, press Undo last tap, which removes the most recent lap recorded on that device.
Will I lose my lap counts if the page refreshes?
No, as long as you use a regular browser window. Counts are saved in that browser after every tap. Private or incognito windows may block saving, so avoid them on event day and keep a paper backup.
How many lap counters do I need for a jog-a-thon?
Plan one device and one volunteer per counting lane, with each lane sized so its crossings per minute stay manageable. The lap calculator works out counters needed from your runners, loop length and age group.