Nairobi belongs to the City line — races named for places rather than distances. Here the name points to Kenya’s capital: a place already associated with altitude, long horizons, and running that sits close to ordinary life. The label sets atmosphere. The mechanics do the rest.
What matters in Season 262 is the combination of an Open format — no fixed target to close — with a single clock that runs a full quarter. From 1 April through 30 June, UTC, kilometres accumulate without a printed finish line. There is nothing to “complete” in the sense of crossing a set distance; there is only what gets logged, verified, and still standing when the window ends.
That absence of a cap changes how the race feels.
Open field, closed window
The rules stay sparse on purpose. The window is fixed: activity must be published to Nairobi inside the live span. How sessions are spaced, how long each run is, and how aggressively volume ramps all remain for the entrant to decide.
That freedom produces different shapes on the leaderboard. Some athletes lean on small, repeated slices. Others bank larger blocks when the calendar allows. Neither pattern is guaranteed to hold across twelve weeks; both have to survive proof.
Over time, those choices show up as a single number: total verified distance, still moving until June closes.
Under everything else
Three months sounds like room to breathe. In a season that stacks Barrel, multiruns, pace work, and shorter classics in parallel, it often works the other way.
Nairobi does not pause while other races run. It keeps accruing in the background — easy to treat as optional until the totals say otherwise. Athletes who enter late still have a path, but Open scoring rewards time on the board; every week not committed is distance someone else can still add.
The pressure is diffuse at first. It tightens as the quarter ages and small gaps stop looking negligible.
Continuity as the test
Without a mandatory daily structure, the race measures something quieter than sprint finishes: whether attention holds.
Momentum from April can flatten by June. A delayed start preserves freshness but shortens the runway to answer leaders. Front-loading kilometres trades early standing for carrying fatigue into later months; hanging back bets on a back half that other commitments may not leave intact.
None of these trade-offs is labeled wrong. Each has a cost that shows up in the same place — the cumulative line when UTC midnight on 30 June passes.
Proof parallel to the running
Scoring follows the published mechanic: maximum total distance among valid results, subject to verification.
So the physical work and the procedural work travel together. A gap in either breaks the chain. The minimal surface of the format hides that second layer; three months of “just run” still has to arrive as defensible, complete records.
When the live phase ends
June closes the active window, but standings do not lock on the last stride. Results move through review; in open fields, provisional order can shift as submissions settle.
Only after the race reaches Results out do the totals freeze in their final form. Until then, distances that looked secure can still move — and with a quarter of runway, small corrections add up.
What the line measures
Nairobi rarely ends in one dramatic session. It settles when the clock stops and verified distance is final.
By then the leaderboard shows who owned the open quarter — not who planned best in April on paper, but who actually threaded volume through overlapping demands and brought most of it through proof.
The underlying demand
Tactics stay open underneath. What the format rewards is alignment over months: between intention and what actually lands in the log, between the rest of the season and this long horizontal race, between the ease of deferring and the cost of catching up later.
That alignment is what turns an open window into a clear outcome — or leaves it as distance that never quite consolidated on the board.
