GTFS Scorecard
← All agencies

Feed status · checked 2026-07-18

Coach Services

Based on the feed this agency publishes

Service mode Bus

54.5 / 100

First scorecard for this agency

Catalogued in Norfolk, United Kingdom.

Covers 368 daysAccessibility gapsRealtime not yet published

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

Fix 01

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 +12 points in its category

Fix 02

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

655 of 655 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

Fix 03

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

310 of 310 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

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.

  1. 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.

  2. 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.

  3. 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 368 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

Correctness49.2 / 100

The MobilityData validator flagged 9 kinds of issue across 162 instances (5 error, 128 warning, 29 informational).

Freshness85.0 / 100

Service data covers the next 368 days.

Rider experience37.5 / 100

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.

Accessibility0 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

1 accessibility depth signal

  • 70 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Norwich, St Stephens Square", "Norwich City Centre, St Stephens Street", "Norwich City Centre, St Stephens Street", 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.

Realtime qualityNot yet measured

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 data

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

  • 332 (white)
  • 357 (white)
  • 358 (white)
  • 37A (white)
  • 37D (white)
  • 37E (white)
  • 37T (white)
  • 401 (white)
  • 411 (white)
  • 80 (white)
  • 80A (white)
  • 81 (white)
  • 84 (white)
  • 86 (white)
  • 86A (white)
  • 88 (white)
  • 89 (white)
  • 90 (white)
  • HL1 (white)
  • T1 (white)
  • T2 (white)
  • T3 (white)
Routes in Coach Services's feed
RouteTypeLine color
332Buswhite
357Buswhite
358Buswhite
37ABuswhite
37DBuswhite
37EBuswhite
37TBuswhite
401Buswhite
411Buswhite
80Buswhite
80ABuswhite
81Buswhite
84Buswhite
86Buswhite
86ABuswhite
88Buswhite
89Buswhite
90Buswhite
HL1Buswhite
T1Buswhite
T2Buswhite
T3Buswhite

This feed has 655 stops.

List every stop
  • Ashwellthorpe, New Road
  • Ashwellthorpe, village shop
  • Ashwellthorpe, village shop
  • Ashwellthorpe, New Road
  • Ashwellthorpe, White Horse
  • Ashwellthorpe, White Horse
  • Attleborough, Queens Square
  • Attleborough, Dodds Road
  • Attleborough, Industrial Estate
  • Attleborough, Phoenix Way
  • Attleborough, Phoenix Way
  • Attleborough, Mill Lane
  • Attleborough, Edenside Drive
  • Attleborough, Mill Lane
  • Attleborough, Brickfield Terrace
  • Attleborough, Brickfield Terrace
  • Attleborough, high school
  • Attleborough, high school
  • Attleborough, Leys Lane
  • Attleborough, Bleinham Drive
  • Attleborough, Ollands Road
  • Attleborough, West Carr Road
  • Attleborough, Dodds Road
  • Attleborough, Short Road
  • Attleborough, Queens Road
  • Attleborough, Cyprus Road
  • Attleborough, Rosecroft Primary School
  • Attleborough, Watling Road
  • Attleborough, Lavender Close
  • Attleborough, Dodds Road
  • Attleborough, police station
  • Attleborough, St Edmunds Gate
  • Banham, Grey's Manor
  • Banham, Grey's Manor
  • Banham Zoo, Zoo
  • Banham, Phone Box
  • Banham Zoo, Zoo
  • Banham, school
  • Banham, Phone Box
  • Banham, school
  • Bracon Ash, School Road
  • Bracon Ash, School Road
  • Mulbarton, Roundabout
  • Mulbarton, Roundabout
  • Bressingham, Church
  • Bressingham, Church
  • Bressingham, Gardens
  • Bressingham, Gardens
  • Bridgham, Bus Shelter
  • Bridgham, Bus Shelter
  • New Buckenham, Green
  • New Buckenham, Green
  • Old Buckenham, High School
  • Old Buckenham, Country Park
  • Old Buckenham, Country Park
  • Bridgham, Chapel Lane
  • Bridgham, Chapel Lane
  • Brettenham, Post Box
  • Old Buckenham, Green
  • Old Buckenham, St Andrews Close
  • Old Buckenham, St Andrews Close
  • Bunwell, Hall Road
  • Bunwell, Hall Road
  • Bunwell, Post Office
  • Caston, Caston Primary School
  • Carleton Rode, Bus Shelter
  • Carleton Rode, Flaxlands
  • Cringleford, Interchange
  • Caston, Attleborough Road
  • Caston, Green
  • Crimplesham, Market Lane
  • Crimplesham, Main Road
  • Crimplesham, Market Lane
  • Crimplesham, Main Road
  • Cringleford, Interchange
  • West Dereham, Church Road junction
  • West Dereham, Bath Road
  • West Dereham, Village Hall
  • West Dereham, Bath Road
  • Diss, Roydon Road
  • Diss, Bus Station
  • Diss, Roydon Road
  • Diss, Taylor Road
  • Diss, Taylor Road
  • Downham Market, Hillcrest
  • Downham Market, Hillcrest
  • Downham Market, High School
  • Feltwell, Post Office
  • Feltwell, Paynes Lane
  • Feltwell, Bell Street
  • Feltwell, Paynes Lane
  • Feltwell, St John`s Way
  • Feltwell, St John`s Way
  • Feltwell, High Street
  • Forncett End, Jolly Farmers
  • Forncett End, Jolly Farmers
  • Griston, Longmeadow Close
  • Griston, Longmeadow Close
  • Griston, Church
  • Griston, Church
  • East Harling, Market Place
  • East Harling, Jubilee Avenue
  • East Harling, Jubilee Avenue
  • East Harling, Kerridges
  • East Harling, Kerridges
  • East Harling, Hambling`s Piece
  • East Harling, Hambling`s Piece
  • East Harling, Park Court
  • East Harling, Brewsters
  • East Harling, Pound Corner
  • East Harling, Market Place
  • East Harling, Pound Corner
  • Great Hockham, green
  • Great Hockham, green
  • Hockwold, Bus Shelter
  • Hockwold, Bus Shelter
  • Hockwold, Nursery Lane
  • Hockwold, Nursery Lane
  • Hockwold, Malt Lane
  • Hockwold, Malt Lane
  • Kenninghall, Post Office
  • Kenninghall, Post Office
  • Kenninghall, School Close
  • Kenninghall, School Close
  • Keswick, Low Road
  • Keswick, Low Road
  • King's Lynn, Mount Street
  • King's Lynn, Mount Street
  • King's Lynn, Extons Road
  • King's Lynn, Extons Road
  • King's Lynn, Thomas Street
  • King's Lynn, Thomas Street
  • King's Lynn, Southgate Street
  • King's Lynn, Southgate Street
  • King's Lynn, McDonalds layby
  • King's Lynn, Transport Interchange
  • King's Lynn, Cemetery Lodge
  • King's Lynn, Cemetery Lodge
  • King's Lynn, College of West Anglia
  • King's Lynn, Hardwick Tesco
  • King's Lynn, Hardwick Tesco
  • King's Lynn, St Katherines Court
  • King's Lynn, Kettlewell Lane
  • North Lopham, The Green
  • North Lopham, The Green
  • South Lopham, War Memorial
  • South Lopham, War Memorial
  • Methwold, Stoke Road
  • Brookville, Old Post Office
  • Methwold, Church
  • Methwold, High School
  • Methwold, Church
  • Methwold, Herbert Drive
  • Methwold Hythe, chapel
  • Brookville, Old Post Office
  • Methwold, Cross
  • Methwold, Stoke Road
  • Methwold Hythe, chapel
  • Methwold, Herbert Drive
  • Mulbarton, Birchfield Gardens
  • Mulbarton, Bluebell Road
  • Mulbarton, Birchfield Lane
  • Mulbarton, Worlds End
  • Mulbarton, Worlds End
  • Mulbarton, Birchfield Lane
  • Mulbarton, Lark Rise
  • Mulbarton, The Common
  • Mulbarton, Rectory Lane
  • Mulbarton, Lark Rise
  • Mundford, Old School
  • Mundford, Old School
  • Northwold, Church
  • Northwold, Chapel
  • Northwold, Little London Lane
  • Northwold, West End
  • Northwold, Chapel
  • Northwold, Church
  • Whittington, Bus Shelter
  • Whittington, Christ Church
  • Whittington, Christ Church
  • Whittington, Bus Shelter
  • Norwich City Centre, St Stephens Street
  • Norwich City Centre, St Stephens Street
  • Norwich City Centre, Castle Meadow
  • Norwich, St Stephens Square
  • Norwich City College, Campus
  • Norwich City College, Campus
  • Norwich, Railway Station
  • Norwich, Railway Station
  • Norwich, St Stephens Square
  • Tuckswood, Sandy Lane
  • Tuckswood, Sandy Lane
  • Norwich, Brunswick Road
  • Norwich, Brunswick Road
  • Norwich, Eagle Walk
  • Norwich, Eagle Walk
  • Norwich, Albemarle Road
  • Norwich, Town Close Road
  • Norwich, Lime Tree Road
  • Norwich, Albemarle Road
  • Norwich, Leopold Road
  • Norwich, Lime Tree Road
  • Norwich, Leopold Road
  • Norwich, Branksome Road
  • Norwich, Branksome Road
  • Norwich, Judges Walk
  • Norwich, Judges Walk
  • Norwich, Elveden Close
  • Norwich, Elveden Close
  • Tuckswood, Robin Hood Road
  • Tuckswood, Robin Hood Road
  • Tuckswood, Bessemer Road
  • Tuckswood, Bessemer Road
  • Tuckswood, Fountains Road
  • Tuckswood, Fountains Road
  • Norwich, Ipswich Grove
  • Norwich, Ipswich Grove
  • Norwich City Centre, Castle Meadow
  • South Tuckswood, Marsh Harrier Inn
  • South Tuckswood, Marsh Harrier Inn
  • Norwich City Centre, Bus Station
  • Roydon, Village Hall
  • Roydon, Copeman Road
  • Roydon, Village Hall
  • Roydon, Copeman Road
  • West Winch, Esso Garage
  • Bexwell, Bexwell Lane
  • Bexwell, Bexwell Lane
  • Shelfanger, bus shelter
  • Shelfanger, bus shelter
  • Shouldham Thorpe, The Jolly Brewers
  • Shouldham Thorpe, The Jolly Brewers
  • Setchey, Old Garage Layby
  • Stoke Ferry, Bus Shelter
  • Stoke Ferry, Bus Shelter
  • Stoke Ferry, School
  • Stoke Ferry, Boughton Road
  • Stoke Ferry, Boughton Road
  • Stoke Ferry, Furlong Road
  • Stoke Ferry, Oak Road
  • Stoke Ferry, Furlong Road
  • Stoke Ferry, Oxborough Road
  • Stoke Ferry, Oxborough Road
  • Stow Bedon, Mere Road
  • Stow Bedon, Mere Road
  • Stradsett, Rose's Wood Layby
  • Stradsett, Rose's Wood Layby
  • Stradsett, The Foldgate
  • Stradsett, The Foldgate
  • Swardeston, Bus Shelter
  • and 405 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

14 findings, ordered by severity.

Show every finding
  • Error5 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.)

    Validator rule: block_trips_with_overlapping_stop_times · See MobilityData GTFS Validator rules

  • Warning655 instances

    655 of 655 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

  • Warning310 instances

    310 of 310 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

  • Warning51 instances

    Some scheduled trips move faster between stops than a bus can.

    Usually a typo'd stop time; riders get arrival times no bus can meet.

    Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)

    Validator rule: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning25 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

  • Warning25 instances

    Some stops sit far from the route line they belong to.

    Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.

    Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)

    Validator rule: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning18 instances

    Some service calendars in the feed have already ended.

    Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.

    Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)

    Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning5 instances

    Stops match shape out of order (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'stops_match_shape_out_of_order' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Validator rule: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules

  • Warning3 instances

    Stop has too many matches for shape (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'stop_has_too_many_matches_for_shape' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Validator rule: stop_has_too_many_matches_for_shape · See MobilityData GTFS Validator rules

  • 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

  • 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

  • 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

  • Info29 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

  • 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

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 368 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 368 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 5 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 49 / 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.

Coach Services GTFS data quality grade: F

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/coach-services-thetford/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.