Explore Grid Lap TimesStart from the homepage to browse the latest race results, season archives and Formula 1 rules in one place.Go to Homepage →2023 Season Archive →

2023 Azerbaijan F1 GP

Sergio Perez won Azerbaijan GP for Red Bull. The final order and points sit below.

Apr 30, 2023Baku City Circuit51 laps6.003 km
S
Race winnerSergio PerezRed Bull · 1:32:42.436

Results

Pos.GridDriverTeamTimeLapsPts
13Sergio PerezRed Bull1:32:42.4365125
22Max VerstappenRed Bull1:32:44.5735118
31Charles LeclercFerrari1:33:03.6535115
46Fernando AlonsoAston Martin1:33:04.4605112
54Carlos SainzFerrari1:33:27.9275110
65Lewis HamiltonMercedes1:33:28.581518
79Lance StrollAston Martin1:33:34.053516
811George RussellMercedes1:33:56.676515
97Lando NorrisMcLaren1:34:02.812512
108Yuki TsunodaAlphaTauri1:34:06.298511

Race report

Sergio Perez won Azerbaijan GP for Red Bull as the final classification fixed the podium, points, grid and lap data for archive readers.

Sergio Perez won the 2023 Azerbaijan GP for Red Bull, completing 51 laps with 1:32:42.436. The final classification places the result in a clear race-report frame rather than a live-timing feed: winner, podium order, team identity, gap or status text, and lap counts are all carried into the table below. Sergio Perez, Max Verstappen, and Charles Leclerc define the podium sequence used by this page, while the surrounding quick facts preserve the date, circuit and distance context. The source summary also records: Sergio Perez won the 2023 Azerbaijan Grand Prix for Red Bull, completing 51 laps with a recorded time of 1:32:42.436. The podium order in the source classification was Sergio Perez, Max Verstappen, Charles Leclerc. The event was held at Baku City Circuit, a street course in Baku. F1DB records 6.003 km circuit length, 51 race laps, 306.049 km race distance for this race. The top ten classification table below keeps the source ordering intact, including gap, lap and points fields when supplied by F1DB. Fastest lap reference: George Russell - 1:43.370 - Lap 51. Use this page as a compact race archive rather than a live timing report: every result comes from the pinned static snapshot and will be refreshed only when the project bumps the F1DB release tag.

The event sits at Baku City Circuit in Baku, with a listed circuit length of 6.003 km and a race distance of 306.049 km. That circuit context matters because Formula 1 results are not just finishing positions; they combine venue layout, lap count, distance, tyre and timing rhythm, and the pressure of converting grid position into a classified finish. This archive therefore keeps the factual venue block near the result table so readers can compare one Grand Prix with another across the 2017-2026 window. The copy is written in a newsroom style, but every factual claim is limited to the fields that are present in the approved race data. A long, high-speed circuit can make lap deficits read differently from a short street course, and a race distance just above three hundred kilometres gives the classification a different rhythm from a stop-start event with many retirements. The page keeps those venue facts close to the result so the report remains useful even when incident-level detail is not available.

The results table keeps the classification order intact. Top-ten readers can follow Sergio Perez, Max Verstappen, Charles Leclerc, Fernando Alonso, Carlos Sainz, Lewis Hamilton, Lance Stroll, George Russell, Lando Norris, and Yuki Tsunoda, then open the full table to see retirements, non-classified finishes, lap deficits and zero-point finishes. Grid and points columns are part of the same contract because they explain how a race result moves beyond the winner line: a driver may finish high after starting deep, or score points while still leaving the podium untouched. George Russell shows the largest positive grid-to-finish move in the stored table, gaining 3 positions from grid 11 to finish 8. Points are displayed as supplied, so a reader can distinguish podium value from lower top-ten scoring without jumping to another page. Fastest lap context is preserved as George Russell - 1:43.370 - Lap 51, which keeps another race-performance signal near the final order without turning the page into a speculative live blog.

Strategy and race-control context is handled conservatively. Where the source does not include safety-car timing, virtual safety-car periods, penalties, overtakes or collision notes, this page does not invent them. Instead, it uses the available classification, lap, status, gap, grid and points fields to describe what can be verified. That keeps the report useful for comparison work while avoiding fake colour. If a future approved data refresh adds richer incident or stint detail, the report can expand in place; until then, the stable contract is a clean Grand Prix report anchored in winner, podium, venue, table and source-backed finishing status. Readers still get a complete race page because the table shows the decisive sporting outcome, while the prose explains how to read that outcome without pretending to know every stint, radio call or stewarding note.

Team and driver performance is read through the classification rather than through unsupported paddock narrative. Red Bull receives the winner line because Sergio Perez is first in the stored result, but the surrounding rows remain just as important for understanding the race. A second-place finisher may protect a large points haul, a midfield driver may climb through the order, and a retirement can explain why a known contender disappears from the points. The full table is therefore not decorative; it is the main evidence object on the page. Lap counts, status text and zero-point rows help distinguish a normal finish from a late mechanical loss, accident status or non-classified result, while grid and points fields keep the race connected to qualifying and scoring context.

For championship reading, the safest signal in this v1 archive is the race-level points field rather than a fabricated season standings story. The 2023 Azerbaijan GP page highlights who won, which team converted the result, who scored, and which rows remained outside the points. It also keeps the date and route stable for search, sitemap and legal attribution. Readers who return after a 2026 refresh should see the same route and page structure, with updated classification only when the pinned data source changes. That gives the site a repeatable editorial rhythm: headline, subtitle, quick facts, full result table, long-form report, and related races. The result can then be compared across the whole 2017-2026 archive without changing page conventions from season to season.