Rex says
Everyday utility math — the kind you'd otherwise pull up four browser tabs for. I keep it to one clean answer.
Try a scenario
Click to load — tweak from there.Inputs
Result
Projected finish (seconds)
5365.0
Ahead / behind PB (seconds)
-35.00
Projected finish (minutes)
89.42
Seconds off goal
25.0
Run progress vs PB total
34.1%
Psst — share this and help Rex grow
One click, a permanent link with your numbers baked in.
How to use this
- 1Enter current elapsed at split (sec).
- 2Enter pb time at that split (sec).
- 3Enter pb total time (sec).
- 4Enter goal time (sec).
- 5Read your projected finish (seconds) on the right — it updates as you type.
- 6Hit Share to keep the scenario or send it to someone.
About this calculator
Enter your elapsed time at a split, the PB time for that split, and your PB total to project where the current run finishes and how much time you're up or down.
Worked example
Using the values the calculator loads with:
Inputs
- Current elapsed at split: 1840 sec
- PB time at that split: 1875 sec
- PB total time: 5400 sec
- Goal time: 5340 sec
Results
- Projected finish (seconds): 5,365
- Ahead / behind PB (seconds): -35
- Projected finish (minutes): 89.42
- Seconds off goal: 25
- Run progress vs PB total: 34.1%
What each field means
Inputs
- Current elapsed at split (sec)
- The current elapsed at split used in the calculation, measured in sec. Starts at 1840 sec so you have a working example on load.
- PB time at that split (sec)
- The pb time at that split used in the calculation, measured in sec. Starts at 1875 sec so you have a working example on load.
- PB total time (sec)
- The pb total time used in the calculation, measured in sec. Starts at 5400 sec so you have a working example on load.
- Goal time (sec)
- The goal time used in the calculation, measured in sec. Starts at 5340 sec so you have a working example on load.
Results
- Projected finish (seconds)
- Returned as a decimal number and shown as the headline result. It recalculates instantly whenever you change an input, so you can compare scenarios without reloading.
- Ahead / behind PB (seconds)
- Returned as a decimal number. It recalculates instantly whenever you change an input, so you can compare scenarios without reloading.
- Projected finish (minutes)
- Returned as a decimal number. It recalculates instantly whenever you change an input, so you can compare scenarios without reloading.
- Seconds off goal
- Returned as a decimal number. It recalculates instantly whenever you change an input, so you can compare scenarios without reloading.
- Run progress vs PB total
- Returned as a percentage. It recalculates instantly whenever you change an input, so you can compare scenarios without reloading.
FAQ
Why is a linear projection wrong sometimes?
Time saves are not evenly distributed. A run that's up 30 seconds through an easy early section may give it all back in a hard late one.
Should I compare against best splits or PB splits?
PB splits for a realistic projection; sum-of-best for theoretical potential. They answer different questions.
Accuracy and limitations
- Estimates assume standard, average conditions — local rules, pricing, and materials vary.
- Results are rounded for readability; add a buffer before ordering, booking, or committing.
- Double-check anything with a real cost attached against a local quote.
Cite this calculator
Writing about this topic? Grab a citation — every link helps keep these tools free.
RevenueLab. (2026). Speedrun Pace & Split Calculator. Retrieved from https://www.revenuelab.fyi/toolbox/speedrun-pace
<p>Source: <a href="https://www.revenuelab.fyi/toolbox/speedrun-pace" target="_blank" rel="noopener">Speedrun Pace & Split Calculator — RevenueLab</a> (2026).</p>
Source: [Speedrun Pace & Split Calculator — RevenueLab](https://www.revenuelab.fyi/toolbox/speedrun-pace) (2026).