Tell me what it means
Instead of "+25", the alert says the consequence: "You'll miss your ICE in Bremen." It leads with the problem, not the raw number.
← Brain dump
DB Navigator · redesign concept
What if DB Navigator handled the delay?
A redesign of the delay moment inside DB Navigator. Instead of a red “+25”, the app tells you what it means, offers new routes your ticket already covers, and files the refund for you.
A red “+25” is where today's rail apps stop helping.
You find out too lateThe delay shows up as a small red number. Whether you'll miss your connection is left for you to work out.
Rerouting is guessworkYou search again from scratch, standing on the platform, without knowing if your cheap ticket is still valid.
Refunds go unclaimedYou're owed money after an hour's delay, but the claim form is so painful that most people never send it.
Try the new delay flow.
Real rules this uses: if you'll arrive 20+ minutes late, your ticket is valid on other trains for the same trip. At 60+ minutes late you get 25% back, and at 120+ minutes, 50%.
Try it: change the delay, pick a new route, then claim the refund.
Today · 1 traveller · 2nd class
Oldenburg (Oldb) → Hamburg Hbf
RE 1towards Bremen Hbf
08:12Oldenburg (Oldb)Pl. 2
08:41Bremen HbfPl. 4
ICE 579towards Hamburg-Altona
08:55Bremen HbfPl. 8
09:50Hamburg HbfPl. 13
…and now you're on your own. 🫠
✓ Your ticket now works on any train for this trip. No need to buy a new one.
Expected delay at Hamburg
060 min · 25%120 min · 50%
✓
Claim sent
Interactive prototype. Times, trains and prices are illustrative.
From a red number to a plan.
Options with reasons
Each new route explains itself: fastest, fewer changes, or a seat likely free. Your ticket's validity is confirmed upfront, so there's no panic purchase.
The refund claims itself
The app already knows your ticket, train and real arrival time. It pre-fills the claim and shows how close you are to each refund level.
Next projectGoogle Maps: the exact stop