Feed status · checked 2026-08-01
Nottingham City Transport
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Nottingham, 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 9 hours ago; last changed 9 hours 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
Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Block trips with overlapping stop times (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +18 points in its category
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
2171 of 2171 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
10549 of 10549 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
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
- Block trips with overlapping stop times (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- 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
- 2171 of 2171 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
- 10549 of 10549 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
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.
Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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_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.
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 84 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 6 kinds of issue across 388 instances (28 error, 360 warning, 0 informational).
Service data covers the next 84 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.
2 accessibility depth signals
13 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (28, 30, 35, 35A, 35B, and more).
Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.
302 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Barnstone, Main Rd East", "Barnstone, Main Rd West", "Cropwell Bishop, Church St", 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 2171 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.
- 833 (white)
- 1 (black)
- 10 (green)
- 10A (white)
- 10C (green)
- 11 (green)
- 11C (green)
- 12 (white)
- 12C (white)
- 12E (white)
- 15 (brown)
- 16 (brown)
- 17 (brown)
- 1A (black)
- 1B (black)
- 1E (white)
- 25 (white)
- 25B (white)
- 26 (white)
- 26A (white)
- 26B (white)
- 27 (white)
- 28 (pink)
- 30 (pink)
- 34 (orange)
- 34C (white)
- 35 (orange)
- 35A (orange)
- 35B (orange)
- 36 (orange)
- 36U (orange)
- 39 (teal)
- 40 (teal)
- 40A (white)
- 40B (teal)
- 41 (teal)
- 42 (teal)
- 43 (red)
- 44 (red)
- 44A (red)
- 45 (teal)
- 45B (white)
- 48 (black)
- 48A (black)
- 49 (black)
- 49A (white)
- 49B (white)
- 49X (black)
- 5 (green)
- 53 (gray)
- 53B (gray)
- 54 (white)
- 55 (white)
- 55A (white)
- 56 (yellow)
- 56A (white)
- 58 (yellow)
- 58A (white)
- 59 (yellow)
- 5A (white)
- 6 (green)
- 60 (white)
- 61 (white)
- 68 (yellow)
- 68A (yellow)
- 68B (yellow)
- 69 (yellow)
- 69A (yellow)
- 69B (yellow)
- 7 (green)
- 70 (yellow)
- 70B (yellow)
- 71 (yellow)
- 71B (yellow)
- 77 (teal)
- 77C (teal)
- 78 (teal)
- 79 (teal)
- 79B (teal)
- 8 (green)
- 87 (purple)
- 88 (purple)
- 89 (purple)
- 89A (purple)
- 9 (green)
- 90 (white)
- 901 (teal)
- 903 (teal)
- 90B (white)
- 9B (green)
- A2 (gray)
| Route | Type | Line color |
|---|---|---|
| 833 | Bus | white |
| 1 | Bus | black |
| 10 | Bus | green |
| 10A | Bus | white |
| 10C | Bus | green |
| 11 | Bus | green |
| 11C | Bus | green |
| 12 | Bus | white |
| 12C | Bus | white |
| 12E | Bus | white |
| 15 | Bus | brown |
| 16 | Bus | brown |
| 17 | Bus | brown |
| 1A | Bus | black |
| 1B | Bus | black |
| 1E | Bus | white |
| 25 | Bus | white |
| 25B | Bus | white |
| 26 | Bus | white |
| 26A | Bus | white |
| 26B | Bus | white |
| 27 | Bus | white |
| 28 | Bus | pink |
| 30 | Bus | pink |
| 34 | Bus | orange |
| 34C | Bus | white |
| 35 | Bus | orange |
| 35A | Bus | orange |
| 35B | Bus | orange |
| 36 | Bus | orange |
| 36B | Bus | white (no shape in feed) |
| 36U | Bus | orange |
| 39 | Bus | teal |
| 4 | Bus | black (no shape in feed) |
| 40 | Bus | teal |
| 40A | Bus | white |
| 40B | Bus | teal |
| 41 | Bus | teal |
| 42 | Bus | teal |
| 43 | Bus | red |
| 44 | Bus | red |
| 44A | Bus | red |
| 45 | Bus | teal |
| 45B | Bus | white |
| 48 | Bus | black |
| 48A | Bus | black |
| 49 | Bus | black |
| 49A | Bus | white |
| 49B | Bus | white |
| 49X | Bus | black |
| 5 | Bus | green |
| 53 | Bus | gray |
| 53B | Bus | gray |
| 54 | Bus | white |
| 55 | Bus | white |
| 55A | Bus | white |
| 56 | Bus | yellow |
| 56A | Bus | white |
| 58 | Bus | yellow |
| 58A | Bus | white |
| 59 | Bus | yellow |
| 5A | Bus | white |
| 6 | Bus | green |
| 60 | Bus | white |
| 61 | Bus | white |
| 68 | Bus | yellow |
| 68A | Bus | yellow |
| 68B | Bus | yellow |
| 69 | Bus | yellow |
| 69A | Bus | yellow |
| 69B | Bus | yellow |
| 7 | Bus | green |
| 70 | Bus | yellow |
| 70B | Bus | yellow |
| 71 | Bus | yellow |
| 71B | Bus | yellow |
| 77 | Bus | teal |
| 77C | Bus | teal |
| 78 | Bus | teal |
| 79 | Bus | teal |
| 79B | Bus | teal |
| 8 | Bus | green |
| 87 | Bus | purple |
| 88 | Bus | purple |
| 89 | Bus | purple |
| 89A | Bus | purple |
| 9 | Bus | green |
| 90 | Bus | white |
| 901 | Bus | teal |
| 903 | Bus | teal |
| 90B | Bus | white |
| 9B | Bus | green |
| A2 | Bus | gray |
List every stop
- Loughborough Endowed Schs
- Gordon Road
- Thomas Cook Place
- Gordon Road
- Aumberry Gap
- Sparrow Hill
- The Greyhound
- The Greyhound
- Loughborough Station, stand A
- Sparrow Hill
- Loughborough Station, stand C
- Loughborough, Baxter Gate BA
- Loughborough Station, stand D
- Meadow Lane
- Kegworth, Market Place
- Hollands Way
- Borough Street
- Nottingham Road
- Frederick Avenue
- Mill Lane
- Anchor Inn
- Anchor Inn
- Mill Lane
- Cator Lane Top
- Mottram Road
- Mottram Road
- Cator Lane Top
- Cator Lane
- Cator Lane
- High Road, Bridge Avenue
- High Road, Bridge Avenue
- Collin Street
- Ellis Grove
- Wilmot Lane
- Bramcote La, Hallams Lane
- Sandby Court
- Oak Acre
- Gt Hogget Drive
- Cator La, Greenwood Court
- Chilwell, Blandford Rd
- Wentworth Road
- Valley Road
- Eskdale Drive
- Caldbeck Court
- Kirkbride Court
- Field La, Burton Drive
- Jessamine Court
- Field Lane, School Lane
- Resource Centre
- City Road
- Rivergreen Crescent
- Deddington Lane
- Eyam Close
- Eyam Close
- Rivergreen Crescent
- Hall Drive
- Trowell Road
- Deddington Lane
- Greenwood Court
- Bramcote Avenue
- Humber Road
- Salthouse Lane
- Salthouse Lane
- Humber Road
- Marlborough Road
- Beeston Interchange bay 1
- Beeston Interchange bay 4
- Norman Close
- Marwood Road
- Carlton Square
- Belper Avenue
- Belper Avenue
- Alpine Crescent
- Alpine Crescent
- Cemetery
- Cemetery
- Carlton Square
- Carlton Square
- Manor Green Walk
- Manor Green Walk
- Manor Crescent
- Manor Crescent
- Burton Road, Ousebridge Drive
- Burton Road, Ousebridge Drive
- Burton Close
- Carlton Square
- Marwood Road
- Huckerby's Field
- Coningswath Rd Bottom
- Coningswath Rd Bottom
- Huckerby's Field
- Burton Close
- Fraser Crescent
- Florence Road
- Chesterfield Street
- Chesterfield Street
- Southcliffe Road
- Carlton, Tesco
- Tesco
- Burton Avenue
- Hillview Road
- Prospect Road
- Foxhill Road West
- Ernest Road
- Fraser Rd, Marshall Hill Dr
- Arnold Lane, Wykes Avenue
- Arnold Lane, Wykes Avenue
- Ernest Road
- Knight Street
- Knight Street
- Marshall Road
- Lees Road
- Fraser Road
- Valley Rd, Foxhill Rd Central
- Florence Road
- Arnold La Cemetery
- Bakewell Avenue
- Westdale La E, Ramsdale Rd
- Westdale La E, Ramsdale Rd
- Victoria Street
- Westdale La, Digby Av
- Lascelles Avenue
- Hartington Avenue
- Hartington Avenue
- Westdale La, Digby Av
- Victoria Street
- Redland Grove
- Redland Grove
- Gedling Rd, Westdale La E
- Main Rd, Westdale La E
- Tennyson Avenue
- Tennyson Avenue
- Church View
- Church View
- Vale Rd, New Vale Road
- Bakewell Avenue
- St John School
- St John School
- Verona Avenue
- Verona Avenue
- Chaworth Road
- Private Road No. 8
- Burton Joyce, Wheatsheaf Ct
- Lambley Lane
- Lambley Lane
- Besecar Avenue
- Burton Road, Linden Grove
- Burton Road, Linden Grove
- Carlton-le-Willows School, Turnround
- Nottingham Road
- Nottingham Road
- Woodside Road
- Woodside Road
- Cragmoor Road
- Arnold La Cemetery
- Westfields Lane
- Westfields Lane
- Church Meadow
- Church Meadow
- Hooton Road
- Buntings Lane
- Buntings Lane
- Forester Grove
- 29 Main Street
- Park Avenue
- Paddock Close
- Orchard Drive
- St Wilfrid's Church
- Forester Grove
- Hooton Road
- Newton Road
- Brentcliffe Avenue
- Carlton Hill, Standhill Rd
- Carlton Hill, Standhill Rd
- 25 Main Street
- Second Avenue
- Lascelles Avenue
- Woodboro', St Swithun's Church
- 69 Green Lane
- 43 Green Lane
- 42 Green Lane
- Lambley, The Dumbles
- Holy Trinity Church
- Holy Trinity Church
- Park Avenue
- Second Avenue
- Greenwood Rd, Douglas Av
- Colwick Manor Farm
- Trentdale Road
- Calverton, St Wilfrid's Square
- Chesterfield Drive
- Iona Gardens
- Burton Joyce, Wheatsheaf Ct
- Chesterfield Drive
- Poplars Avenue
- Hillarys
- Netherfield, Victoria Rd Shops
- Netherfield, Victoria Rd Shops
- Chaworth Road
- Private Rd no. 2, Private Rd no. 1
- Hillarys
- Colwick Manor Farm
- Oakdale Rd, Avondale Rd
- Private Rd no. 1, Private Rd no. 2
- Arnold, Front Street stand 2
- Arnold, Front Street stand 5
- Arnold, Front Street stand 6
- Arnold, Front Street stand 7
- Arnold, High Street, ASDA
- High Street Avenue
- Charles Street
- Nottingham Rd, Sainsbury's
- Portland Street
- Daybrook Square
- Brackendale Avenue
- Mellors Road
- St Mary's Close
- Albion Rise
- Patricia Drive
- Surgeys Lane
- Karen Rise
- Walton Road
- Ashdale Road
- Cedar Grove
- Spinningdale
- Killisick, Gleneagles Dr
- Canonbie Close
- Daybrook Square
- Portland Street
- Nottingham Rd, Sainsbury's
- Arnold, Croft Rd
- Spinningdale
- Cedar Grove
- Oakdale Road
- Ashdale Road
- Walton Road
- Karen Rise
- Surgeys Lane
- Patricia Drive
- Albion Rise
- St Mary's Close
- Mellors Road
- Church St, Brackendale Ave
- Cornell Drive
- Coppice Road
- Rolleston Dr, Kiddier Ave
- Rolleston Drive Shops
- Gedling Rd, Rolleston Dr
- Arnold View School
- Friar Tuck
- and 1921 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 55.7 | first check |
| 2026-07-30 | 55.7 | no change |
| 2026-07-31 | 55.7 | no change |
| 2026-08-01 | 55.7 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-07-31.
The feed file was re-published since 2026-07-31 (+40 KB).
What changed inside the export
- Route 901, 903 are new in this export.
- 17 new stops appeared.
Read from the feed file itself, compared with the previous export. A service change is normal; this is a heads-up so nothing disappears silently.
Changed counts
- up 10549 of 10549 trips don't say whether the vehicle is wheelchair accessible. (10408 → 10549) (scorecard_wheelchair_accessible_unknown)
- up Some service calendars have no days of the week switched on. (184 → 226) (service_has_no_active_day_of_the_week)
- up 2171 of 2171 stops don't say whether a wheelchair user can board there. (2154 → 2171) (scorecard_wheelchair_boarding_unknown)
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
11 findings, ordered by severity.
Show every finding
- Error28 instances
Block trips with overlapping stop times (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: block_trips_with_overlapping_stop_times · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning10549 instances
10549 of 10549 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)
- Warning2171 instances
2171 of 2171 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)
- Warning226 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)
- Warning98 instances
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)
Finding code: unused_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning30 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no bus is scheduled to arrive.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning5 instances
On some trips the stops fall along the route line in a different order than the schedule lists.
Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.
Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)
Finding code: stops_match_shape_out_of_order · 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. 1 validator error to resolve. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 1 validator error to resolve.
- Current Met
- Service data covers the next 84 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 30 of 2171 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.
These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.
Clears the Google and Apple Maps four-week coverage bar. This feed has 84 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 28 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
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 52 / 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/nottingham-city-transport/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.