How we source.

No number without a source

Every spec on Mesa Project links to the source it was read from and the date we checked it. If we can't find a source, the field says Not published. We don't estimate it or borrow it from a sister model.

When Mesa Project calculates something itself, such as battery watt-hours from volts × amp-hours or power-to-weight, it's marked CALC and the inputs stay traceable.

Three kinds of data

• ClaimedManufacturer claims. What the brand says, even when we read it in a magazine or a dealer listing. Nearly everything on the site today.
• VerifiedIndependently verified. Measured on a scale, a dyno or a tape measure, by us or a named tester. None yet.
• Rider-reportedRider-reported. Real-world range reports and similar. Coming later, moderated, and never mixed into the spec columns.

Where today's numbers come from

113 sources so far: 26 manufacturer, 5 press, 7 distributor, 75 retailer. Retailer listings are the weakest of these, and we use them only where we haven't found a manufacturer spec page yet.

Still on the to-do list: E Ride Pro Pro SS 3.0 (2025), Arctic Leopard XE Pro R (2025). Some of these figures came from search-indexed listings we couldn't open directly. They're flagged on each bike page until an editor reads the source.

Photos

Product photos are the manufacturers' own images, credited under every photo and linked to where we found them. We haven't yet confirmed permission with each brand. If you represent one of these brands and want a photo changed or removed, tell us and we'll do it right away.

Money stays out of the spec table

Mesa Project will eventually earn money from affiliate links, dealer listings and sponsored placements. The rules:

• Paid placements always carry a visible Sponsored label, and the link is marked rel="sponsored".
• Nobody can pay to change a spec, a sort order, a filter result or a comparison highlight.
• Retailer links sit in their own “Where to buy” block, never inside the data.

Found a wrong number?

Good. That's the point. A corrections inbox is coming. Until then, if you're reading this in the repo, open an issue with the bike, the field, and a link to a better source.