Nick runs NYC

TCS New York City Marathon · Sunday, November 1
Connecting…
Distance
–
of 26.2 mi
Pace
–
per mile
Heart rate
–
bpm
Elapsed
–
 
Projected finish
–
 
Nick Goal pace Timing mat Cheer spot

When will Nick reach me?

Share your location once and the page works out which mile of the course you're nearest and when he'll get there. Your location stays in your browser.

Where to cheer

Estimated times at each spot, from his current pace. They move as he runs.

Send a cheer

Messages are bundled every few minutes and sent to Nick's watch.

    Course profile

    Official splits

    Timing mats from NYRR, roughly every mile from mile 3. These update even when his phone has no signal.

    MarkClockRace timeSplit pacevs goal

    No mats crossed yet.

    Heart rate

    How this works

    Garmin watch → his phone → Garmin's LiveTrack → this page. Position, pace, heart rate, cadence, about every 15 seconds. When his phone has no signal (the start village, the big crowds), the points queue up and arrive late. The status pill turns amber and says estimating.
    NYRR timing mats at nearly every mile. Official, and independent of his phone. They anchor the distance, and the splits table updates even when nothing else does.
    His phone's own GPS posts to this page as a backup. It only takes over if the Garmin feed goes quiet. It shares the phone's signal, so dead zones affect it too.
    Between updates the dot slides along the course at his last pace, never past a mat that hasn't reported, and holds still if the watch says he stopped.

    Want to see it all happen? The simulation replays his 2025 race in fast-forward with fake dead zones and a Garmin failure at mile 10.