runlytics.app

What is Runlytics?

Runlytics is a free, browser-based running analytics tool that puts your race result into context. Instead of just showing your finish time, it compares your performance against a large database of official race results — the site says it analyzes over 1 million running performances — so you can see how you stack up against other runners in your category.

How it works

It is deliberately minimal. You enter three things: your age, your sex, and your race time. There is no name, email, or account required, and the analysis runs immediately. The output is a set of statistics intended to give you a more precise read on your result than a raw time or a generic age-graded calculator.

Who it's for

• Runners who have just finished a race and want to know whether that time was genuinely strong for their age and sex.
• People chasing a personal best who want a baseline to measure improvement against.
• Data-curious runners who enjoy percentile-style comparisons rather than simple pace numbers.

What it isn't

It is not a training platform, a GPS tracker, or a coaching service. There is no mention of training plans, workout logging, or device sync. It is a single-purpose comparison tool, and the site notes that additional features are planned for the future.

A practical next step

Have your most recent official race time handy, along with your age and sex, and run it through the tool. Then enter an older result from a year or two ago: seeing how your percentile position has shifted is often more motivating — and more honest — than comparing raw times across different courses and conditions.

If you want a second opinion on the same result, age-graded calculators from major race organizers, such as parkrun, offer a related but differently calculated perspective.

How does Runlytics compare my race time to other runners?

Runlytics compares your race time by having you enter three things: your age, sex and your race time. It then places that performance against a dataset drawn from official running races — the site describes analysing more than one million race performances — to show how you stack up against other runners. No name, email or sign-up is required to get the comparison, and the result is framed as analytics you "won't find anywhere else," with an invitation to return after a new personal best.

What the comparison is actually based on

The inputs are deliberately minimal: age, sex and time. That means the comparison is a demographic benchmark, not a like-for-like course comparison. Your result is being read against other runners in the same broad category, using real race results rather than self-reported training logs. For a runner who has just finished a local 10K and wants to know whether a 48-minute time is ordinary or strong for their age group, that is exactly the right question — and it is faster than digging through results pages yourself.

Where it fits in a runner's routine

• Post-race check: enter your time straight after a race, while the result still means something to you.
• Reality check on goals: if you are chasing a PB, seeing where the current time sits in the distribution tells you how much headroom exists.
• Age-group context: useful for masters runners whose times look slower in absolute terms but rank well within their bracket.

Trade-offs to keep in mind

A single age-sex-time input cannot account for course difficulty, weather, or how deep the field was. A hilly half marathon and a flat one produce very different times for the same fitness. So treat the output as a population benchmark, not a verdict on your training. If you want course-adjusted or field-relative analysis, you would need a tool that ingests the specific race — for example, official results pages from race organisers, or broader race-result archives such as Athlinks.

A practical next step

Run your most recent race time through Runlytics, note the percentile or comparison it gives you, then repeat with an older result from a year or two ago. The gap between the two is more informative than either number alone, because it shows direction of travel rather than a single snapshot.

Do I need to create an account or provide personal information to use Runlytics?

No account is needed. Runlytics is designed to work without a sign-up: you enter your age, sex and race time, and it runs the analysis from there. Its own page states that no name, email or sign-up is required for the core tool.

The only place an email comes up is optional: a "coming soon" list where you can be notified about new features. That is separate from using the running analytics, so you can skip it entirely.

What this means in practice

• For a quick check: You can compare a recent race result against other runners in a couple of minutes, with nothing stored about your identity.
• For repeat use: You would re-enter your details each time rather than logging in to a saved profile, since there is no account layer described.
• For privacy-minded runners: This is a low-commitment option, because the tool asks only for the attributes needed to make the comparison.

A useful next step

Have your most recent official race time and distance ready, along with your age and sex, then run one comparison. If you want to track progress over a season, keep your own simple log of race times and results, because the site as described does not maintain a personal history for you.

If you would rather have saved profiles and long-term tracking, a platform built around accounts may suit you better — for example Strava for logged activity history or Athlinks for official race results. Runlytics fits the opposite case: a fast, anonymous look at how your time stacks up.

What data sources does Runlytics use for its running analytics?

Runlytics says its analytics are built on data from official running races. On its home page it describes analyzing “1+ million running performances from official races” to generate stats about how you stack up against other runners. It does not name specific races, timing companies or governing bodies, so the exact source list is not visible from the page.

What you provide is different from what it analyzes. You enter only your age, sex and race time — no name, email or account — and Runlytics does the comparison against its race dataset. So the input is your result; the benchmark data is the official-race pool.

Practical check before trusting a percentile

• Ask which races and seasons are included. A pool skewed toward large, fast or local races will shift your percentile.
• Check whether the comparison group is filtered by age and sex, since that is all you supply.
• Re-run after a personal best to see whether the figure moves in a way you can explain.

If you want to verify the scope, use the site’s own “Learn more” or About section, or contact the operator, rather than assuming coverage of every race you have run. For a second opinion on how your time compares, Athlinks hosts official race results you can cross-check against.

Can Runlytics help me set realistic goals for my next race?

Yes, but indirectly: Runlytics is built to show where your current race time sits relative to other runners, which is exactly the kind of context you need to pick a realistic target time.

How it works

The site asks only for your age, sex and a race time — no name, email or sign-up. It then compares that performance against more than a million results from official running races to produce analytics.

Turning that into a goal

• Percentile context: If your recent time puts you in, say, the middle of your age and sex group, a target that jumps you far up the field is probably a multi-season project, not a next-race goal.
• Age-graded perspective: Comparing across age groups helps you judge whether a time is genuinely strong for your category or just looks fast in isolation.
• A concrete scenario: You ran a 10K in 52 minutes and want a spring half marathon target. Runlytics won't prescribe a training plan, but seeing how 52 minutes ranks for your age and sex tells you whether a sub-1:50 half is a stretch or a sensible first attempt.

Where it stops

Runlytics is an analytics and comparison tool, not a coach. It doesn't know your weekly mileage, injury history or how hilly your course is, so treat its output as one input into goal-setting rather than a verdict. Pair it with a plan or a coach for the training side.

Next step

Enter your most recent official race time, note the percentile it returns, then set a goal that moves you a modest, believable amount up that distribution — and re-check after your next race. The site also invites you to join an email list for upcoming features, which may add more goal-oriented tools later.

What new features are coming soon to Runlytics?

Runlytics doesn't say what the upcoming features are. Its homepage only has a "There's more…" section marked "⚡ Coming Soon!" with an email signup to be notified when new features are released. No feature names, dates or details are given.

If you want to know first, the practical step is to join that notification list — the page states no spam — and treat the announcement as the only reliable source. Until then, plan around what exists today: entering your age, sex and a race time, with no name, email or account required, to see how your result compares with a database of official race performances.

For context, other running-data services have moved toward features like race-result search, course-specific comparisons and training-load tracking. That's general industry direction, not a Runlytics roadmap. If those are what you're waiting for, check the site's own updates rather than assuming.