Journeys
See what is ready to claim, what needs checking and what happened next.
Add journeys
Choose a TfL statement and we will detect the format, skip duplicates and check each journey.
Add journeys
PDF for contactless cards, CSV for Oyster. You can add more than one file.
Or paste statement text / CSV instead
Account
Manage your account, plan and claim suggestions.
Your account
Checking sign-in…
Sign in to save your journeys to your account and keep them in sync across devices.
Claim suggestions
Choose how many borderline journeys appear.
Expected-time troubleshooting
TfL's eligibility rules stay the same.
Personalised savings
Add your date of birth to see whether an age-based Railcard could reduce eligible off-peak fares.
Used only for your savings estimate. Select the discount actually registered on each Oyster card. Fare values alone are not enough to detect it reliably because caps, zones and concessions overlap.
Automatic tracking
Automatic tracking
Forward TfL emails to update claim outcomes automatically. Oyster exports can also import journeys.
Network status
Live network status
Live TfL disruptions across the Tube, DLR, Overground and Elizabeth line. It refreshes on its own, and any journey that overlaps a logged disruption gets flagged in your results table.
Insights and trends
Travel snapshot
Across the journeys in your current view.
Advanced insights
PlusTravel time
Minutes travelled, split by peak and off-peak starts.
Time by service
Where your recorded travel time was spent.
Peak estimates use weekday TfL time bands. Railcard figures are indicative: standard discounts use off-peak Oyster fares, while Disabled Persons Railcard estimates include peak travel. Daily caps and route-specific exclusions can change the final amount.
Claim status
Screening result for the selected period.
Delay trend
Calculated delay by journey date.
Money back by month
Successful refunds in the selected period.
Largest calculated delays
Top journeys with a usable baseline.
Your journeys
Expected times are saved and reused. We only check new or changed journeys.
Filter journeys Action needed
| Date | Journey | Time | Delay | Eligibility | Claim status | Actions |
|---|
Add a journey manually
Add a journey manually
Useful when copied statement formatting is awkward.
Advanced: expected-time corrections
Expected journey times
Automatic estimates are saved and reused. Only correct a time when you know the suggested route is wrong.
Backups & data
Journeys are saved on this device. Sign in to sync them across devices.
Independent delay screening
TfL Refund Dashboard
Check Tube, DLR, London Overground and Elizabeth line journeys for delays that may qualify for a TfL Service Delay Refund. Import locally for free, then decide what to submit.
You control exactly what you share
We never ask for your TfL password and never log in to your TfL account. Stay signed out for browser-only analysis, or create an account when you want secure sync.
1. Check journeys privately
Upload or paste a statement and we analyse it in your browser. While signed out, your journey data stays on that device.
2. Sign up to save & sync
Create a free account with an email when you want your journeys and claim statuses available across devices.
3. Add automatic tracking
Paid plans can import Oyster journey emails and match forwarded TfL claim outcomes without accessing your mailbox.
How it works
Bring your journeys
Download your journey history from TfL (CSV for Oyster, PDF for contactless) and import it here. Paid Oyster plans can also import forwarded journey exports automatically.
Check calculated delays
We estimate the expected route time using TfL journey data and compare it with your recorded trip, including any logged service disruption that overlaps the journey.
Review and submit to TfL
Open TfL's official Service Delay Refund form from a candidate journey and use the details shown here. TfL makes the final eligibility decision and pays any refund directly.
Keep outcomes organised
Update claim statuses yourself, or forward TfL outcome emails on a paid plan so matching journeys are updated automatically.
Practical TfL refund guides
Plain-English guidance on the rules, the data you can import and what each dashboard result means.
TfL delay refund rules
Understand the 15- and 30-minute thresholds, deadlines and common exclusions before you claim.
Read the eligibility guideImport journey history
Choose the right Oyster CSV or contactless PDF and avoid the most common import problems.
Follow the import guideUnderstand your results
See how expected times, known disruptions and claim suggestions are calculated and limited.
Read the methodology guideTrack a refund claim
Keep submitted, approved, rejected and paid claims organised without losing the underlying journey.
Read the claim guidePlans
Use the core dashboard free. Paid plans add longer history, ad-free use and automatic email tracking.
Free
Check recent journeys and manage claims yourself, with optional account sync.
- Import Oyster / contactless statements
- Automatic expected journey times
- Delay detection & refund candidates
- Live network status & disruption flags
- 7 days of journeys and travel insights
- Browser-only use or optional secure account sync
- Occasional ads when available
- You track claim outcomes yourself
Base
Thirty days of history with automatic tracking for one Oyster card.
- Everything in Free
- No ads
- Automatic tracking for 1 Oyster card
- Automatic claim status updates by forwarding TfL emails
- Automatic journey import by email (Oyster only)
- 30-day travel insights and delay totals
- Up to 5 cards
- Email alerts for new claims
Plus Most popular
Unlimited history and automatic tracking across multiple cards.
- Everything in Base
- Automatic tracking for up to 5 cards / Oysters
- Overcharge & incomplete-journey detection to catch max fares from missed tap-outs
- Email notifications when you have claims ready to submit
- Advanced reliability and Railcard savings insights
- Priority support
- Claim status updates (all cards): forward TfL's refund result emails and we match each one to your journey by its reference and mark it approved, credited or unsuccessful.
- Automatic journey import (Oyster only): set TfL to email your Oyster journey history and we import those journeys for you. TfL does not provide email journey exports for contactless, credit or debit cards, so those are imported manually from the PDF.
Support this project
This tool is free and runs on a shoestring. If it has put money back in your pocket, a small tip covers the hosting and keeps it free for everyone.
Buy me a coffee
One-off tips of any size mean a lot and go straight towards the AWS bill that powers the live TfL tracking.
Would rather upgrade? See the Plans tab for ad-free use and automatic claim tracking.
Help & FAQ
Get your journey history out of TfL and into this dashboard in a few steps, plus answers to the questions we hear most.
Getting your TfL journey history
Sign in to your TfL account
Go to account.tfl.gov.uk/my-account and sign in with the account that holds the Oyster or contactless card you travel with.

View your journey history
Open your Oyster or Contactless card from the account dashboard, then under Journeys select View journey history.

Pick a date range
Choose the date range you want to check (for example the last seven days) and submit.

Download the right format for your card
Oyster card: download the CSV. It includes the exact start and end tap times we need.
Contactless / credit or debit card: download the PDF. The contactless CSV does not include the full start and end times of each journey, so the PDF is required for an accurate delay calculation.
Then open Add journeys here and drop the file in; duplicates are skipped automatically.

Go to Service delay refunds
Back in your TfL account, select Service delay refunds in the My Account menu for your chosen Oyster or contactless payment card.

Claim using the details from this dashboard
For each likely eligible journey, select Start TfL claim to open TfL's Service Delay Refund form, then use the journey details shown here.

FAQ
Is my data private?
Yes. If you stay signed out, your journeys never leave your browser, we store nothing on our servers. Sign up with an email and we save them to a private record tied to your account so they sync across your devices. The public demo ships with sample data only, never anyone's real journeys.
What counts as a refundable delay?
TfL offers a Service Delay Refund when your journey was delayed 15 minutes or more on the Tube or DLR, or 30 minutes or more on the Elizabeth line or London Overground. You must claim within 28 days.
How is the "expected" time worked out?
Expected times are checked automatically using the journey date, departure time and service, then saved for reuse. If a route cannot be identified safely, we ask you to review it instead of guessing.
What do the disruption flags mean?
A scheduled job records TfL line disruptions every few minutes. If a journey overlaps a logged issue on its line, we show the disruption beside that trip. Worth trying follows your suggestion level: Strict starts at 14 minutes for Tube/DLR or 28 minutes for Overground/Elizabeth line, Normal at 12 or 25 minutes, and Lenient at 10 or 20 minutes. TfL's official thresholds remain 15 and 30 minutes.
Should I use CSV or PDF?
For an Oyster card, use the CSV. It lists exact start and end tap times. For a contactless or credit/debit card, use the PDF: the contactless CSV omits the full start and end times of each journey, so only the PDF gives an accurate delay calculation.
Will importing the same statement twice duplicate journeys?
No. A journey is treated as a duplicate when the card, date, route and both tap times match an existing one, so re-importing is safe.
Does this guarantee a refund?
No. We highlight journeys that may qualify and explain what still needs checking. TfL uses its own timetable and operational records when deciding a claim.
Contact support
Found a problem, need help with an import, or want to make a privacy request?
Email support