The 2026 F1 calendar has 23 races across five continents. The original 24-round schedule was trimmed after the Bahrain Grand Prix was cancelled. Each circuit has a distinct character: high-speed flowing corners, slow technical sequences, twisty street layouts, fast straights. Here is the complete data set for the season, with the circuits ranked by characteristic.
The full table
| Spec | Length | Corners | DRS | Elevation Δ |
|---|---|---|---|---|
| Saudi Arabia (Jeddah) | 6.174 km | 27 | 3 zones | 11 m |
| Australia (Albert Park) | 5.278 km | 14 | 4 zones | 5 m |
| Japan (Suzuka) | 5.807 km | 18 | 2 zones | 40 m |
| China (Shanghai) | 5.451 km | 16 | 2 zones | 8 m |
| Miami | 5.412 km | 19 | 3 zones | 3 m |
| Imola | 4.909 km | 19 | 2 zones | 46 m |
| Monaco | 3.337 km | 19 | 1 zone | 42 m |
| Spain (Barcelona) | 4.657 km | 14 | 2 zones | 30 m |
| Canada (Montréal) | 4.361 km | 14 | 3 zones | 7 m |
| Austria (Red Bull Ring) | 4.318 km | 10 | 3 zones | 63 m |
| Britain (Silverstone) | 5.891 km | 18 | 2 zones | 16 m |
| Hungary | 4.381 km | 14 | 2 zones | 36 m |
| Belgium (Spa) | 7.004 km | 19 | 2 zones | 101 m |
| Netherlands (Zandvoort) | 4.259 km | 14 | 2 zones | 20 m |
| Italy (Monza) | 5.793 km | 11 | 2 zones | 15 m |
| Singapore | 4.940 km | 19 | 4 zones | 4 m |
| USA (Austin) | 5.513 km | 20 | 2 zones | 40 m |
| Mexico | 4.304 km | 17 | 3 zones | 6 m |
| Brazil (Interlagos) | 4.309 km | 15 | 2 zones | 43 m |
| Las Vegas | 6.201 km | 17 | 2 zones | 0 m |
| Qatar (Lusail) | 5.419 km | 16 | 2 zones | 5 m |
| Abu Dhabi (Yas Marina) | 5.281 km | 16 | 2 zones | 7 m |
A few things stand out from this table[1]:
- Spa is the longest at 7.004 km. Monaco the shortest at 3.337 km. A driver completes 70 laps of Monaco in roughly the time they complete 44 of Spa.
- The biggest elevation change is Spa at 101 metres. Eau Rouge alone climbs 41 metres in under 200 metres of track length.
- Singapore has the most DRS zones (4) reflecting how slow the circuit is and how much help drivers need to overtake.
Lap-time benchmark
Different circuits, different lap-time regimes. Lap-time is a function of length, corner count, average corner speed, and downforce setup.
Source: F1 official lap records via Ergast API
Spa's 1:46 is dominated by the long Kemmel Straight and the Les Combes complex. Monaco's 1:13 is dominated by Casino Square and Tabac, with no real straight at all. Singapore at 1:28 is the slowest of the medium-length circuits, partly due to bumpy concrete-strip surface beneath the painted lines.
Three regime classification
I find it useful to bucket circuits by their dominant characteristic. Setup choices and tyre strategy follow from the regime.
Power tracks
Spa, Monza, Las Vegas, Baku, Saudi Arabia. Long straights, low downforce setups, slipstream-dependent overtaking. Engine power matters more than chassis. Mercedes traditionally strong; Ferrari competitive; Red Bull less so since 2024 due to drag-coefficient compromises.
Downforce tracks
Hungary, Singapore, Monaco, Zandvoort. High downforce, low engine emphasis. Mechanical grip and chassis balance dominate. McLaren and Ferrari historically strong; Red Bull good when the front-end balance is right.
Hybrid tracks
Silverstone, Suzuka, Spa (yes, both), Austin, Mexico. Long fast corners require both downforce and power. The cars that win these are the cars that win the championship.
Where to find the actual data
Ergast Developer API is free, no key required, and serves every result, lap, qualifying time, and circuit dimension since 1950[1]. Example endpoint:
https://ergast.com/api/f1/2026/circuits.json
returns every 2026 circuit as JSON with lat/long, length, country, and a Wikipedia link.
For lap-by-lap telemetry (throttle, brake, gear, speed every ten metres), fastF1 wraps the F1 live timing API[2]. The data is rich and free for non-commercial use.
For tyre allocation per circuit, Pirelli's motorsport press releases publish the compound choices a week before each race[3].
How I would build this on a website
The Ergast API is fine for static, retrospective data. For live timing during sessions, the F1 official live timing endpoint at livetiming.formula1.com streams JSON over WebSocket. There is no documentation but reverse-engineered libraries handle it.
A nice F1 data product would combine:
- Ergast for historical context (lap records, championship standings, qualifying gaps)
- fastF1 for telemetry overlays during a race weekend
- F1 live timing for in-session feeds
- Custom commentary based on real-time gap evolution
That is what F1 Tempo and similar sites do. The data is freely available; the value is in the presentation.
Watching the 2026 season
The 23 races split roughly into:
- 4 must-watch live: Spa, Monaco, Suzuka, Silverstone
- 8 worth watching live: Australia, Imola, Canada, Singapore, USA, Mexico, Brazil, Abu Dhabi
- 11 record and skip the boring bits: everything else
The 2026 regulations change everything. Active aero, sustainable fuels, smaller cars. Some traditionally dull circuits (Hungary, Spain) might become exciting. Some traditionally good ones (Monaco, Singapore) might become processional if the new cars do not overtake well.
I will write a follow-up after Saudi Arabia, the season opener, with first-look data on whether the regulations have changed the racing.