F1Peak
Game-style Formula 1 session viewer
The signature trick, running
Real canonical circuit lines from the app's own cache. No track artwork exists.
This is the app's real canonical line for Monaco: the median of 18 clean laps of car position data from the Monaco Grand Prix, June 2026 (agreement score 109), with the corners, start/finish seam and pit lane the app derived itself. No hand-drawn track art exists anywhere in F1Peak.
F1Peak is a game-style Formula 1 session viewer: a live track map with every car moving on it, a timing tower, replay with DVR-style scrubbing, and a telemetry analytics layer for comparing drivers. It looks like something out of a racing game's spectator mode, and everything on screen is real session data.
The data comes from the static file tree and streaming endpoints behind Formula 1's own live-timing player, which are publicly reachable for the basic topics. The feed is minimal by design: car positions at about 3.7 Hz with metres of noise, five telemetry channels, and no track map at all. F1Peak's defining constraint is squeezing a rich viewer out of that, honestly.
Derived, not downloaded
The circuit outline is not a hand-drawn asset. It is derived from the cars themselves: clean laps from multiple drivers are resampled by arc length, phase-aligned and median-combined into a canonical outline per circuit, with the start/finish seam parked on the longest straight. Corner numbers snap official per-circuit counts to the strongest real apexes, because pure geometric detection produces phantom corners at places like Monaco.
The same spine carries the analytics: GPS samples project onto the derived centreline as a distance along the lap, which unlocks real lap windows, speed-by-distance comparisons between drivers, and derived channels like lateral G (computed from speed and curvature, and badged as the estimate it is). Where the derivation could be cross-checked against the feed's own statistics, it was: derived top speeds matched to within a single km/h.
Why it isn't public
Formula 1 blocks requests from datacenter and hosting IP ranges, so a hosted relay simply cannot connect: the live path only works from a residential connection. F1Peak therefore runs in my lab rather than on a public URL. A hosted replay archive built from published session files is the plausible future path, but it is not built, so this page will not pretend otherwise.
The full derivation stories (the track from car positions, the projection spine, the corner numbering problem, the data path itself) are in the devlog.