Phase clock: a chart you can recalculate
Choose the phase and timer shown by the HUD. This uses the published 8×8 Normal chart, including the initial 90 seconds. It cannot detect your server, mode, match start or live circle position. Ranked, smaller maps and custom rules need their own chart.
Phase 2 starts at 90 + 240 + 270 = 600 seconds. Its 80-second wait ends at 680; its 100-second shrink ends at 780. If the wait timer has 30 seconds left, chart time is 650 seconds (10:50), with 130 seconds until phase end. This is not elapsed time since landing.
[M01] [M02]Rotation budget: expose your assumptions
Read the current countdown yourself, estimate the route you will actually travel, and enter an effective speed. The default 6 m/s is an illustrative assumption, not a measured character speed. Include bends, climbing, boarding and healing in your estimate. A straight map line usually omits some costs.
Using the result during a match
A negative margin is a signal to revise the plan now. Removing an optional detour changes the budget; choosing a faster number does not create a faster route. Recalculate after a blocked crossing, lost vehicle or unexpected stop.
For a positive margin, keep the reserve visible. The tool cannot know whether a crossing is contested or where you will find cover. Set a destination and fallback before departure, then use the live HUD as the authority.
Inputs stay in this page and are not uploaded or saved. Without JavaScript, the formulas and worked examples remain readable. Neither tool supplies an unpublished damage formula or recommends a fixed combat speed.
Calibrate an input without claiming a universal constant
Decide what your effective-speed input includes. If you time only uninterrupted travel, put boarding, healing and regrouping in the separate stop field. If your timed route already includes those pauses, adding them again double-counts the cost. Both conventions can be useful, but a comparison must use the same one. Write the convention beside your own route note.
Suppose an illustrative 240-metre route takes 50 seconds including a 10-second pause. Its inclusive effective speed is 4.8 m/s. If you instead remove the pause, travel takes 40 seconds and the travel-only speed is 6 m/s, with 10 seconds entered separately. Both give a 50-second total. Using 4.8 and adding the same ten seconds again would incorrectly produce 60.
Observe repeated trips if you want a personal estimate, and keep different terrain and movement states separate. This tool does not collect those observations or turn them into a hidden recommendation. Its value is that you can inspect the arithmetic and replace an assumption you do not trust. A more precise-looking decimal does not repair an unobserved route.
Test how much one extra action costs
Keep the default route and speed: 360 metres at 6 m/s is 60 seconds. With 20 seconds of stops and 15 reserve, the required budget is 95. Against 120 seconds the margin would be 25. Add an optional 30-second detour and it becomes -5. The useful comparison is the change caused by the detour, not whether one isolated result has a reassuring positive sign.
The phase clock and route budget deliberately remain separate. The clock explains a scoped reference chart; the budget uses the countdown you enter from the live HUD. Automatically substituting a chart duration for your actual timer would conceal a mismatch in mode or origin. Compare the tools when useful, but do not assume one can observe the other for you.