18 April 2025
Put into service
0 km
Workshop A
Sealed
Bike register for Germany
A bike that
remembers.
Service, odometer, components, ownership changes — recorded where they happen: at the work stand. Chained, so nobody can massage the numbers later. Readable from a QR code, with no app and no account.
Free for workshops. No contract, no monthly fee, no minimum volume.
3,900bikes in the register
2,700recorded events
0 €for workshops, for good
The public pass
This is the whole pass.
There is no second page.
A code on the frame, a browser, done. The pass belongs to the bike — not to a customer file. The owner’s name and address are not in it, and they are not going in.
thebikepassport.com/p/8K4N-2QJD
- Frame number
- WBK·········1396 · resolved
- Odometer
- 4,812 km +3,572 km since the last service
- Last service
- 12 Feb 2026 Workshop B · chain, brake pads
- Components
- 7 recorded Drivetrain, brakes, battery, wheels
- Battery
- 625 Wh, fitted 04/2025 Battery-passport ready from 02/2027
- History
- 4 entries · no gaps
The problem
A bike’s history ends with the mechanic who knows it.
A bike changes workshop, city, owner. Its history doesn’t. It stays behind: on paper invoices, in shop systems that don’t talk to each other, and in the head of a colleague who eventually quits.
“When was the last service?”
“No idea. Bought it used.”
- 01
No record
Which chain, which battery, when were the brakes last done? The answer sits in three systems that don’t know about each other — or in none of them.
- 02
No proof
An e-bike costs as much as a used car. At resale there is no stamped service book, only stories. The price ends up set by doubt.
- 03
No protection
After a theft, the frame number is on a receipt in a shoebox. If the shoebox is still there.
- 04
No head start
From 2027 the EU requires a digital battery passport. A shop with no history starts from zero.
0 €per workshop, per month, per entry.
For workshops
Workshops pay nothing. That’s not generosity, it’s arithmetic.
A register with no entries is worthless, and entries are made in exactly one place: at the work stand. Nobody gets paid for supplying data. So the rule is reciprocity — you write, you read.
- The history before the job
- You see what was done to a bike you have never met, before it goes up in the stand.
- No new software
- The entry can come out of the system you already use. Ideally the mechanic never notices it happened.
- No password per person
- A shop tablet is paired once. Shared device, people coming and going — that is what a workshop actually looks like.
- Your customer data stays with you
- The pass belongs to the bike. Your customers’ names and addresses have no place in the register.
Integrity
Every entry gets sealed.
An entry is never edited and never deleted — not even by us. A correction is a new entry that sets the old one straight. The mistake stays visible, and that is exactly the point.
1
Every entry gets a seal when it is saved.
2
Inside every seal sits the seal of the entry before it. That is what holds the chain together.
3
Change something after the fact and every seal from there on springs open. There is no quietly closing them again.
3 November 2025
Service — chain, brake pads
1,240 km
Workshop A
Sealed
12 February 2026
Change of owner
4,812 km
Workshop B
Sealed
Chain closed
All three seals match. The odometer reading is the one the workshops entered.
For manufacturers and workshop software
One API. And a window you embed.
A small workshop is not going to build an integration. Its software vendor will, the moment its customers want to see the history. The same deal applies there: contribute, and you read.
- The pass window is an iframe, not an npm package
- One fix reaches every vendor at once, and the host page’s JavaScript cannot read the pass.
- Collisions are not guessed
- When two bikes match the same number, the workshop decides — not the algorithm.
- Data stays in the EU
- Database in Frankfurt, TLS all the way into the database, a log of every access.
# Append a service event. There is no overwrite.
Authorization: Bearer <workshop API key>
Content-Type: application/json
{
"frame_number": "WBK0000000161396",
"type": "service.performed",
"occurred_at": "2026-02-12",
"odometer_km": 4812,
"work": ["chain", "brake_pads"]
}
→ 201 Created
{
"event_id": "ev_3JX9c5d7853c",
"content_hash": "c5d7853c…0320b734",
"chain_hash": "8736ebfc…17ee2645",
"passport_url": "https://thebikepassport.com/p/8K4N-2QJD",
"identity": { "matched": true, "confidence": 0.98 }
}Regulation (EU) 2023/154218 February2027
From that day on, the digital battery passport is mandatory across Europe for batteries in light means of transport. Not recommended — mandatory.
If you are keeping a bike’s history anyway, you already have the structure for it: an identifiable object, an unbroken sequence of events, and a publicly readable address behind a QR code. The battery passport is then one more event type, not a project.
We run the register and we sell bikes. “Trust us” would not be an answer. A chain anyone can recalculate is one.
Contact
A bike without a history is a promise. With one, it is proof.
The register is running, the API is running, the first workshops are writing to it. Tell us what your shop could record and what you want to read — that is what the integration is built from.
Bike Passport — a project by We Like Bikes. Legal notice and privacy policy are there.
No cookies, no tracking pixels, no external services: this page loads nothing from anywhere else.