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 55% of all tracked agencies and 52% 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 17 minutes ago; last changed 17 minutes 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
115 of 118 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 +24 points
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.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
⏱ A small file for most flat-fare systems.worth about +15 points
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).Likely your export tool
303 of 358 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ Often one default setting in your export.worth about +13 points
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
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.
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. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
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.
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. · Read the fix guide
Make the change. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
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_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). · Read the fix guide
Make the change. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
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 Passio a fix request
This feed is generated by your Passio system. Copy this and send it to your Passio contact; the fixes apply to the route and stop data behind your AVL setup. Each fix names the validator notice and a guide link.
Score by category
The MobilityData validator flagged 5 kinds of issue across 41 instances (0 error, 31 warning, 10 informational).
Service data covers the next 30 days.
3% of stops state wheelchair accessibility (3% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
2% of stops state accessibility (2% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
8 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (BSK, 20, 41, 42, 51, 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.
98 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Avent Ferry at Gorman St (WB)", "Avent Ferry Rd at Avery Close Apt", "Avent Ferry Rd at Brigadoon Dr (NB)", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.
Not scored yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 42 (pink)
- 20 (orange)
- 41 (gray)
- 30 (red)
- 43 (blue)
- 52 (yellow)
- 60 (teal)
| Route | Type | Line color |
|---|---|---|
| 40 Route 40 | Bus | green (no shape in feed) |
| 42 Route 42 | Bus | pink |
| RS RS Lot Shuttle | Bus | yellow (no shape in feed) |
| 20 Route 20 | Bus | orange |
| 50 Route 50 | Bus | purple (no shape in feed) |
| 41 Route 41 | Bus | gray |
| 30 Route 30 | Bus | red |
| 43 Route 43 | Bus | blue |
| 52 Route 52 | Bus | yellow |
| 60 Route 60 | Bus | teal |
| 51 Route 51 | Bus | gray (no shape in feed) |
| FTB Football Shuttle ("Red Terror") | Bus | brown (no shape in feed) |
| BSK Basketball Shuttle ("Red Terror") | Bus | pink (no shape in feed) |
| GRK Greek Football Shuttle ("Greek Terror") | Bus | brown (no shape in feed) |
| RT Red Terror | Bus | red (no shape in feed) |
This feed has 118 stops.
List every stop
- Barbour Dr at Spring Hill Lot
- Dunn Ave at Jeter Dr
- Oval Dr at Main Campus Dr
- Main Campus Dr at Venture Bldgs
- Textiles Complex
- Avent Ferry Rd at Western Blvd (SB)
- Avent Ferry Rd at Centennial Pkwy (SB)
- Varsity Dr at Capability Dr
- Wolf Village (WB)
- Jackson St at Whitmore Dr
- Jackson St at Method Rd
- Ligon St at Method Rd
- Ligon St at Atwater St
- Ligon St at Okelly St
- Sullivan Dr at Admin Services (EB)
- Sullivan Dr at Sullivan Drive Lot
- Dan Allen Dr at Witherspoon
- Dan Allen Dr at Lee Lot
- Hillsborough St at NC State Belltower
- Pullen Rd at Stinson Dr
- Centennial Fringe Lots (1st Shelter)
- Centennial Fringe Lots (2nd Shelter)
- Avent Ferry Rd at Centennial Pkwy (NB)
- Dan Allen Dr at Hodges Lab
- Founders Dr at Nelson Hall
- Hunt Library
- Partners Way at Varsity Dr
- Varsity Dr at Keystone Bldg
- Varsity Dr at Varsity Research Bldg
- Crest Rd at Burt Dr (SB)
- Conifer Dr at Crest Rd (WB)
- Conifer Dr at Gorman St
- Gorman St at Kaplan Dr (WB)
- Gorman St at Kings Ct (SB)
- Avent Ferry Rd at Trailwood Dr (NB)
- Avent Ferry Rd at Trailwood Dr (EB)
- Avent Ferry Rd at Brigadoon Dr (NB)
- Wolf Village (EB)
- Varsity Dr at West Deck (SB)
- Varsity Dr at Marcom St
- Varsity Dr at Avent Ferry Rd
- Varsity Dr at Greek Village Dr
- Events Lot
- Varsity Dr at West Deck (NB)
- Sullivan Dr at Admin Services (WB)
- Gorman St at Jackson St
- Founders Dr at Lampe Dr
- Avent Ferry Rd at Varsity Dr (SB)
- Avent Ferry Rd at Avery Close Apt
- Avent Ferry Rd at Crest Rd (SB)
- Avent Ferry Rd at Brigadoon Dr (SB)
- Avent Ferry Rd at Trailwood Dr (SB)
- Avent Ferry Rd at Gorman St
- Gorman St at Kings Ct (NB)
- Gorman St at Kaplan Dr (EB)
- Gorman St at Conifer Dr
- Conifer Dr at Crest Rd (EB)
- Crest Rd at Burt Dr (NB)
- Crest Rd at Varsity Dr
- Hillsborough St at Brooks Ave
- Hillsborough St at Shepherd St
- Hillsborough St at Meredith College (WB)
- Trinity Rd at Thornberry St
- Carter-Finley Park & Ride
- Westchase Blvd at Blue Ridge Rd
- Centennial Biomedical Campus (SB)
- Hillsborough St at Meredith College (EB)
- Hillsborough St at Turner St
- Hillsborough St at Rosemary St
- Hillsborough St at Friendly Dr
- Morrill Dr at Carmichael Gym
- Morrill Dr at Faucette Dr
- Dan Allen Dr at Dan Allen Deck (NB)
- Sullivan Dr at Lee Lot
- Varsity Dr at McKimmon Center
- Initiative Way at The Greens
- Initiative Way at Wolf Ridge (NB)
- DH Hill Library Platform B
- Avent Ferry Rd at Centennial View Lane
- DH Hill Library Platform A
- Westchase Blvd at The Station
- Hillsborough St at Furches St
- Centennial Biomedical Campus (NB)
- Hillsborough St at Horne St (WB)
- Dan Allen Dr at Dan Allen Deck (SB)
- Dan Allen Dr at Schaub Food Science Bldg
- Greek Way at Avent Ferry Rd
- Engineering II
- Morrill Dr at Cates Ave (NB)
- Hillsborough St at Enterprise St
- Varsity Parking Lot (1st Shelter)
- Varsity Parking Lot (2nd Shelter)
- Gorman St at McKimmon Center
- Greek Village (WB)
- Greek Village (EB)
- Gorman St at Sullivan Dr
- Gorman St at Lexington Dr
- Trinity Rd (Red Terror)
- Cates Ave at Witherspoon Student Center
- Greek Tailgate
- Lenovo Center
- Cates Ave at Jensen Dr
- Dan Allen Dr at Cates Ave
- Avent Ferry Rd at Western Blvd (NB)
- Dan Allen Dr at Western Blvd (NB)
- Dan Allen Dr at Western Blvd (SB)
- Faucette Dr at Dan Allen Dr
- Faucette Dr at Varsity Dr
- Blue Ridge Rd at Trinity Rd (NB)
- Carter Finley Park & Ride (State Fair)
- Faircloth St at Meredith College (SB)
- Faircloth St at Brookwood Dr (NB)
- Bilyeu St at Barbour Dr
- Western Blvd at Morrill Dr (WB)
- Oglethorpe at Westchase
- Avent Ferry at Gorman St (WB)
- Morrill Drive at Cates Avenue (NB)
- Hillsborough St at Faircloth St
Over time
Overall score across the last 20 checks — unchanged since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-19 | 64.6 | first check |
| 2026-06-20 | 64.6 | no change |
| 2026-06-21 | 64.6 | no change |
| 2026-06-22 | 64.6 | no change |
| 2026-06-23 | 64.6 | no change |
| 2026-06-24 | 64.6 | no change |
| 2026-06-25 | 64.6 | no change |
| 2026-06-26 | 64.6 | no change |
| 2026-06-27 | 64.6 | no change |
| 2026-06-28 | 64.6 | no change |
| 2026-06-29 | 64.6 | no change |
| 2026-06-30 | 64.6 | no change |
| 2026-07-01 | 64.6 | no change |
| 2026-07-02 | 64.6 | no change |
| 2026-07-04 | 64.6 | no change |
| 2026-07-05 | 64.6 | no change |
| 2026-07-06 | 64.6 | no change |
| 2026-07-07 | 64.6 | no change |
| 2026-07-08 | 64.6 | no change |
| 2026-07-09 | 64.6 | 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.
The feed file was re-published since 2026-07-08.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
- Warning303 instances
303 of 358 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)
- Warning115 instances
115 of 118 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)
- Warning28 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)
- Warning2 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.)
Agencies here usually clear this within about 1 week (based on 7 observed fixes).
Validator rule: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Route long name contains short name (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'route_long_name_contains_short_name' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)
Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info8 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.)
Agencies here usually clear this within about 1 week (based on 13 observed fixes).
Validator rule: big_gap_in_service · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 instances
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)
NTD certification readiness Needs attention
This feed is close to NTD-ready. Service data runs out in 30 days; renew before you certify.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Needs attention
- Service data runs out in 30 days; renew before you certify.
- 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.
- shapes.txt covers your trips Ready
- All 358 trips have a shape in shapes.txt.
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. Service data runs out in 30 days; renew to qualify. States wheelchair access on 2% of stops and 15% 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 2% of stops and 15% 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.
- 28 of 118 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 540 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
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 85 / 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 50 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 48 / 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-2245/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.