Feed status · checked 2026-07-18
Thames Valley Buses
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Windsor and Maidenhead, United Kingdom.
A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.2, validator 8.0.1.
Measured 3 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: medium.
- Realtime quality was not measured this run. It does not count against the grade.
- The feed was downloaded from the agency's own URL.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team
1312 of 1312 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool
1735 of 1735 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ A default or per-trip field in your export.worth about +15 points in its category
Add feed_info.txt with feed_start_date and feed_end_date to your export.Likely your export tool
feed_info.txt is missing its start/end dates (the file itself is absent) Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
⏱ Two fields, set once in export settings.worth about +15 points in its category
How to make and check these changes
Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Add feed_info.txt with feed_start_date and feed_end_date to your export. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date is in 346 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- No fare information is published in the feed.
- Realtime information
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
Send your vendor a fix request
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
Score by category
The MobilityData validator flagged 4 kinds of issue across 74 instances (0 error, 21 warning, 53 informational).
Service data covers the next 346 days.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
50 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Cranbourne Ave", "Cranbourne Ave", "Eltham Ave, Philbye Road", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.
Not scored yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 1 (white)
- 108 (white)
- 121 (white)
- 122 (white)
- 123 (white)
- 124 (white)
- 125 (white)
- 125A (white)
- 125B (white)
- 127 (white)
- 128 (white)
- 129 (white)
- 150 (white)
- 151 (white)
- 151A (white)
- 156 (white)
- 157 (white)
- 158 (white)
- 16 (white)
- 171 (white)
- 172 (white)
- 194 (white)
- 1A (white)
- 2 (white)
- 227 (white)
- 227A (white)
- 228 (white)
- 5 (white)
- 53 (white)
- 6 (white)
- 7 (white)
- 703 (white)
- 704 (white)
- F10 (white)
| Route | Type | Line color |
|---|---|---|
| 1 | Bus | white |
| 108 | Bus | white |
| 121 | Bus | white |
| 122 | Bus | white |
| 123 | Bus | white |
| 124 | Bus | white |
| 125 | Bus | white |
| 125A | Bus | white |
| 125B | Bus | white |
| 127 | Bus | white |
| 128 | Bus | white |
| 129 | Bus | white |
| 150 | Bus | white |
| 151 | Bus | white |
| 151A | Bus | white |
| 156 | Bus | white |
| 157 | Bus | white |
| 158 | Bus | white |
| 16 | Bus | white |
| 171 | Bus | white |
| 172 | Bus | white |
| 194 | Bus | white |
| 1A | Bus | white |
| 2 | Bus | white |
| 227 | Bus | white |
| 227A | Bus | white |
| 228 | Bus | white |
| 5 | Bus | white |
| 53 | Bus | white |
| 6 | Bus | white |
| 7 | Bus | white |
| 703 | Bus | white |
| 704 | Bus | white |
| F10 | Bus | white |
This feed has 1312 stops.
List every stop
- Johnson & Johnson
- Pinewood Crossroads
- Spooner Place
- Culver Grove
- Remenham Hill Garage
- Coleridge Close
- Coleridge Close
- Old Silk Mill
- Old Silk Mill
- Hurst Road Turn
- Hurst Road Turn
- Wokingham Station Interchange
- Wokingham Station Interchange
- Pond
- Pond
- Emmbrook School
- Waterloo Road
- Winnersh Crossroads
- Winnersh Crossroads
- Woodward Close
- Woodward Close
- Sadlers Lane
- Sadlers Lane
- Simons Lane
- Simons Lane
- Rifle Volunteer
- Rifle Volunteer
- Oxford Road
- Oxford Road
- Holt Lane
- Holt Lane
- Shute End
- Shute End
- Wokingham, Broad Street
- Wokingham, Broad Street
- Seaford Road
- Seaford Road
- Hilton St Annes Hotel
- Hilton St Annes Hotel
- Lowther Road
- Lowther Road
- Toutley Close
- Toutley Close
- Corfield Green
- Corfield Green
- Dog and Duck
- Dog and Duck
- Matthewsgreen Farm
- Matthewsgreen Farm
- Matthewsgreen East
- Matthewsgreen East
- Jubilee Avenue
- Jubilee Avenue
- Milton Court
- Glebelands Road
- Library
- Elms Road
- Wokingham Station
- Wokingham Hospital
- Wokingham Hospital
- Oaklands Drive
- Oaklands Drive
- Molly Millars Close
- Molly Millars Close
- Two Poplars
- Two Poplars
- Luckley Road
- Luckley Road
- Evendons Lane
- Evendons Lane
- Woodcray Manor Farm
- Woodcray Manor Farm
- Handpost Corner
- Handpost Corner
- Pine Drive
- Pine Drive
- Barkham Ride
- Ratepayers Hall
- Finchampstead, California Crossroads
- California Crossroads
- Kiln Ride
- Kiln Ride
- Range Road
- Range Road
- Kings Mere
- Kings Mere
- Kingsbridge Cottages
- Kingsbridge Cottages
- St Sebastians Roundabout
- St Sebastians Roundabout
- Ellis Road
- Ellis Road
- Wokingham Tesco
- Molly Millars Lane
- Molly Millars Lane
- Woosehill, Dorset Way
- Heron Road
- Heron Road
- Northway
- Morrisons
- Morrisons
- Rectory Road
- Osborne Road
- Wiltshire Drive
- Sarum Crescent
- Ashridge Shops
- Norreys Avenue
- Binfield Road
- Barrett Crescent
- Budges Road
- Keephatch Road
- Hughes Road
- Ashridge Road
- Bean Oak Road Shops
- Bean Oak Road Shops
- Proctors Road
- Proctors Road
- The Plough
- The Plough
- Woodley, Chequers
- Woodley, Chequers
- Woodwaye
- Woodwaye
- Beaufield Close
- Beaufield Close
- Chequers Way
- Chequers Way
- Howth Drive Top
- Howth Drive Top
- Hanwood Close
- Hanwood Close
- Western Avenue - Reading Road
- Western Avenue - Reading Road
- Warren Road
- Warren Road
- Ryecroft Close
- Ryecroft Close
- Butts Hill Bridge
- Butts Hill Bridge
- Mustard Lane
- Mustard Lane
- London Road - The Drive
- London Rd - The Drive
- Shepherds House Lane
- Shepherds House Lane
- Earley Power Station
- Earley Power Station
- Shepherds Hill Top
- Shepherds Hill Top
- Sonning Lane
- Sonning Lane
- Sonning Lane
- Holmemoor Drive
- Hawthorn Way
- Hawthorn Way
- Model Farm
- Model Farm
- Milestone Avenue
- Milestone Avenue
- Charvil, Wee Waif
- Charvil, Wee Waif
- Holme Park Farm Lane
- Bluecoat School
- Bluecoat School
- Sonning, High Street
- Sonning, High Street
- Sonning, adj Fire Station
- Fire Station
- Sonning, opp Fire Station
- Little Glebe
- Little Glebe
- Park View Drive
- Carliles Corner West
- Horse and Groom
- Hare Hatch, Grange
- Hare Hatch, Grange
- The Forge
- The Forge
- Castle Royale Golf Club
- Castle Royale Golf Club
- Knowl Hill, Bird In Hand
- Knowl Hill, Bird In Hand
- Old Devil Inn
- Park View Drive South
- Park View Drive South
- Chiltern Drive
- Chiltern Drive
- Waggon and Horses
- Waggon and Horses
- Twyford, Waitrose
- Twyford, Crossroads
- Waitrose
- Church Street
- Wargrave Road
- Twyford Station
- Twyford Station
- Springfield Park
- Springfield Park
- Orchard Estate
- Orchard Estate
- Royal Oak
- Royal Oak
- Northbury Farm Bridleway
- Northbury Farm Bridleway
- Twyford Orchards Caravan Park
- Twyford Orchards Caravan Park
- Loddon Hall Road
- Pennfields
- Northbury Farm Bridleway
- Pennfields
- Longfield Road
- Arnside Close
- Twyford, Amberley Drive
- Ruscombe Turn
- Ruscombe Turn
- Colleton Drive
- Colleton Drive
- Winchcombe Road Foot
- Winchcombe Road Foot
- Burton Close
- Hurst Road
- Dinton Pastures
- Dinton Pastures
- Broadmoor Lane
- Charvil Lane
- Charvil Lane East
- Broad Hinton - Bolwell Close
- Broad Hinton - Bolwell Close
- Broad Hinton Fields
- Broad Hinton Fields
- Burton Close
- Broadwater Lane
- Elephant and Castle
- Elephant and Castle
- Wards Cross
- Wards Cross
- Primary School
- Primary School
- Hurst, School Road South
- School Road South
- Sawpit Road
- Sawpit Road
- Jolly Farmer
- Jolly Farmer
- Davis Street
- Davis Street
- Bluebell Meadow
- Bluebell Meadow
- Robinhood Lane
- Robinhood Lane
- and 1062 more (see the full list on the map or in the GeoJSON)
Over time
This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.
Everything we checked
9 findings, ordered by severity.
Show every finding
- Warning1735 instances
1735 of 1735 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the bus itself can take them.
Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning1312 instances
1312 of 1312 stops don't say whether a wheelchair user can board there.
Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning16 instances
Some service calendars have no days of the week switched on.
Trips tied to these calendars never run; they are dead data that can mask real schedule problems.
Fix: Delete the empty calendars or set their service days. (A few minutes in your scheduling software.)
Validator rule: service_has_no_active_day_of_the_week · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning4 instances
Leading or trailing whitespaces (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'leading_or_trailing_whitespaces' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: leading_or_trailing_whitespaces · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
A file GTFS asks for (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Validator rule: missing_recommended_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt is missing its start/end dates (the file itself is absent)
Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Validator rule: scorecard_missing_feed_info_dates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)
Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info53 instances
Big gap in service (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'big_gap_in_service' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: big_gap_in_service · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Validator rule: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Conformance mark Not yet
This feed is close to the conformance mark. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 346 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Clears the Google and Apple Maps four-week coverage bar. This feed has 346 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.
How this agency maps to the standards
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance. Read the full standards crosswalk.
- Correctness 85 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication.
- Freshness 85 / 100
- GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners.
- Rider experience 38 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality Not yet published
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.
Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.
Cite this record
This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/thames-valley-buses/2026-07-18.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-07-18. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.