Feed status · checked 2026-08-01
Reading Buses
Based on the feed this agency publishes
Service mode Bus
down 0.4 since 2026-07-31
Catalogued in Reading, 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.3, validator 8.0.1.
Checked for changes 71 minutes ago; last changed 5 days ago.
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
1624 of 1624 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
6446 of 6446 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
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- 1624 of 1624 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- 6446 of 6446 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- feed_info.txt is missing its start/end dates (the file itself is absent)
- Next action
- Add feed_info.txt with feed_start_date and feed_end_date to your export.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
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. See this feed's finding-clearance log.
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. See this feed's finding-clearance log.
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. See this feed's finding-clearance log.
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 30 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 2 kinds of issue across 53 instances (0 error, 53 warning, 0 informational).
Service data covers the next 30 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
59 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("St Bernards Convent", "Langley, London Road/High Street", "St Leonards Hill", 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.
This feed has 1624 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 703 (white)
- 1 (white)
- 11 (white)
- 13 (white)
- 14 (white)
- 15 (white)
- 15a (white)
- 16 (white)
- 17 (white)
- 18 (white)
- 19a (white)
- 19b (white)
- 19c (white)
- 2 (white)
- 21 (white)
- 22 (white)
- 23 (white)
- 24 (white)
- 25 (white)
- 25a (white)
- 26 (white)
- 28 (white)
- 28a (white)
- 29 (white)
- 29a (white)
- 2a (white)
- 3 (white)
- 300 (white)
- 33 (white)
- 4 (white)
- 43 (white)
- 4a (white)
- 5 (white)
- 50 (white)
- 500 (white)
- 50a (white)
- 6 (white)
- 600 (white)
- 6a (white)
- 701 (white)
- 702 (white)
- 80 (white)
- 81 (white)
- 82 (white)
- 83 (white)
- 84 (white)
- 85 (white)
- 86 (white)
- 87 (white)
- 88 (white)
- 9 (white)
- 90 (white)
- 91 (white)
- 92 (white)
- 93 (white)
- 9a (white)
- 9b (white)
| Route | Type | Line color |
|---|---|---|
| 703 | Bus | white |
| 1 | Bus | white |
| 11 | Bus | white |
| 13 | Bus | white |
| 14 | Bus | white |
| 15 | Bus | white |
| 15a | Bus | white |
| 16 | Bus | white |
| 17 | Bus | white |
| 18 | Bus | white |
| 19a | Bus | white |
| 19b | Bus | white |
| 19c | Bus | white |
| 2 | Bus | white |
| 21 | Bus | white |
| 22 | Bus | white |
| 23 | Bus | white |
| 24 | Bus | white |
| 25 | Bus | white |
| 25a | Bus | white |
| 26 | Bus | white |
| 28 | Bus | white |
| 28a | Bus | white |
| 29 | Bus | white |
| 29a | Bus | white |
| 2a | Bus | white |
| 3 | Bus | white |
| 300 | Bus | white |
| 33 | Bus | white |
| 4 | Bus | white |
| 43 | Bus | white |
| 4a | Bus | white |
| 5 | Bus | white |
| 50 | Bus | white |
| 500 | Bus | white |
| 50a | Bus | white |
| 6 | Bus | white |
| 600 | Bus | white |
| 6a | Bus | white |
| 701 | Bus | white |
| 702 | Bus | white |
| 80 | Bus | white |
| 81 | Bus | white |
| 82 | Bus | white |
| 83 | Bus | white |
| 84 | Bus | white |
| 85 | Bus | white |
| 86 | Bus | white |
| 87 | Bus | white |
| 88 | Bus | white |
| 9 | Bus | white |
| 90 | Bus | white |
| 91 | Bus | white |
| 92 | Bus | white |
| 93 | Bus | white |
| 9a | Bus | white |
| 9b | Bus | white |
List every stop
- Addiscombe Chase
- Addiscombe Chase
- Albury Gardens
- Albury Gardens
- Aldermaston Station
- Aldermaston Station
- Amners Farm Road
- Amners Farm Road
- Aldworth Road
- Lower Padworth, Avon Way
- Lower Padworth, Avon Way
- AWE Main Gate
- AWE Main Gate
- Beale Park
- Beale Park
- Fernhurst Road
- Fernhurst Road
- Beckfords
- Beech Road
- Beech Road
- Beenham Turn
- Beenham Turn
- Berkshire Arms
- Berkshire Arms
- Birch Lane
- Birch Lane
- Birchwood Road
- Birchwood Road
- Bitterne Avenue
- Blands Court
- Blands Court
- Bourne Road
- Bourne Road
- Bowden Green
- Bowden Green
- Brackenwood
- Brading Way
- Brewery Court
- Brewery Court
- Brooksby Road
- Church Lane
- Church Lane
- Burghfield Road Railway Bridge
- Burghfield Road Railway Bridge
- Calcot Priory
- Calcot Priory
- Calcot, Mill Lane
- Calcot, Mill Lane
- Calcot, Mill Lane
- Calcot Post Office
- Calcot Post Office
- Camp Road
- Camp Road
- Chapel Lane
- Chapel Lane
- Chestnut Drive
- Chestnut Drive
- Purley, Chestnut Grove
- Churchward Walk
- Churchward Walk
- Coachmans Court
- Coachmans Court
- College Piece
- Stephen's Road
- College Piece
- Colthrop Lane
- Colthrop Lane
- Colyton Way
- Colyton Way
- Conway Road
- Conway Road
- Cods Hill
- Cods Hill
- Cresswell Road
- Cresswell Road
- Cromwell Road
- Cromwell Road
- Dark Lane Top
- Dark Lane Top
- Dell Road
- Dell Road
- Denefield School
- Denefield School
- Denefield School INSIDE GROUNDS
- Elm Drive
- Elm Drive
- Fairford Road
- Fairford Road
- Pipers Way Top
- Ferndale Court
- Ferndale Court
- Fir Tree Primary School
- Fir Tree Primary School
- Footpath to Highfield Road
- Footpath to Highfield Road
- Island Farm Road
- Island Farm Road
- Garston Crescent Summit
- Garston Crescent Summit
- Mortimer, Glenapp Grange
- Golf Club West Gate
- Golf Club West Gate
- Goodliffe Gardens
- Goodliffe Gardens
- Goodwood Close
- Goodwood Close
- Green Lane
- Green Lane
- Greenwood Road
- Greenwood Road
- Hallplace Farm
- Hall Place Farm
- Arlington Business Park
- Pangbourne Station
- Pangbourne Station
- Hatch Gate PH
- Hatch Gate PH
- Hawthorn Road
- Hawthorn Road
- Highcroft Kennels
- Highcroft Kennels
- Highwoods lodge
- Highwoods lodge
- Hillfoot Cottages
- Hillfoot Cottages
- Holmdene
- Holmdene
- Hook End Lane
- Hook End Lane
- Kennet Valley School
- Kennet Valley School
- Kettering Close
- Kettering Close
- Upper Basildon, Captains Gorse
- Knollmead
- Knollmead
- Ledbury Drive
- Ledbury Drive
- Little Heath School Grounds
- Little Heath School
- Lower Bowden Farm
- Lower Bowden Farm
- Burghfield, Mans Hill
- Burghfield, Mans Hill
- Mayfield Avenue
- Mayfield Avenue
- Coach and Horses
- Coach and Horses
- Midgham Kennels
- Midgham Kennels
- South Lodge
- South Lodge
- Milehouse Cottages
- Milehouse Cottages
- Langley Hill
- Langley Hill
- Royal Avenue
- Royal Avenue
- New Hill
- New Hill
- Matthews Close
- Matthews Close
- Northridge Bottom Plantation
- Oliver Drive West
- Oliver Drive West
- Clayhill Road Shops
- Clayhill Road Shops
- Dark Lane Foot
- Dark Lane Foot
- Oxford Road
- Oxford Road
- Collins Caravan Centre
- Collins Caravan Centre
- Pangbourne Library
- Pangbourne Police Station
- Primary School
- Primary School
- The George Hotel
- Pangbourne Village Hall
- Park Wall Lane
- Park Wall Lane
- Pemberton Gardens
- Pemberton Gardens
- Purley Hall Gatehouse
- Purley Hall Gatehouse
- Purley on Thames, Sherwood Rise
- Purley on Thames, Sherwood Rise
- Recreation Road
- Recreation Road
- Burghfield Village Hall
- Burghfield Village Hall
- Easter Park
- Easter Park
- Red Lion PH
- Red Lion PH
- The Sun Garage
- The Sun Garage
- Roebuck Rise
- Roebuck Rise
- Roselawn Hotel
- Roselawn Hotel
- Knappswood Close
- Knappswood Close
- Sandown Avenue
- Calcot (Sainsbury's)
- Shaw Road foot
- Shaw Road foot
- Shooters Hill Riverside
- Siege Cross Roundabout
- Siege Cross Roundabout
- Southdown Road
- Sovereign Way
- Sovereign Way
- Springfield
- St John's Church
- St Michaels
- St Pauls School
- Stephen's Close
- London Road Chapel
- London Road Chapel
- The Bull PH
- The Bull PH
- Clayhill Road Turn
- Clayhill Road Turn
- Spring Inn
- Spring Inn
- Sutherland Grove
- Sutherland Grove
- Swanholm Gardens
- Swanholm Gardens
- Talbot Way
- Thatcham, Broadway
- Thatcham, Broadway
- Thatcham Cemetery
- Thatcham Cemetery
- St Stephens Church
- St Stephens Church
- The Bevers
- Burghfield, The Close
- Burghfield, The Close
- Tamarind Tree
- Tamarind Tree
- Cunning Man
- Cunning Man
- West Berkshire Crematorium
- West Berkshire Crematorium
- The Mearings
- The Mearings
- Theale Green School
- Theale Green School
- and 1374 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — down 0.4 since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 48.5 | first check |
| 2026-07-30 | 59.8 | up 11.3 |
| 2026-07-31 | 59.4 | down 0.4 |
| 2026-08-01 | 59.0 | down 0.4 |
What changed since your last check
- Correctness no change
- Freshness down 1.7
- Rider experience no change
What changed in this feed
Overall score fell 0.4 points since 2026-07-31.
Same feed file as 2026-07-31; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
What changed over time
On 2026-07-25 this feed started at grade F. On 2026-07-30 feed renewed to a current calendar. On 2026-08-01 feed entered the expiry window (30 days of service left). As of 2026-08-01 it holds grade F.
A plain-language history of this feed, newest first.
- 2026-08-01 Feed entered the expiry window (30 days of service left).
- 2026-07-30 Feed renewed to a current calendar.
Everything we checked
7 findings, ordered by severity.
Show every finding
- Warning6446 instances
6446 of 6446 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.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning1624 instances
1624 of 1624 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.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning52 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.)
Finding code: 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)
- 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.)
Finding code: 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.)
Finding code: 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.)
Finding code: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices 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.)
Finding code: 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. Service data runs out in 30 days; renew to qualify. 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 Not yet
- Service data runs out in 30 days; renew to qualify.
- 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 30 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 88 / 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 35 / 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/reading-buses/2026-08-01.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-08-01. 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.