A breakaway is a pursuit problem wearing a jersey. Two groups are on the same road at different speeds, separated by a gap that is quoted in minutes rather than metres, and the only question that matters is whether the road runs out before the gap does. The arithmetic is not difficult, but almost nobody does it during a race, which is why commentary spends whole afternoons saying the gap is coming down without ever saying where the junction will happen. This cycling breakaway calculator does that sum: it converts the time gap into a distance, divides by the closing rate, and tells you how far from the finish the catch lands.
Arb Digital publishes free sports calculators that show the mechanism rather than a verdict, so this one also reports the closing rate, the gap in metres, and the two threshold speeds — the speed the break would need to survive and the speed the bunch would need to catch it exactly on the line. Those two numbers are usually more interesting than the headline, because they tell you how much either group has to change to flip the result.
What This Cycling Breakaway Calculator Does
It models the chase as constant-speed pursuit. You give it the distance remaining, the current time gap, the speed of the break and the speed of the bunch, and it works out whether the closing rate is enough to erase the gap before the finish line. If it is, the tool reports the distance to go at the moment of the catch. If it is not, it reports the margin in seconds at the line and the distance the break has in hand.
The reason the model is worth building at all is that the two groups do not ride at the same speed for physical reasons that are well documented. Riding in a bunch cuts aerodynamic drag dramatically — the Wikipedia article on the peloton summarises the published modelling and reports drag reductions in the middle of a well-developed group of as much as 95 per cent, and cites Olds’ analysis showing that group size and wheel spacing govern whether a chase can ever close. The glossary of cycling terminology defines a gap as a separation large enough that drafting no longer helps, which is the point at which the two groups become genuinely independent systems.
How to Use It
- Pick your units first. Everything switches together, so a mixed entry of kilometres and mph is not possible.
- Enter the distance to the finish, not the total race distance. This is the number on the race clock or the roadside boards.
- Enter the time gap in minutes and seconds as it is called. The tool converts it to a road distance itself, at the chasers’ speed.
- Enter the two speeds you expect for the rest of the race. Not the current instantaneous speeds — the averages you think each group will hold from here.
- Read the two threshold speeds in the grid. They tell you how much either group has to find to change the outcome, which is the practically useful part.
The Formula and How It Is Calculated
Gap on the road = time gap × peloton speed. Closing rate = peloton speed − break speed. Time to catch = gap on the road ÷ closing rate. Distance to go at the catch = distance remaining − break speed × time to catch. If the break survives, the margin at the line = (distance remaining + gap on the road) ÷ peloton speed − distance remaining ÷ break speed.
Work the default example by hand. Forty kilometres to go, a gap of two minutes thirty, the break holding 42 km/h and the bunch at 45 km/h. The bunch covers 45 km/h ÷ 3,600 = 12.5 metres per second, so 150 seconds of gap is 1,875 metres of road. The closing rate is 3 km/h, which is 0.8333 metres per second, so the catch takes 1,875 ÷ 0.8333 = 2,250 seconds, or 37.5 minutes. In that time the break rides 42 × 0.625 = 26.25 kilometres, leaving 40 − 26.25 = 13.75 kilometres to go when it is swallowed. The tool returns exactly that.
The threshold speeds fall out of the same relation. For the break to reach the line first it needs distance remaining ÷ break speed to be no greater than (distance remaining + gap) ÷ peloton speed, which rearranges to a required break speed of 45 × 40 ÷ 41.875 = 42.99 km/h. Under a kilometre an hour more than it is riding. That is the number that explains why breaks so often lose by seconds: the margin between surviving and being caught with fourteen kilometres left is tiny.
Why a Time Gap Is Not a Distance
This is the most common misreading in the sport and it is worth being blunt about. When race radio says the gap is three minutes, that is the interval between the two groups passing the same point on the road. Converting it to metres requires a speed, and the correct speed is the chasers’, because they are the ones who still have to cover the ground. At 45 km/h a three-minute gap is 2.25 kilometres. At 55 km/h on a fast finale, the same three minutes is 2.75 kilometres — the road gap grows even though the time gap has not changed.
The reverse effect matters more. If the bunch lifts its speed and the break holds its own, the time gap falls even before any ground is made up, because the same road distance now takes the bunch less time to cover. Gaps therefore appear to collapse in the last hour partly as an artefact of the units. Some of the drama is arithmetic.
The same care applies when you are pacing your own ride rather than watching one. The cycling pace calculator handles the single-rider version of speed, distance and time, and the pace converter moves between the pace and speed conventions different sports use. This page is the two-group problem those tools do not cover.
What Constant Speed Cannot Capture
The model assumes both groups hold the speeds you enter for the rest of the race. That is a deliberate simplification and it is wrong in several specific, predictable ways.
Breakaways slow down. A group that has been away for a hundred kilometres is riding on a diminishing reserve, and the last twenty kilometres are usually the slowest, not the fastest. A peloton does the opposite: an organised chase with fresh teams rotating on the front accelerates through the closing hour. So the real closing rate typically widens as the race goes on, and a model with fixed speeds will place the catch further from the line than it happens.
Terrain reorders everything. A climb favours a small group of light riders and punishes a bunch that has to funnel onto a narrow road. A descent or a crosswind favours the group with the most riders to share the work. Wind direction alone can reverse the answer: a headwind finale makes the drafting advantage decisive and almost always kills a small break, while a tailwind flattens the difference because drag matters less at any given effort. The drag force calculator shows why that dependence is so steep, since aerodynamic drag rises with the square of speed.
Finally, neither group is riding a physics problem. Teams chase when they have a sprinter and sit up when they do not. A break with a rider dangerous on general classification will be chased far harder than an identical break of no threat. The arithmetic tells you what happens at the speeds you enter; it has no opinion about whether anyone wants that outcome.
Why the Number of Riders Changes the Answer
The rider count in the form does not enter the calculation, and that is intentional — it belongs to the question of whether the speed you entered is realistic. A solo rider takes the full aerodynamic load for every metre. Four riders rotating share it, and each spends most of the time at a substantially lower power for the same speed. The published modelling of the peloton makes the same point about the chase: the size of the chasing group and how tightly it drafts determine whether the closing rate you assumed can be sustained at all.
The practical rule that follows is that a small break needs a bigger head start than its speed suggests, because its speed will decay faster. When you use this tool on a live race, the honest approach is to run it twice: once at the speeds being ridden now, and once with the break a full unit slower and the bunch a unit faster. If the break survives both, it is genuinely clear. If it only survives the optimistic run, it is in trouble.
Power output is where that difference becomes concrete rather than intuitive. The cycling power calculator estimates the watts required to hold a speed against drag, gradient and rolling resistance, and running the same speed for a solo rider and for a rider sheltering in a group shows how large the sharing effect is.
Arb Digital builds free tools like this one because useful pages earn attention. If you want tools, calculators or content built for your own audience, we can help.
Browse All Free Tools Talk to Arb DigitalCommon Mistakes to Avoid
- Treating the time gap as a fixed distance — it converts to metres at the chasers’ speed, so the same gap in minutes is more road when the bunch is riding faster.
- Entering total race distance instead of distance remaining — the model only cares about the road still to be covered.
- Using instantaneous speeds — a single fast split from a descent will place the catch in completely the wrong place. Use the averages you expect from here to the line.
- Assuming the break holds its speed — breaks decay and organised chases accelerate, so a constant-speed model usually flatters the break.
- Ignoring wind and terrain — a headwind finale multiplies the bunch’s drafting advantage and is the single most common reason a break that looked safe is caught.
Related Free Tools From Arb Digital
For single-rider speed, distance and time work use the cycling pace calculator, and for the effort behind a speed the cycling power calculator. The drag force calculator explains why speed is so expensive, the bike gear ratio calculator covers the transmission side, and the pace converter moves between pace and speed. Everything is on the free online tools hub.
Frequently Asked Questions
Multiply the gap by the speed of the chasing group, because they are the ones who still have to cover that ground. Two minutes thirty at 45 km/h is 12.5 metres per second times 150 seconds, which is 1,875 metres. Using the breakaway's speed instead gives a slightly different and less useful answer, since the question you are asking is how long the bunch needs to ride to reach the point the break has already passed.
Because the gap is quoted in time, not distance. If the road separation stays the same but the bunch rides faster, it covers that separation in fewer seconds, so the quoted gap shrinks without a single metre being taken back. Part of every late-race collapse in the gap is this unit effect rather than real progress, which is one reason the road-distance figure in the grid above is worth watching alongside the minutes.
It depends entirely on how much road is left. The tool reports the exact chase speed that would bring the catch to the finish line, so anything above that number catches the break and anything below it does not. In the default example the bunch needs a shade over 42.99 km/h from the break's side, or equivalently must ride 45 km/h to catch with fourteen kilometres to spare. Small changes in either speed move the catch point enormously.
Not to this arithmetic, but very much to whether the speed you entered is realistic. Aerodynamic drag dominates at racing speeds and a rider in a group can shelter from most of it, so four riders rotating hold a given speed at far lower individual cost than one rider alone. That is why the field is on the form: use it to sanity-check your speed assumption rather than expecting it to change the calculated catch point.
Because constant speeds flatter the break. In reality a group that has been away for hours slows in the final hour while an organised chase with fresh teams accelerates, so the true closing rate widens as the finish approaches. A useful habit is to run the calculation twice, once at current speeds and once with the break one unit slower and the bunch one unit faster, and to trust the result only if both runs agree.
More than almost anything else. Drafting saves energy in proportion to how much drag there is to save, so a headwind finale makes sheltering in the bunch enormously more valuable and usually ends a small breakaway. A tailwind reduces the advantage because everyone is fighting less air, and a crosswind can shatter the bunch itself into echelons and hand the break a reprieve. None of that is in the arithmetic, so treat wind as a reason to adjust your speed inputs.
Then there is no catch at all and the tool says so in words rather than returning a nonsensical negative time. The gap grows for as long as that holds, and the result switches to reporting the margin at the finish line. This is genuinely common in the middle of a stage, when the bunch is content to let a break go, and it is the reason a chase has to start early enough to be worth starting at all.
The arithmetic is general and applies to any two groups moving at different speeds on the same course, so a marathon chase pack or a triathlon bike leg works the same way. What does not transfer is the aerodynamic reasoning about why the groups ride at different speeds, which is far stronger in cycling than in running because the speeds are higher and drag rises with the square of speed. Use the model, but not the sport-specific commentary around it.
This tool is provided for educational use. It models a constant-speed pursuit from figures you enter and does not predict the outcome of any real race. Actual speeds vary with terrain, wind, fatigue and tactics, and the result should be treated as an illustration of the arithmetic rather than a forecast.
