Live now!
Formula 1 reference · 2026 season

Formula 1 circuits and calendar, 2026 season

Every round of the 2026 championship with circuit length, lap count, race distance, corner count and the current race lap record. Round numbers, dates and venues are the calendar as it stands after this season's changes, not as it was first announced.

23Rounds on the calendar
5Continents visited
6Sprint weekends
2Circuits new or returning

All 23 rounds

Sortable by any column. Click Length to find the longest lap, Corners to find the most technical circuit, or Lap record to see which times have stood the longest. Sprint weekends are marked. Circuit and session data of this kind is available from the Sportmonks Motorsport API as JSON.

Rd Circuit Location Length Laps Distance Corners Lap record

Lap records are race lap records, current as of 4 August 2026. Ten of the twenty-two were set in 2024 or 2025, and none was set in 2026: the new-regulation cars are slower than the generation before them, so these times are expected to stand all season. Circuit specifications and the calendar are public record, not API fields.

Circuit profiles

One card per round, in calendar order.

Which of these numbers come from an API

Not all of them, and it is worth being straight about that. A circuit's length and corner count are fixed facts that belong in a reference table. What you cannot maintain by hand is everything that happens at those circuits across a season, and that is the part the Motorsport API is for.

Where each number comes from
  • ● Fixed reference · on this page
    Length, laps, race distance, corners, lap record
    Public record. Circuit specifications change only when a circuit is resurfaced or reprofiled, which is roughly once a decade per venue. There is no reason to call an endpoint for these, and we have not pretended otherwise.
  • ● From the API · every session
    Who was entered, and what they did
    Each round is a fixture with its own id, tied to a season_id and a league_id. Ask for a round and you get the entry list back per session, including lineups.driver, lineups.team and lineups.number, plus session results, classification, gaps and lap times.
  • ● From the API · the calendar itself
    The schedule, without you watching for changes
    This season is the argument for reading the calendar rather than typing it. Two rounds were cancelled in March and a replacement venue was added in July. A hardcoded schedule was wrong twice; a season query was current both times.
Circuit specifications and the calendar in the table above are public record. The response below is a real round from this season.
Live request 200 OK
GET https://api.sportmonks.com/v3/motorsport/fixtures/19615512
  ?include=lineups.driver;lineups.team
  &api_token=YOUR_TOKEN
// truncated for display: 2 of 22 entries shown
{
  "data": {
    "id": 19615512,
    "sport_id": 2,
    "league_id": 3468,
    "season_id": 26733,
    "lineups": [
      {
        "number": 1,
        "driver": {
          "id": 37920802,
          "name": "Lando Norris"
        },
        "team": {
          "id": 276191,
          "name": "McLaren",
          "code": "MCL"
        }
      },
      {
        "number": 3,
        "driver": {
          "id": 37920800,
          "name": "Max Verstappen"
        },
        "team": {
          "id": 276190,
          "name": "Red Bull Racing",
          "code": "RBR"
        }
      }
    ]
  }
}
Round 10, Spa-Francorchamps, 19 July 2026. Values printed exactly as returned. One fixture id gets you the entry list for that round, which is how you attach results to a circuit without maintaining either list yourself.
Formula 1 reference, 2026 season

Build with the Formula 1 API

The calendar moved twice this season. Reading it from an endpoint is one call, and it was right both times. Get a token, run it against a real round, and see the response before you commit to anything.

One plan, every race No contracts, no minimums Human support, 7 days a week