Race statistics & analysis
See what really happened this year, before you plan the next one
When an event ends, what the organizer is left with is usually impressions and anecdotes: more spectators this year, the water station was swamped mid-morning, a lot of medals left over. But when it is time to order stock or negotiate with a sponsor for next year, there is no number solid enough to quote.
The data has not gone anywhere — it is all there in the results. But getting a simple answer like when finishers peaked, or what share of entrants actually ran, means somebody building a spreadsheet, which in practice nobody ever gets round to. So next year is planned on impressions again.
Starters by distance, down to gender and age group, laid out so the whole event can be compared at a glance. You can see immediately which distance is the event’s core and which categories have enough runners to deserve their own prizes.
Split into finishers, withdrawals, disqualifications and no-shows. The no-show number is the one organizers use most, because it is the gap between what you ordered and what was actually used.
A graph by clock time showing how many crossed the line in each period. The peak is where the medal queue is longest, the water runs out fastest and the medical team works hardest — so next year you can position people and supplies around when runners actually arrive rather than when you expected them to.
Every distance has its fastest, slowest, median and average time, with a distribution showing where the field is bunched. These are the answers you need before the next edition: whether the road closure you requested was long enough, how many runners a given cut-off affects, and where the prize categories should be drawn.
Pick a distance, age group or gender and every chart on the page follows. Questions like when women in the mini marathon finished, or how long the over-60s took, are answered in two clicks instead of a request for a file and a wait.
Anyone with access to the event’s back office can open this page themselves, so the whole team works from the same numbers instead of passing several versions of a summary file round a chat group.
Actual starters by distance and category is the base for how many medals, meals, drinks and which sizes to allow for — rather than estimating from entries, which is always higher than the number who turn up.
The finisher peak tells you when to reinforce the medal zone, the water points and first aid, and when people can be released to help elsewhere.
The slowest time per distance with its distribution is direct evidence for a road-closure application, and lets you say in advance how many runners a tighter cut-off would affect.
The mix of distances, age groups, gender and nationality among the people who actually ran is a picture of your participants for the post-event report — your event’s own data, not a platform total.
Every year you have run with RunLah is in the same system, so you can open last year’s and see which distance runners moved to, which age groups grew, and whether the no-show rate came down.
Nothing to fill in. Every figure is calculated from the results the timing system recorded. If a result is corrected later, the statistics move with it, so there is no separate file to keep in sync.
Not currently, because the page reads per-runner times and statuses directly from RunLah’s timing system — which is why the statistics appear with nobody entering data. Events using our timing service get this page as part of it, with nothing extra to buy and nothing to connect.
This page answers questions about the race: who ran, who finished, when they crossed the line and how long they took. Information about entrants — province, shirt size, how they heard about the event — belongs to the registration side, which has its own statistics page.
Anyone in the system with no recorded time at any timing point across the whole event counts as a no-show, kept separate from those who withdrew mid-race and do have times at some points. The two groups are used for different planning, so they are not combined.
Tell the RunLah team and we will write an analysis from your event’s data and attach it to this page, where everyone on your team can read it. It is not produced automatically for every event, so please ask when you want one.
Yes — tell us what you intend to do with it and we will export per-runner results with splits as a file. It suits teams that already have someone who works with data.