Speedrun Timer Calculator

Track splits, calculate time saves, and analyze your speedrun pace.

Time Comparison

Add Split

Current Pace

+4:15
Ahead of target

Split Analysis

Intro
4:50 / 5:00
+0:10
Level 1
10:15 / 10:00
-0:15
Boss 1
2:50 / 3:00
+0:10

Statistics

Total Time Save
+0:05
Gold Time
17:40

What Is a Speedrun Timer Calculator?

A speedrun timer calculator is an essential tool for competitive gamers who want to beat a game as fast as possible. Speedrunning has evolved from a niche hobby into a globally recognized competitive discipline tracked on leaderboards like Speedrun.com, with players competing in categories ranging from Any% to 100% completion. To improve, runners need precise data — not just a stopwatch, but a system that breaks a run into individual splits, compares each segment against a personal best (PB) or world record (WR) pace, and calculates the cumulative time delta at every checkpoint.

This calculator lets you enter a target/PB time and a current run time, then instantly shows whether you are ahead of or behind your goal. The difference field uses the formula targetSeconds − currentSeconds: a positive value means you are ahead, a negative value means you are behind. The color-coded result — green for ahead, red for behind — gives runners at-a-glance feedback without needing to do mental arithmetic mid-run.

Beyond the simple time comparison, the tool supports a full split analysis panel. Each split (a named segment of the run, such as "Intro", "Level 1", or "Boss 1") stores a target duration and an actual duration, both in seconds. The per-split difference and running cumulative difference are calculated automatically, so you always know where you lost time and where you saved it. This is exactly the workflow used by professional tools like LiveSplit, which is the industry-standard split timer for PC speedrunners.

Whether you are new to speedrunning and want to understand how split timers work, or you are an experienced runner planning a routing strategy offline, this speedrun timer calculator gives you the data you need in a clean, no-install web interface.

Speedrun Timer Formulas Explained

Every number the calculator displays comes from a small set of formulas. Understanding them helps you interpret the results and decide where to focus your practice.

Time Conversion

All times are stored internally as total seconds to make arithmetic simple:

totalSeconds = hours × 3600 + minutes × 60 + seconds

For example, a target time of 1 h 30 m 0 s converts to 1 × 3600 + 30 × 60 + 0 = 5400 seconds.

Pace Percentage

The pace percentage tells you how your current-run speed compares to your target pace:

pace (%) = (targetSeconds ÷ currentSeconds) × 100

A pace above 100% means you are on track to beat the target; below 100% means you are slower than needed.

Gold Potential

Gold splits represent the fastest you have ever completed each individual segment. The gold potential — the theoretical best time you could achieve if you hit every personal-best split — is calculated as:

goldPotential = Σ min(split.target, split.actual)

This sum represents a lower bound on your achievable final time if every segment were run at its recorded best.

Speedrun Core Formulas

difference = targetSeconds − currentSeconds; totalTimeSave = Σ(split.target − split.actual); goldPotential = Σ min(split.target, split.actual); pace% = (targetSeconds ÷ currentSeconds) × 100

Where:

  • targetSeconds= Target/PB time converted to total seconds (hours×3600 + minutes×60 + seconds)
  • currentSeconds= Current run time converted to total seconds
  • difference= Time delta vs target; positive = ahead, negative = behind
  • split.target= Expected duration of a named segment, in seconds
  • split.actual= Actual recorded duration of a named segment, in seconds
  • totalTimeSave= Sum of all per-split differences; net time gained or lost across all splits
  • goldPotential= Sum of the minimum (target, actual) for each split — theoretical best time
  • pace%= Ratio of target to current time, expressed as a percentage

How to Use Split Analysis for Speedrunning

Split analysis is the backbone of meaningful speedrun improvement. A split divides the full run into named checkpoints — common examples include game zones, boss fights, loading screens, or any repeatable landmark you can identify in real time. For each split you record a target time (your goal for that segment) and an actual time (how long the segment really took, in seconds).

The calculator processes each split to produce four key values:

  • Split difference: target − actual. Positive means you were faster than planned on that segment; negative means you were slower.
  • Cumulative actual time: the running total of all actual segment durations so far.
  • Cumulative difference: the running total of all per-split differences, equivalent to Σ(target − actual) up to and including that split. This is the most important number during a live run — it tells you your overall position relative to the target at every checkpoint.
  • Total time save: the cumulative difference for all splits combined. A positive number means your splits were collectively faster than target; negative means slower.

To get the most from split analysis, break your game into 8–15 segments. Too few splits and you cannot identify which part of the game is costing you time. Too many and the overhead of reading split data during a run becomes distracting. Most runners organize splits around natural boundaries: level transitions, boss kills, or menu screens.

Once you identify a consistently negative split — a segment where your actual time repeatedly exceeds the target — that segment becomes a training priority. Focused practice on individual segments (called segment grinding) is far more efficient than repeatedly running the full game.

Gold Splits and Total Time Save

Two statistics the speedrun timer calculator highlights deserve special attention: gold splits and total time save.

Gold Splits

In speedrunning terminology, a gold split is the fastest time ever recorded for a single segment, across all of a runner's attempts. The gold potential displayed by this calculator is computed as the sum of the minimum of (target time, actual time) for every split you have entered. If your actual time on a split was faster than your target, the actual time is the gold candidate; if the target was faster, that target becomes the benchmark. The resulting total represents the theoretical best final time you could achieve if every segment were completed at its personal-best pace — sometimes called Sum of Best Segments (SoB) in the speedrunning community.

Understanding the gap between your current PB and your gold potential tells you how much time is theoretically available. If your PB is 1:30:00 and your Sum of Best is 1:24:30, there are approximately 5.5 minutes of time save still reachable with perfect execution.

Total Time Save

Total time save is the sum of all individual split differences: Σ(target − actual). A positive total means your splits were collectively faster than planned; a negative total means you are behind target pace. Tracking this value across many runs reveals whether your overall execution is improving, even when individual runs end prematurely. Runners often use this to set intermediate goals — for example, targeting a 30-second total time save improvement before attempting a full PB run.

Both metrics together give a complete picture of performance: gold potential shows the ceiling, and total time save shows how close to that ceiling your current run is reaching.

Understanding Pace Percentage and Target Time

The pace percentage is a normalized way to compare run speed against a target, independent of how much of the run remains. The formula is (targetSeconds ÷ currentSeconds) × 100. When pace equals exactly 100%, your current-run time matches your target time precisely. Values above 100% indicate you are running faster than the target (ahead of pace); values below 100% indicate you are running slower (behind pace).

For example: if your target is 5400 seconds and your current run reads 5145 seconds, pace = (5400 ÷ 5145) × 100 ≈ 104.96%, meaning you are running roughly 5% faster than the target at that moment.

The target time input is flexible. You can use it as:

  • Your personal best (PB) — to track whether a run has PB potential in real time.
  • A world record (WR) — to see how far behind the top pace you are running.
  • A category record — useful for runners competing in sub-categories like glitchless, low%, or specific platform runs.
  • A training milestone — set a challenging but realistic goal as a waypoint toward a longer-term target.

Switching the target between these reference points while keeping your split data unchanged lets you instantly re-frame the same run data against different benchmarks — a powerful way to gauge improvement without re-entering all your split information.

Accurate pace tracking is especially valuable in long games (RPGs, open-world titles) where a single bad segment might cost 10–15 minutes. Knowing your pace percentage early in the run helps you decide whether to reset and start over or continue in hopes of recovering the time through exceptional later segments.

Speedrunning Categories and Strategy Tips

Speedrunning is not monolithic — dozens of categories exist for most games, each with distinct rules and optimal strategies. Understanding these categories helps you configure the speedrun timer calculator most effectively.

Common Speedrun Categories

Category Definition Typical Split Focus
Any% Reach the credits as fast as possible, any means allowed Glitch entry points, skip triggers
100% Complete all objectives, collectibles, or achievements Collection zones, completion checks
Glitchless No out-of-bounds, wrong warps, or unintended exploits Optimal movement, menu navigation
Low% Finish with minimum items, pickups, or actions Avoidance routing, RNG manipulation

For multi-segment games, align your splits with the boundaries that matter most in the category you are running. In Any% categories, splits often sit right before and after known glitches so you can quickly identify whether the glitch attempt succeeded. In 100% categories, splits often correspond to major collection milestones.

Use the cumulative difference to make reset decisions: if you fall behind your target pace by more than a threshold you set in advance (say, 30 seconds in a 90-minute run), it is usually more efficient to reset and start a fresh attempt rather than finishing a run that cannot realistically achieve your goal time.

Worked Examples

Basic Ahead-of-Pace Calculation

Problem:

Your target (PB) time is 1 hour 30 minutes 0 seconds. Your current run reads 1 hour 25 minutes 45 seconds. Are you ahead or behind, and by how much?

Solution Steps:

  1. 1Convert target to seconds: 1 × 3600 + 30 × 60 + 0 = 5400 s
  2. 2Convert current to seconds: 1 × 3600 + 25 × 60 + 45 = 3600 + 1500 + 45 = 5145 s
  3. 3Calculate difference: 5400 − 5145 = +255 s
  4. 4Format +255 s: 255 ÷ 60 = 4 min 15 s → displayed as +4:15
  5. 5Since difference is positive, you are AHEAD of target pace by 4 minutes 15 seconds

Result:

+4:15 ahead of target (difference = +255 seconds)

Three-Split Total Time Save

Problem:

You have three splits: Intro (target 300 s, actual 290 s), Level 1 (target 600 s, actual 615 s), Boss 1 (target 180 s, actual 170 s). What is the total time save?

Solution Steps:

  1. 1Intro split difference: 300 − 290 = +10 s (ahead)
  2. 2Level 1 split difference: 600 − 615 = −15 s (behind)
  3. 3Boss 1 split difference: 180 − 170 = +10 s (ahead)
  4. 4Total target splits: 300 + 600 + 180 = 1080 s
  5. 5Total actual splits: 290 + 615 + 170 = 1075 s
  6. 6Total time save: 1080 − 1075 = +5 s (net 5 seconds ahead)

Result:

Total time save = +5 seconds; cumulative difference after all splits is +5 s

Gold Potential (Sum of Best Segments)

Problem:

Using the same three splits above — Intro (target 300 s, actual 290 s), Level 1 (target 600 s, actual 615 s), Boss 1 (target 180 s, actual 170 s) — what is the gold potential (Sum of Best)?

Solution Steps:

  1. 1Intro: min(300, 290) = 290 s (actual was faster)
  2. 2Level 1: min(600, 615) = 600 s (target was faster)
  3. 3Boss 1: min(180, 170) = 170 s (actual was faster)
  4. 4Gold potential = 290 + 600 + 170 = 1060 s
  5. 5Convert: 1060 ÷ 60 = 17 min 40 s → 17:40

Result:

Gold potential = 1060 seconds (17:40) — the theoretical best time across these three segments

Pace Percentage Calculation

Problem:

Target is 5400 s, current run is 5145 s. What is the pace percentage?

Solution Steps:

  1. 1Apply formula: pace% = (targetSeconds ÷ currentSeconds) × 100
  2. 2pace% = (5400 ÷ 5145) × 100
  3. 35400 ÷ 5145 ≈ 1.04956
  4. 41.04956 × 100 ≈ 104.96%
  5. 5Pace above 100% means you are running faster than target pace

Result:

Pace ≈ 104.96% — approximately 5% faster than the target, indicating a run with PB potential

Tips & Best Practices

  • Set your target time to the current world record for your category to see exactly how far behind WR pace your splits are.
  • Enter split times in seconds — convert minutes to seconds by multiplying by 60 before adding remaining seconds.
  • Focus practice on splits with the largest negative difference first; those segments are costing you the most time.
  • Use gold potential as a long-term goal, not a short-term expectation — a single run that matches Sum of Best on every split is extremely rare.
  • Set a reset threshold before starting a run, not during it, to avoid biased decisions under pressure.
  • Track cumulative difference after each major split to make run-continuation decisions early rather than 80% into a lost run.
  • Align split checkpoints with game loading screens or cutscenes — these are consistent, easy-to-identify boundaries that reduce timing error.
  • If your pace percentage is consistently 95–99%, you are close to target — small movement optimizations or menu routing improvements are often enough to close the gap.
  • Review your split data across multiple runs to find systematic losses — a segment that is always 5–10 seconds slow every attempt is a strong candidate for isolated segment grinding.

Frequently Asked Questions

The terms are often used interchangeably in the community, but technically a <em>segment</em> is the portion of the run between two split points, while a <em>split</em> is the timestamp or duration recorded at a checkpoint. In this calculator, splits store a segment name and that segment's duration in seconds — both target and actual. Most modern split timers (LiveSplit, wsplit) use the same convention.
It means your current run time is less than your target time at this point in the run, so you are on pace to beat the target if you maintain your current speed. The calculator computes <em>difference = targetSeconds − currentSeconds</em>; a positive result displayed in green means you are ahead. The larger the positive number, the more buffer time you have.
Your personal best (PB) is a real, completed run time. Gold potential — also called Sum of Best Segments — is a theoretical lower bound constructed by taking the fastest time you have ever recorded for each individual segment and adding them together. It is almost always faster than your PB because achieving every personal-best split in a single run requires nearly flawless execution. The gap between PB and gold potential shows how much improvement is theoretically still available.
Split placement depends on the game and category. A common guideline is to place splits at natural, easily identifiable boundaries — level loads, boss deaths, cutscene transitions — and to aim for 8–15 total splits for a typical 60–120 minute run. Fewer splits make it harder to isolate problem areas; more splits create information overload during a live run. For categories with a handful of major glitch attempts, placing splits around each glitch attempt is especially useful so you know instantly if the attempt succeeded.
A reset threshold is a maximum time-behind-pace that you decide in advance will trigger a run reset rather than a continuation. For example, if your goal is a 1:30:00 finish and you set a 30-second threshold, you reset any run where the cumulative split difference falls below −30 s. Setting this threshold before you start prevents emotional, in-the-moment decisions that often lead to wasted time finishing unrecoverable runs. Most seasoned speedrunners tighten their reset threshold as their PB improves.
This web-based speedrun timer calculator is designed primarily for planning, practice analysis, and offline calculation. For live splits during an actual run you would use dedicated desktop software such as LiveSplit, which overlays on your capture or monitor. However, this calculator is excellent for setting target split times before a run, reviewing past runs by entering your recorded segment times, or comparing two routing strategies side by side.
Any% allows all in-game techniques including glitches, out-of-bounds movement, wrong warps, and other unintended mechanics — the only goal is to reach the end credits as fast as possible. Glitchless restricts runners to intended gameplay mechanics only, resulting in longer but more approachable runs. Both categories use split timers and the same mathematical framework; the difference is purely in the routing and what techniques are legal.

Sources & References

Last updated: 2026-06-05

💡

Help us improve!

How would you rate the Speedrun Timer Calculator?

<>

Editorial Note

MyCalcBuddy Editorial Team

This page is maintained as an educational calculator reference.

Source

Formula Source: Standard Mathematical References

by Various

UpdatedLast reviewed: May 2026
CheckedFormula checks are based on standard references and internal QA review.

Privacy choices

MyCalcBuddy uses necessary storage for the site to work. Optional analytics, notifications, and future advertising features stay off unless you allow them.