Sea Run Planner
Use the slower of two route tests, then leave room for mistakes and lag.
This is not an official live event timer. Recheck the route after updates, upgrades or server changes.
A route timer should expose its assumptions
The official description confirms that sea waves close, but it does not publish one universal route timer in the public listing. Enter your observed total window, outbound time and safety buffer. The planner then calculates a latest turn-back time and a conservative pickup estimate.
This is an editorial route instrument, not a live server timer. Treat the result as a plan you verify in the current session, especially after an update, movement change or route detour.
Planner assumptions
| Topic | Input | Meaning | Caution |
|---|---|---|---|
| Total wave window | Seconds from opening to closing | The full route budget. | Measure in the same server and route context. |
| Outbound time | Seconds from base to target | Time before the pickup. | Do not omit a detour or interaction. |
| Return time | Seconds from target to base | Time you need to get home. | Use the slower, repeatable result. |
| Safety buffer | Extra seconds | Protection for mistakes and lag. | More buffer means fewer planned pickups. |
How to improve the plan
Run the same route twice and use the slower return time. Then add a buffer that reflects your controls, server lag and the cost of losing the run. If the output is too conservative, improve one route variable and measure again instead of deleting the buffer.
The tool can estimate pickups only when you provide an average pickup interval. Leave that field blank if pickup time varies too much; a trustworthy turn-back rule is more important than a precise-looking count.
Sea Run Planner FAQ
Is this an official event timer?
No. It is a local calculator based on your observed route. The official listing confirms closing waves but does not provide a universal live timer here.
What if the result says I have no pickup time?
Increase your route window, reduce the target distance, improve the measured bottleneck or keep the run as a return-only test.
Why use the slowest return?
A plan that survives the slower repeat is safer than one based on a best-case sprint.
Tool source and limitation
Read the source type and checked date before treating a changing claim as a fact.
