GTFS Scorecard
← All agencies

Feed status · checked 2026-08-01

Duke University

Based on the feed this agency publishes

Service mode Bus

41.6 / 100

unchanged since 2026-07-31

Catalogued in North Carolina.

Feed expiredAccessibility gapsFlexible serviceRealtime 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.3, validator 8.0.1.

Checked for changes 79 minutes ago; last changed 41 days ago.

Measured 3 of 4 score categories from the agency's own feed.

How we measured this

Confidence in this measurement: medium.

  • Realtime quality was not measured this run. It does not count against the grade.
  • The feed was downloaded from the agency's own URL.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

Top things to fix

Fix 01

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 356 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 in its category

Fix 02

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

Stop time timepoint without times (flagged by the MobilityData validator). See the linked rule for what this affects.

⏱ Varies.worth about +24 points in its category

Fix 03

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

125 of 127 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

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.

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
Service data ended 356 day(s) ago.
Next action
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.
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.

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

    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. Review the rule documentation for 'stop_time_timepoint_without_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

    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.

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

    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 was 356 days ago.
Published accessibility data
Accessibility information is stated for 1.6% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
Fare information
Fare information is published using GTFS Fares v1.
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 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

Correctness54.0 / 100

The MobilityData validator flagged 8 kinds of issue across 231 instances (152 error, 34 warning, 45 informational).

Freshness0.0 / 100

Service data ended 356 day(s) ago. Trip planners have likely already dropped this feed.

Rider experience57.5 / 100

2% of stops state wheelchair accessibility (2% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.

Accessibility1 / 100

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

2 accessibility depth signals

  • 6 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (H1, H2, LL, H5, SWS, 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.

  • 112 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Swift Ave at Duke University Rd", "Duke University Rd at Swift Ave (EB)", "Imperial Building (215 Morris 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.

FaresLegacy fares

Fares are applied to trips.

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.

This feed has 127 stops.

Skip to route and stop data

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.

  • SWS (purple)
  • CSW (orange)
  • CSF (blue)
  • LL (blue)
  • PR1 (red)
  • H2 (purple)
  • H5 (pink)
  • C1 (red)
  • H1 (teal)
  • C (green)
  • LNC (yellow)
Routes in Duke University's feed
RouteTypeLine color
SWS Swift Avenue ShuttleBuspurple
CSW Smith WarehouseBusorange
CSF C1-Swift WeekendBusblue
LL LaSalle LoopBusblue
PR1 Bassett-ResearchBusred
H2 Hospital LoopBuspurple
H5 Broad-ErwinBuspink
C1 East-WestBusred
H1 HospitalBusteal
C SwiftBusgreen
LNC Lancaster CommonsBusyellow
List every stop
  • Swift Ave at Duke University Rd
  • Duke University Rd at Swift Ave (EB)
  • Imperial Building (215 Morris St)
  • Morreene Rd at Campus Walk Ave (NB)
  • Erwin Rd at Lambeth Cir (Erwin Terraces)
  • Duke University Rd at Chapel Dr (EB)
  • Safeway St at Ninth St
  • Elf St at Elder St
  • Erwin Rd at LaSalle St (WB)
  • Duke St at Main St (Chesterfield Building)
  • Lancaster Commons North
  • Research Dr at Circuit Dr (Genome Research Bldg II)
  • Yearby St. at H Lot (Eastbound)
  • Lancaster Commons South
  • Erwin Rd at Fulton St (VA Hospital)
  • Campus Walk Ave at Campus Walk Apts (EB)
  • Trent Dr at Duke Hospital South (WB)
  • Erwin Rd at Research Dr
  • Fulton St at Pratt St
  • LaSalle St at Bradford Ridge Apts‎
  • Erwin Rd at Lenox Baker Children's Hospital
  • Flowers Dr at Duke Gardens (NB)
  • Morreene Rd at Erwin Rd
  • Morreene Rd at Sherwood Dr (NB)
  • Trent Dr at Duke Hospital South (EB)
  • LaSalle St at Hillsborough Rd (Tire King)
  • LaSalle St at Hillsborough Rd (NB)
  • Erwin Rd at Fulton St (Duke University Hospital)
  • Fulton St at Erwin Rd (Duke Hospital Parking Garage)
  • Towerview Rd at the School of Law
  • Science Dr at Fuqua School of Business (SB)
  • Science Dr at Cameron Blvd (David Thomas Center)
  • Chapel Dr at Duke University Rd (Duke News)
  • Trent Dr at Erwin Rd (Clipp Research Bldg)
  • West Campus Grounds Lot
  • Gilbert-Addoms Westbound
  • East Campus Quad
  • Campus Dr at Maxwell Ave (EB)
  • Campus Dr at Arts Annex (WB)
  • Campus Dr at Arts Annex (EB)
  • Campus Dr at Swift Ave (WB)
  • Campus Dr at Swift Ave (EB)
  • Campus Dr at Nasher (Westbound)
  • Campus Dr at Central Campus (Eastbound)
  • Campus Dr at Anderson St (Westbound)
  • Campus Dr at Anderson St (Eastbound)
  • Campus Dr at Chapel Circle (EB)
  • Campus Dr at Chapel Circle (Admissions)
  • West Campus Chapel (Abele Quad)
  • Towerview Rd at Sanford PPS (Public Policy)
  • Science Dr at Duke Law School
  • Science Dr at Sanford School of Public Policy
  • Science Dr at Biological Sciences Bldg (Southbound)
  • Research Dr at GSRB 2 (Northbound)
  • Science Drive Circle
  • Research Dr at Hudson Hall
  • Research Dr at Duke Clinic
  • Trent Dr at School of Nursing (Southbound)
  • Flowers Dr at Trent Hall (SB)
  • Flowers Dr at Trent Hall (NB)
  • Research Dr at Erwin Rd (Eye Center Garage)
  • Parking Garage 3 at Duke North Pavilion
  • Research Dr at LSRC Building (SB)
  • Research Dr at Nanaline Duke Bldg (NB)
  • Circuit Dr at Circuit Lot (Westbound)
  • Circuit Dr at LaSalle (Circuit Lot Eastbound)
  • Yearby Ave at H Lot (Westbound)
  • Yearby Ave at Anderson St
  • Anderson St at Mill Village
  • Anderson St at Lewis St
  • Alexander Ave at Vance St (Ronald McDonald House)
  • Alexander Ave at Vance St (Episcopal Center)
  • Erwin Square
  • Alexander Ave at Pace St (Pi Kappa Phi)
  • Alexander Ave at Pace St (Ubuntu House)
  • Swift Avenue at Caswell Pl (EB)
  • Science Dr at Fuqua School of Business (NB)
  • Shops at Erwin Mill
  • Perry St at 705 Broad Street Bldg
  • Circuit Dr at Towerview Rd
  • Duke Dialysis Center
  • Maxwell Ave at Smith Warehouse (WB)
  • Campus Dr at Maxwell St (WB)
  • Duke Center For Living Campus
  • Hock Plaza (2424 Erwin Rd)
  • Maxwell Ave at Smith Warehouse (EB)
  • Yearby Ave at Flowers Dr (GC/DN Eastbound)
  • Yearby Ave at Flowers Dr (GC/DN Westbound)
  • Anderson St at Campus Dr (Northbound)
  • Anderson St at Campus Dr Lot (Southbound)
  • Rutherford St at Hillsborough Rd
  • Towerview Rd at Wilson Gym (across)
  • Towerview Rd at Edens B & C Lots (roundabout)
  • Circuit Dr at Circuit Lot Ext (Westbound)
  • Circuit Dr at F.E.L. Labs (Eastbound)
  • 15th St at Hillsborough Rd
  • LaSalle St at Circuit Lot
  • Circuit Dr at North Building
  • Duke Medical Pavilion/Cancer Ctr
  • Millenium Hotel at Campus Walk Ave (EB)
  • Campus Walk Ave at LaSalle St
  • LaSalle St at Campus Walk Ave (Belmont Apts)
  • LaSalle St at Best Products Lot
  • Duke Hospital
  • LaSalle St at Duke Manor Apts (NB)
  • Science Dr at Bryan Center Garage
  • Towerview Rd at Gross Hall Labs
  • East Campus (Washington Duke Statue)
  • Hillsborough Rd at 9th St
  • Trent Dr at Duke Circle Parking Deck
  • Towerview at Circuit Dr
  • Swift Ave at Faber St
  • Rutherford St at Main St
  • Swift Ave at 300 Swift Apts
  • Towerview Rd at Wannamaker Dorm (Outbound)
  • LaSalle St at Grace Healthcare
  • Swift Ave at Campus Dr
  • Erwin Rd at Alexander Ave (Central Campus)
  • Campus Dr at Nasher (Eastbound)
  • LaSalle St at Kangaroo St (The Heights Apts)
  • Lasalle St at Blue Crest Ln (Blue Crest Apts)
  • Chapel Dr at Duke University Rd (Alumni House)
  • LaSalle St at Campus Walk Ave (Holly Hill Apts)
  • Science Dr at Bassett Dr (NB)
  • Science Dr Circle
  • Oregon St at Pace St
  • Main St at Erwin Rd

Over time

Overall score across the last 4 checks — unchanged since 2026-07-31.

2026-07-25: 41.62026-07-30: 41.62026-07-31: 41.62026-08-01: 41.6
Show the numbers
CheckScoreChange
2026-07-2541.6 first check
2026-07-3041.6 no change
2026-07-3141.6 no change
2026-08-0141.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-31.

Same feed file as 2026-07-31; the published zip did not change.

Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.

Everything we checked

13 findings, ordered by severity.

Show every finding
  • Error152 instances

    Stop time timepoint without times (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Finding code: stop_time_timepoint_without_times · See MobilityData GTFS Validator rules

  • Error1 instance

    Service data ended 356 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.)

    Finding code: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices

  • Warning2207 instances

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

  • Warning425 instances

    425 of 2207 trips lack rider-facing destination or direction text.

    When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.

    Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)

    Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices

  • Warning125 instances

    125 of 127 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

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

  • Warning6 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.)

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

  • 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.)

    Finding code: feed_expiration_date7_days · Read the fix guide · See MobilityData GTFS Validator rules

  • 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.)

    Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning1 instance

    This feed describes flexible (demand-responsive) service but has no booking_rules.txt.

    Riders can see the service area but not how or when to reserve a trip, so they can't actually use the service.

    Fix: Add booking_rules.txt saying how far ahead and how to book (phone, app, or web). (A small file; one rule often covers the whole service.)

    Finding code: scorecard_flex_no_booking_rules · Read the fix guide · See GTFS Schedule reference

  • Info34 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.)

    Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules

  • Info8 instances

    The feed includes a file that is not part of the GTFS spec.

    Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.

    Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)

    Finding code: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules

  • Info3 instances

    Some service dates fall outside the date window set in feed_info.txt.

    feed_info.txt should span every day your service runs, so apps know when the data applies.

    Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)

    Finding code: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules

Beyond the grade

Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.

  • Flex zones are published but no booking_rules.txt is present.

    Consider: Add booking_rules.txt with how far ahead and how to reserve (phone, app, or web).

NTD GTFS readiness Not ready

Resolve this before you certify on the D-10. 1 validator error to resolve. Service data expired 356 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 356 days ago, so FTA would find the link out of date.
agency_id provided Ready
agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.
agency_id equals your NTD ID (optional) Not checked yet
This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.
shapes.txt covers your trips Ready
All 2207 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, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.

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). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also 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 356 days ago. States wheelchair access on 2% 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 356 days ago.
Accessible Not yet
States wheelchair access on 2% 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.

  • 26 of 127 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 152 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, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.

Correctness 54 / 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. FTA NTD readiness also checks that the published feed is valid.
Freshness 0 / 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. FTA NTD readiness also checks that the published feed is current.
Rider experience 58 / 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.

Duke University 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/duke-university/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.