Prep for a call: printable one-page brief · For your board packet: printable one-pager · Compare with another agency · Watch this feed: get an email before it expires
Feed status · checked 2026-07-09
North Carolina State University (NCSU)
Based on the feed this agency publishes
unchanged since 2026-07-08
Ahead of 27% of all tracked agencies and 27% of mid-size agencies. Operates in North Carolina.
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.1, validator 8.0.1.
Checked for changes 3 hours ago; last changed 8 days ago.
Top things to fix
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.Likely your export tool
Service data ended 2200 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points
Agencies here usually clear this within about 1 week (based on 18 observed fixes).
Review the rule documentation for 'missing_required_column' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Missing required column (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 points
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
114 of 114 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
Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. · Read the fix guide
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Review the rule documentation for 'missing_required_column' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. · Read the fix guide
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. 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. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Send Trillium a fix request
This feed is produced and hosted by Trillium. Copy this and send it to your Trillium contact; they make the change and republish the feed. Each fix names the validator notice and a guide link.
Send the agency a note
Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.
Score by category
The MobilityData validator flagged 9 kinds of issue across 92 instances (2 error, 54 warning, 36 informational).
Service data ended 2200 day(s) ago. Trip planners have likely already dropped this feed.
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 published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
Fares are applied to trips.
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.
- 7R (red)
- 6 (red)
- 7 (red)
- 8 (red)
- 2 (red)
- 4 (red)
| Route | Type | Line color |
|---|---|---|
| 9S Gorman Street | Bus | red (no shape in feed) |
| 16 Werewolf Shuttle | Bus | red (no shape in feed) |
| 1 Avent Ferry | Bus | red (no shape in feed) |
| 10 Centennial | Bus | red (no shape in feed) |
| 11 Village Link | Bus | red (no shape in feed) |
| 7R Wolflink Reverse | Bus | red |
| 3 Engineering | Bus | red (no shape in feed) |
| 5 Varsity | Bus | red (no shape in feed) |
| 6 Carter Finley | Bus | red |
| 7 Wolflink Shuttle | Bus | red |
| 8 Southeast Loop | Bus | red |
| 9 Gorman Street | Bus | red (no shape in feed) |
| 14 Centennial Night | Bus | red (no shape in feed) |
| 12 Night Wolf | Bus | red (no shape in feed) |
| 6S Hillsborough Street West | Bus | red (no shape in feed) |
| 13 Full Moon | Bus | red (no shape in feed) |
| 17 RS Lot Shuttle | Bus | red (no shape in feed) |
| 2 Spring Hill | Bus | red |
| 4 Centennial Express | Bus | red |
This feed has 114 stops.
List every stop
- Oval Dr at Main Campus Dr
- Trinity Rd at Blue Ridge Rd
- Engineering II (COE)
- Hillsborough St at Furches St
- Varsity Dr at Campus Police
- Cates Ave at Jensen Dr (EB)
- Stinson Dr at Boney Dr (Leazar Hall)
- Stinson Dr at Current Dr (Park Shops)
- Stinson Dr Ext at Yarborough Dr
- Yarborough Dr at Dan Allen Dr (Clark Labs)
- Sullivan Dr at Admin Services (WB)
- Barbour Dr at Spring Hill Lot
- Wolf Ridge at Initiative Way (NB)
- The Greens at Initiative Way
- Initiative Way at Main Campus Dr Lots
- The Greens at Initiative Way (Inbound)
- Hillsborough St at Dixie Trail
- Westchase Blvd at The Station
- Centennial Biomedical Campus at Vet School (SB)
- Centennial Biomedical Campus at Vet School (NB)
- Founders Dr at Nelson Hall
- Scott Hall - Platform B
- Scott Hall - Platform A
- Founders Dr at Lampe Dr (Patterson Hall)
- Stinson Dr at Boney Dr (Brooks Hall)
- Current Dr at Stinson Dr (Lang & Comp Labs)
- Cates Ave at Witherspoon Student Center
- Sullivan Dr at West Lot
- Ligon St at O'kelly St (King Village)
- Ligon St at King Village
- Ligon St at Method Rd (King Village)
- Jackson St at Method Rd (Soccer Field)
- Jackson St at Whitmore Dr (King Village)
- Faucette Dr at Weaver Labs
- Partners Way at Varsity Dr (College of Engineering)
- Varsity Dr at West Deck
- Faucette Dr at Varsity Dr (Butler)
- Dan Allen Dr at Hodges Bldg
- Faucette Dr at Dan Allen Dr (Robertson)
- Yarbrough Dr at Dan Allen Dr (EB)
- Yarborough Dr at Stinson Dr (Broughton Hall)
- Pullen Rd at Stinson Dr (Brooks Hall)
- Cates Ave at Talley Student Center
- Avent Ferry Rd at Centennial Pkwy (Burger King)
- Main Campus Dr at Venture Bldgs
- Varsity Dr at Avent Ferry Rd (Carolyn Apts)
- Avent Ferry Rd at Gorman St (WB)
- Gorman St at Kings Ct (NB)
- Gorman St at Conifer Dr (Parkwood Village Apts)
- Conifer Dr at Crest Rd (Parkwood Village Apts)
- Crest Rd at Burt Dr (Ivy Commons Apts)
- Crest Rd at Varsity Dr (Inbound)
- Varsity Dr at Crest Rd
- Greek Village (Outbound)
- Greek Village (Inbound)
- Varsity Dr at Marcom St
- Varsity Parking Lot (1st shelter)
- Varsity Dr at McKimmon Center (East side)
- Gorman St at Varsity Parking Lot (2nd Shelter)
- Sullivan Dr at Admin Services (EB)
- Varsity Dr at Varsity Research Bldg
- Centennial RS Lots (2nd shelter)
- Crest Rd at Varsity Dr (Outbound)
- Crest Rd at Burt Dr (Outbound)
- Conifer Dt at Crest Rd (Outbound)
- Conifer Dr at Gorman St (Outbound)
- Gorman St at Kaplan Dr (Outbound)
- Gorman St at Kings Ct (SB)
- Varsity Dr at Avent Ferry Rd
- Gorman St at Jackson St (King Village)
- Main Campus Dr at College of Textiles
- Carter-Finley Park and Ride
- Centennial RS Lots (1st shelter)
- Greek Way at Avent Ferry Rd
- Dan Allen Dr at Western Blvd (NB)
- Wolf Village Shelter #1 (WB)
- Dan Allen Dr at Witherspoon Student Center
- Westchase Blvd at Blue Ridge Rd
- Main Campus Dr at Partners II (Southbound)
- Dan Allen Dr at Lee Lot
- Centennial Pkwy at Mission Valley Apartments
- Hunt Library at Partners Way
- Dan Allen Dr at Schaub Food Science Bldg
- Hillsborough St at Meredith College (EB)
- Hillsborough St at Brooks Ave (WB)
- Hillsborough St at Friendly Dr
- Hillsborough St at Horne St (EB)
- Hillsborough St at Enterprise St (NCSU Bell Tower)
- Avent Ferry Rd at Centennial Pkwy (SB)
- Morrill Dr at Carmichael Gym
- Avent Ferry Rd at Western Blvd (Avent Ferry Complex)
- Avent Ferry Rd at Varsity Dr (Carolyn Apts)
- Avent Ferry Rd at Crest Rd
- Avent Ferry Rd at Brigadoon Dr (2nd entr.)
- Avent Ferry Rd at Gorman St (EB)
- Avent Ferry Rd at Trailwood Dr (EB)
- Avent Ferry Rd at Brigadoon Dr (EB)
- Avent Ferry Rd at Centennial View Ln
- Morrill Dr at Cates Ave (NB)
- Hillsborough St at Shepherd St
- Hillsborough St at Meredith College (WB)
- Gorman St at McKimmon Center
- Hillsborough St at Turner St
- Hillsborough St at Rosemary St
- Gorman St at Graduate Ln
- Gorman St at Sullivan Dr
- Avent Ferry Rd at Trailwood Dr (Kensington Apts)
- Dunn Ave at Jeter Dr (Coliseum Parking Deck)
- Morrill Dr at Faucette Dr
- Avent Ferry Rd at Avery Close Apts
- Wolf Ridge at Initiative Way (SB)
- Gorman St at Wolf Village Way
- Wolf Village Shelter #2 (EB)
- Sullivan Dr at Lee Lot
Over time
Overall score across the last 9 checks — unchanged since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-30 | 46.8 | first check |
| 2026-07-01 | 46.8 | no change |
| 2026-07-02 | 46.8 | no change |
| 2026-07-04 | 46.8 | no change |
| 2026-07-05 | 46.8 | no change |
| 2026-07-06 | 46.8 | no change |
| 2026-07-07 | 46.8 | no change |
| 2026-07-08 | 46.8 | no change |
| 2026-07-09 | 46.8 | 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-08.
Same feed file as 2026-07-08; 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.
Everything we checked
- Error2 instances
Missing required column (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_required_column' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: missing_required_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Service data ended 2200 day(s) ago.
When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
Fix: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)
Agencies here usually clear this within about 1 week (based on 18 observed fixes).
Validator rule: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning132 instances
132 of 132 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 (most small-agency fleets are 100% accessible, so this is often a single default). (Often one default setting in your export.)
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning114 instances
114 of 114 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)
- Warning47 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.)
Agencies here usually clear this within about 1 week (based on 11 observed fixes).
Validator rule: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning4 instances
Equal shape distance same coordinates (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'equal_shape_distance_same_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: equal_shape_distance_same_coordinates · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some service calendars in the feed have already expired.
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.)
Agencies here usually clear this within about 1 week (based on 61 observed fixes).
Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
This feed's service calendar runs out within the next 7 days.
When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all.
Fix: Export and publish an updated GTFS feed that covers at least the next 30 days of service. (Usually a re-export from your scheduling software.)
Agencies here usually clear this within about 1 week (based on 16 observed fixes).
Validator rule: feed_expiration_date7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Agencies here usually clear this within about 1 week (based on 31 observed fixes).
Validator rule: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info26 instances
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Validator rule: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info9 instances
Unknown file (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unknown_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Service window outside feed period (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'service_window_outside_feed_period' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 17 observed fixes).
Validator rule: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Beyond the grade
Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.
98 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Oval Dr at Main Campus Dr", "Trinity Rd at Blue Ridge Rd", "Hillsborough St at Furches St", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
Some fixes we can make for you
These are the safe mechanical fixes, applied to a copy of your feed. They change only what is certain and leave everything else untouched. Review the diff before you publish.
Trimmed surrounding whitespace 1 change
For example: 'stop_name': 'Hillsborough St at Friendly Dr ' -> 'Hillsborough St at Friendly Dr'
Run it yourself on your own copy of the feed: scorecard autofix <feed.zip> --out corrected.zip
NTD certification readiness Not ready
Resolve this before you certify on the D-10. 1 validator error to resolve. Service data expired 2200 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 1 validator error to resolve.
- Current Not ready
- Service data expired 2200 days ago, so FTA would find the link out of date.
- agency_id matches your NTD ID Not checked yet
- Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed and confirm it once a year. This box is a heads-up on whether yours looks ready; it is not the official sign-off.
A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). Aligning agency_id with your NTD ID lets the feed line up with your NTD record; the July 2025 final rule links the two on the P-50 form rather than requiring that feed change, and requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.
Conformance mark Not yet
This feed is close to the conformance mark. 1 validator error to resolve. Service data expired 2200 days ago. 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 Not yet
- Service data expired 2200 days ago.
- 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.
- 47 of 114 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.
Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks. The feed also carries 2 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
How this agency maps to the standards
A data-quality lens, not a compliance determination. Each category shows this feed's score and the standards it relates to: the FTA National Transit Database GTFS requirement, the MobilityData grading scheme, and the Google Transit gate. Read the full standards crosswalk.
- Correctness 64 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading: stop locations, route names and colors. Google Transit: a feed must pass validation to stay in Maps.
- Freshness 0 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 60 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: 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 live badge on your agency site or feed README. It updates daily 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/north-carolina-state-university-ncsu-1289/2026-07-09.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-09. Use it in a board packet, an NTD narrative, 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.