F1 Race Results and Standings Scraper avatar

F1 Race Results and Standings Scraper

Pricing

from $12.00 / 1,000 result items

Go to Apify Store
F1 Race Results and Standings Scraper

F1 Race Results and Standings Scraper

Pull Formula 1 race results, qualifying, sprint, drivers, constructors, circuits and championship standings from 1950 to present. Returns positions, points, lap times, fastest laps, grid positions and full driver/team metadata per race. Filter by season, round, driver, constructor or circuit.

Pricing

from $12.00 / 1,000 result items

Rating

0.0

(0)

Developer

ParseForge

ParseForge

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

6 hours ago

Last modified

Share

ParseForge Banner

๐ŸŽ๏ธ F1 Race Results and Standings Scraper

๐Ÿš€ Pull Formula 1 race results, qualifying, drivers, constructors, and championship standings from 1950 to present.

๐Ÿ•’ Last updated: 2026-05-06 ยท ๐Ÿ“Š 34 fields per record ยท 1950 to present ยท races, qualifying, sprint, drivers, constructors, circuits, standings ยท 76+ years of F1 history

The F1 Race Results and Standings Scraper pulls Formula 1 data from 1950 to present. Output includes per-race results with positions, points, lap times, fastest laps, grid positions, status, plus full driver/team metadata; qualifying and sprint results; driver and constructor profiles; circuit data; and per-season championship standings.

The scraper covers 76+ years of F1 history with structured records across 9 endpoints. Filters run server-side, so a single run can isolate every Verstappen win, every Ferrari race in 2024, or the complete 1976 championship standings.

๐ŸŽฏ Target Audience๐Ÿ’ก Primary Use Cases
F1 journalists, sports-analytics teams, fantasy F1 platforms, ML pipelines, broadcast researchers, fan communitiesSports analytics, F1 fantasy app data, broadcast production research, betting and odds platforms, content marketing on F1

๐Ÿ“‹ What the F1 Race Results and Standings Scraper does

Five filtering workflows in a single run:

  • ๐Ÿ Race results. Positions, points, lap times, status per race.
  • โฑ๏ธ Qualifying results. Q1/Q2/Q3 times per driver per session.
  • ๐Ÿ† Championship standings. Driver and constructor standings per round, per season.
  • ๐Ÿ‘ค Driver/constructor profiles. One row per driver or team across all years.
  • ๐ŸŸ๏ธ Circuits + schedule. All circuits with geo coordinates; per-season race schedule.

๐Ÿ’ก Why it matters: clean, server-side filtering removes the parser-and-pagination work from your team and keeps your dataset fresh on every run.


๐ŸŽฌ Full Demo

๐Ÿšง Coming soon: a 3-minute walkthrough showing how to go from sign-up to a downloaded dataset.


โš™๏ธ Input

InputTypeDefaultBehavior
maxItemsinteger10Records to return. Free plan caps at 10, paid plan up to 1,000,000.
endpointstring"results"`results`, `qualifying`, `sprint`, `drivers`, `constructors`, `circuits`, `driverStandings`, `constructorStandings`, `races`.
seasonstring"2024"Year, `current`, or empty for all.
roundstring""Specific round number.
driverIdstring""Driver filter (`max_verstappen`, `hamilton`).
constructorIdstring""Constructor filter (`ferrari`, `mercedes`).
circuitIdstring""Circuit filter (`monaco`, `silverstone`).

Example: every 2024 race result.

{
"maxItems": 500,
"endpoint": "results",
"season": "2024"
}

Example: Verstappen all-time wins.

{
"maxItems": 100,
"endpoint": "results",
"driverId": "max_verstappen"
}

๐Ÿ“Š Output

Each record contains 34 fields. Download the dataset as CSV, Excel, JSON, or XML.

๐Ÿงพ Schema

FieldTypeExample
๐Ÿ“… seasonstring"2024"
๐Ÿ”ข roundstring"1"
๐Ÿ raceNamestring"Bahrain Grand Prix"
๐Ÿ“… datestring"2024-03-02"
๐ŸŸ๏ธ circuitNamestring"Bahrain International Circuit"
๐ŸŒ countrystring"Bahrain"
๐Ÿ† positionstring"1"
โญ pointsstring"26"
๐Ÿƒ gridstring"1"
๐Ÿ‘ค driverNamestring"Max Verstappen"
๐Ÿท๏ธ driverNationalitystring"Dutch"
๐ŸŽ๏ธ constructorNamestring"Red Bull"
โฑ๏ธ timeOrStatusstring"1:31:44.742"
โšก fastestLapstringnull
๐Ÿ”— wikipediaUrlstring"https://en.wikipedia.org/wiki/2024_Bahrain_Grand_Prix"

๐Ÿ“ฆ Sample records


โœจ Why choose this Actor

Capability
๐Ÿ“š76+ years of F1. 1950 to present, every race result and championship standing.
๐Ÿ”„9 endpoints. Results, qualifying, sprint, drivers, constructors, circuits, standings, schedule.
๐ŸŒGeo-tagged. Circuit lat/lng for map overlays.
โšกFast. 100 records in under 20 seconds.
๐Ÿ†“No quota. Public open-data backend, no key required.

๐Ÿ“ˆ How it compares to alternatives

ApproachCostCoverageRefreshFiltersSetup
โญ This Actor$5 free credit1950 to presentLive per run9 endpoints, 6 filtersโšก 2 min
Manual Wikipedia scrapingFreeAllVariableDIY๐Ÿข Days
Sports-data APIs$200+/monthLiveLiveMany๐Ÿข Account
CSV dump downloadsFreeVariableStaleNone๐Ÿข ETL

Pick this Actor when you want broad coverage, server-side filtering, and no pipeline maintenance.


๐Ÿš€ How to use

  1. ๐Ÿ“ Sign up. Create a free account with $5 credit (takes 2 minutes).
  2. ๐ŸŒ Open the Actor. Go to the F1 Race Results and Standings Scraper page on the Apify Store.
  3. ๐ŸŽฏ Set input. Pick your filters and maxItems.
  4. ๐Ÿš€ Run it. Click Start and let the Actor collect your data.
  5. ๐Ÿ“ฅ Download. Grab your results in the Dataset tab as CSV, Excel, JSON, or XML.

โฑ๏ธ Total time from signup to downloaded dataset: 3-5 minutes. No coding required.


๐Ÿ’ผ Business use cases

๐Ÿ“Š Sports Analytics

  • Driver-vs-driver historical comparisons
  • Team performance over decades
  • Circuit-specific win patterns
  • Track-record analysis

๐ŸŽฎ Fantasy F1 / Betting

  • Train ML models on historical data
  • Build odds and prediction features
  • Power fantasy F1 leaderboards
  • Run season-simulation engines

๐Ÿ“ฐ Sports Journalism

  • Race-week stat packages
  • Driver retirement features
  • Constructor history articles
  • Championship-decided pieces

๐ŸŽ๏ธ Broadcast & Fan Apps

  • Live commentary stat overlays
  • Build fan-engagement dashboards
  • Build retro F1 viewing apps
  • Power F1 history podcasts

๐Ÿ”Œ Automating F1 Race Results and Standings Scraper

Control the scraper programmatically for scheduled runs and pipeline integrations:

  • ๐ŸŸข Node.js. Install the apify-client NPM package.
  • ๐Ÿ Python. Use the apify-client PyPI package.
  • ๐Ÿ“š See the Apify API documentation for full details.

The Apify Schedules feature lets you trigger this Actor on any cron interval. Hourly, daily, or weekly refreshes keep downstream databases in sync automatically.


๐ŸŒŸ Beyond business use cases

Data like this powers more than commercial workflows. The same structured records support research, education, civic projects, and personal initiatives.

๐ŸŽ“ Research and academia

  • Sports-economics research
  • Performance analysis studies
  • Reproducible F1 data snapshots
  • Coursework on time-series analysis

๐ŸŽจ Personal and creative

  • Personal F1 dashboards
  • Side projects on race data
  • Fan blogs and newsletters
  • Hobbyist visualizations

๐Ÿค Non-profit and civic

  • Sports inclusion research
  • Driver diversity studies
  • Open sports-data contributions
  • Educational stats projects

๐Ÿงช Experimentation

  • Train race-prediction models
  • Prototype F1-aware agents
  • Build position-change visualizations
  • Test sports analytics libraries

๐Ÿค– Ask an AI assistant about this scraper

Open a ready-to-send prompt about this ParseForge actor in the AI of your choice:


โ“ Frequently Asked Questions

๐Ÿงฉ How does it work?

Pick an endpoint and optional filters (season, round, driver, constructor, circuit). The Actor queries the public Ergast/Jolpica F1 backend and emits structured records.

๐Ÿ“… How far back does data go?

1950, the first F1 season. Every race, qualifying session, and championship is included.

๐Ÿ What's the difference between endpoints?

Each endpoint returns a different table: results (per-race), qualifying (Q1-Q3 times), sprint, drivers (per driver), constructors (per team), circuits, standings (driver/constructor), races (schedule).

๐Ÿ“Š How many fields per record?

Up to 34 fields per race-result row. Other endpoints return correspondingly different schemas.

๐Ÿ” Can I schedule runs?

Yes. Use Apify Schedules to refresh standings after each Grand Prix or build a season-tracker.

โš–๏ธ Is this data public?

Yes. The Ergast Developer API and its Jolpica-hosted mirror publish F1 data under an open license.

โฑ๏ธ Are lap times included?

Yes for race results (timeOrStatus, fastestLap). Per-lap data is available on a separate endpoint via the laps query.

๐Ÿ’ณ Do I need a paid Apify plan?

No. The free plan covers preview runs. A paid plan unlocks higher item counts and scheduling.

๐Ÿ†˜ What if a run fails?

Apify retries transient errors. Partial datasets are preserved.

๐ŸŒ Does it cover sprint races?

Yes. Set endpoint to sprint for sprint results.


๐Ÿ”Œ Integrate with any app

F1 Race Results and Standings Scraper connects to any cloud service via Apify integrations:

  • Make - Automate multi-step workflows
  • Zapier - Connect with 5,000+ apps
  • Slack - Get run notifications in your channels
  • Airbyte - Pipe data into your warehouse
  • GitHub - Trigger runs from commits and releases
  • Google Drive - Export datasets straight to Sheets

You can also use webhooks to trigger downstream actions when a run finishes.


๐Ÿ’ก Pro Tip: browse the complete ParseForge collection for more reference-data scrapers.


๐Ÿ†˜ Need Help? Open our contact form to request a new scraper, propose a custom data project, or report an issue.


โš ๏ธ Disclaimer: this Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by Formula One Group, the FIA, the Ergast project, the Jolpica project, or any F1 team or driver. All trademarks mentioned are the property of their respective owners. Only publicly available open data is collected.