Speedrun Time Save Calculator

Frequently Asked Questions

How is time save per split calculated?

Split delta = your split time − comparison (PB or best) split time. A negative delta means you saved that much time on that segment; summing deltas projects your final time.

How is the projected final time estimated?

Projected final = comparison final time + running sum of split deltas so far. If you are 4 seconds ahead at the last split, projected final is the PB minus roughly 4 seconds.

What is the difference from PB vs from world record?

Comparing to your personal best shows realistic improvement pace; comparing to the world record (or sum of best segments) shows the theoretical ceiling and where the biggest time is hiding.

What is "sum of best segments"?

It adds your fastest-ever time for each individual split, giving the best possible run if you nailed every segment in one attempt - usually well below any actual PB and a useful goal pace.

Provided by AllCalculators.io
Free online calculators for everyday. No registration required.

Estimates for informational purposes only.

Important Disclaimer: Estimates for informational purposes only.

This calculator provides estimates for informational purposes only. Results are based on assumptions and may not reflect actual outcomes. Consult qualified professionals in relevant fields before making important decisions based on these results.

JavaScript is required to use the interactive calculator above. The questions and answers below remain readable without JavaScript.

How This Calculator Works

A speedrun is a sequence of splits, and a run's quality is judged by how each split compares to a reference - a personal best (PB) or a world record. The difference at each split is a delta: negative means you were faster than the reference (time saved), positive means slower (time lost). This tool sums those per-split deltas to give the net time saved or lost across the whole run and, given the reference's final time, projects what your finishing time would be. It also separates the total saved from the total lost and flags your best and worst splits, so you can see exactly where a run was won or thrown away.

Formula / Method

Net delta = ∑(split delta), with the sign convention that negative = faster. Time saved = sum of all negative deltas; time lost = sum of all positive deltas; the net is their algebraic total. Projected final time = reference final time + net delta - so a −5.4 s net against a 30:45.6 PB projects to 30:40.2. Best split = the most negative delta; worst split = the most positive. Times are formatted as m:ss.cc, or h:mm:ss.cc for runs over an hour. Deltas are entered comma- or space-separated and any non-numeric entries are ignored, so a stray label will not crash the calculation.

Worked Example

Per-split deltas of −2.4, +1.1, −0.8, +3.2, −5.5 seconds against a PB of 1845.6 s (30:45.60). Net = −2.4 + 1.1 − 0.8 + 3.2 − 5.5 = −4.4 s, so the run is 4.4 seconds ahead overall. Total saved = −2.4 − 0.8 − 5.5 = −8.7 s; total lost = +1.1 + 3.2 = +4.3 s. Projected finish = 1845.6 − 4.4 = 1841.2 s = 30:41.20, a new PB by 4.4 seconds. The worst split (+3.2) is the obvious place to look for improvement even though the run still finished ahead.

Common Mistakes

Getting the sign backwards - in most timers a green/negative delta means time saved; enter saved time as negative here.

Mixing cumulative split times with per-segment deltas - this tool expects the gain or loss at each split, not the running total.

Reading "sum of best segments" as an achievable goal - it is a theoretical floor rarely hit in one run.

Comparing against world record when your route differs - deltas only make sense versus a comparable reference run.

Forgetting load-time or in-game-time differences; mixing timing methods skews every delta.

Tips & FAQ

Where should I practise? Look at the worst (most positive) split and the largest variance between attempts - that is where the most time is realistically available, far more than shaving an already-tight segment that is near its theoretical best. A split you lose three seconds on inconsistently is a better training target than one you could optimise by a tenth. Why is my net positive even with great splits? One disastrous segment can outweigh several small saves; the algebraic sum is what matters, not the count of green splits, which is why a single big mistake can sink an otherwise excellent run. What is "sum of best"? Add the best delta you have ever recorded for each split individually - it is the theoretical perfect-run ceiling assuming every segment goes optimally at once, a motivating target rather than a realistic expectation. Should I reset on a bad early split? Only if recovery is genuinely unrealistic; feed your running deltas in here to see whether plausible later saves can still erase an early loss before you abandon a run that might actually be salvageable. Should I compare to PB or world record? Compare to a reference that uses the same route and timing method - delta against a faster but different strategy is meaningless, so pace against a run you could actually reproduce. How do I handle a sub-split skip? If a strategy removes a split entirely, enter the saved time as one negative delta for that section rather than trying to map it onto the old split layout.

Speedrun Time Save Calculator

Frequently Asked Questions

Related Gaming Calculators