About
A STRUCTURED, SOURCED DATABASE OF SUPERCARS AND HYPERCARS — WRITTEN AND MAINTAINED BY AN INDEPENDENT EDITORIAL TEAM.
What we cover
SUPERCARS.ORG is a reference database for supercars and hypercars — the road-legal and track-only flagships that sit at the top of every manufacturer's range, from the greats of the past to the latest announcements.
Every record carries its core figures: power, torque, top speed, acceleration, production totals and original pricing, alongside galleries, generations, and the variants that each model was sold in. Where a figure differs between markets or is disputed between sources, we say so rather than pick one at random.
The database is built to be browsed, filtered and compared. You can sort the full list by anything from engine configuration to country of origin, put two cars side by side on the compare page, and dig into individual manufacturers to see how their flagships evolved over time.
How we research
Figures come from manufacturer statements, press kits and contemporary coverage. Each car record keeps its sources attached, and figures are tagged by confidence — so you can see at a glance whether a number is confirmed, an estimate, or still disputed.
The same discipline applies to our news coverage. Every article is written and checked against the sources it cites. When something can't be verified, it doesn't go in — or it's clearly labelled as unconfirmed.
The database is a living document. Records are updated as new information surfaces, and corrections are made as soon as they're found.
Who we are
SUPERCARS.ORG is run by a small team based in the United Kingdom — people who have spent years reading about, watching and following supercars, and who decided to build the reference they always wanted.
We're not a company, an agency or a content farm. We're enthusiasts who care about the details: the engineering, the history, the numbers behind each car. If it's on this site, someone on the team put the hours in to get it right.
Get in touch
Interested in a partnership or a collaboration, or spotted something in the database that needs a correction? We'd like to hear from you.
