Feed status · checked 2026-09-01
Mitteldeutscher Verkehrsverbund (MDV)
Based on a Mobility Database mirror copy of the feed source on file; publisher ownership is not verified
unchanged since 2026-08-31
Catalogued in Sachsen, Germany.
Heads-up: The score fell 35 points in one step, from 67 on 2026-08-25 to 31 on 2026-08-26. A jump this size usually means the export changed rather than the service. Worth checking the run on this date. (checked 2026-08-26). This can be a brief vendor export glitch; watch the next update before acting.
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 4 hours ago; last changed 11 days ago; last fetch returned HTTP 404.
Measured 3 of 4 score categories from the Mobility Database's mirror copy of the feed.
How we measured this
Confidence in this measurement: provisional.
- Realtime quality was not measured this run. It does not count against the grade.
- The configured feed URL was unreachable, so the Mobility Database's hosted mirror copy was scored instead. Publisher ownership of the configured URL is not verified.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Add feed_start_date and feed_end_date to feed_info.txt and include calendar end dates in your export.Likely your export tool
Neither feed_info.txt nor the calendars state when service ends. Nobody can tell when this feed will go stale.
⏱ Likely a one-time export setting.worth about +100 points in its category
Review the rule documentation for 'missing_required_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Missing required file (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 points in its category
Review the rule documentation for 'missing_calendar_and_calendar_date_files' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Missing calendar and calendar date files (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 points in its category
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- Neither feed_info.txt nor the calendars state when service ends.
- Next action
- Add feed_start_date and feed_end_date to feed_info.txt and include calendar end dates in your export.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- Missing required file (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'missing_required_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- Missing calendar and calendar date files (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'missing_calendar_and_calendar_date_files' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
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.
Add feed_start_date and feed_end_date to feed_info.txt and include calendar end dates in your export.
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. See this feed's finding-clearance log.
Review the rule documentation for 'missing_required_file' 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. See this feed's finding-clearance log.
Review the rule documentation for 'missing_calendar_and_calendar_date_files' 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. See this feed's finding-clearance log.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- Schedule visibility is not known from this scorecard.
- Published accessibility data
- Published accessibility-data coverage is not known from this scorecard. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- No fare information is published in the feed.
- Realtime information
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
Send your vendor a fix request
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
Score by category
The MobilityData validator flagged 4 kinds of issue across 9 instances (6 error, 1 warning, 2 informational).
No service end date could be found in this feed, so there is no way to know when riders will lose trip planning.
This feed has no stops to state wheelchair accessibility for. Fare data is not published.
Not scored yet. Nothing here counts against the grade.
Over time
Overall score across the last 11 checks — unchanged since 2026-08-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-06 | 64.2 | first check |
| 2026-08-07 | 64.2 | no change |
| 2026-08-10 | 64.2 | no change |
| 2026-08-25 | 66.6 | up 2.4 |
| 2026-08-26 | 31.3 | down 35.3 |
| 2026-08-27 | 31.3 | no change |
| 2026-08-28 | 31.3 | no change |
| 2026-08-29 | 31.3 | no change |
| 2026-08-30 | 31.3 | no change |
| 2026-08-31 | 31.3 | no change |
| 2026-09-01 | 31.3 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed over time
On 2026-08-06 this feed started at grade D. On 2026-08-26 the grade moved from D to F. On 2026-09-01 the check no longer reported: the feed has a stretch of two weeks or more with no service running; two or more routes share the same name; some service calendars in the feed have already ended; some scheduled trips move faster between stops than a transit vehicle can; feed valid beyond total service window (flagged by the MobilityData validator); this feed models stations or entrances but has no pathways.txt; 144129 of 144129 trips don't say whether the vehicle is wheelchair accessible; 7621 of 7621 stops don't say whether a wheelchair user can board there; some service calendars have no days of the week switched on; unexpected enum value (flagged by the MobilityData validator); unsorted stop times (flagged by the MobilityData validator). As of 2026-09-01 it holds grade F.
A plain-language history of this feed, newest first.
- 2026-08-26 Grade went D to F, freshness fell 100 points.
Everything we checked
8 findings, ordered by severity.
Show every finding
- Error5 instances
Missing required file (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_required_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: missing_required_file · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Missing calendar and calendar date files (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_calendar_and_calendar_date_files' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: missing_calendar_and_calendar_date_files · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Neither feed_info.txt nor the calendars state when service ends.
Nobody can tell when this feed will go stale.
Fix: Add feed_start_date and feed_end_date to feed_info.txt and include calendar end dates in your export. (Likely a one-time export setting.)
Finding code: scorecard_no_expiry_date
- Warning1 instance
A file GTFS asks for (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Finding code: missing_recommended_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)
Finding code: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning1 instance
agency.txt has no working website URL.
Trip planners link riders to this URL for schedules and fares.
Fix: Set agency_url to your agency's website, starting with https://. (One field.)
Finding code: scorecard_bad_agency_url
- Info2 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 (opens the validator rules on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Conformance mark Not yet
This feed does not meet the conformance requirements yet. Here is what the mark needs: 2 validator errors to resolve. No service end date could be read. Accessibility completeness has not been measured.
- Valid Not yet
- 2 validator errors to resolve.
- Current Not yet
- No service end date could be read.
- Accessible Not yet
- Accessibility completeness has not been measured.
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.
Below the Google and Apple Maps four-week coverage bar. This feed has no service end date, so Maps cannot tell how far ahead it runs. Set a feed_info end date and a calendar that covers at least the next four weeks, then re-export. The feed also carries 6 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 72 / 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 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.
- Rider experience 0 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality Not yet published
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.
Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.
Cite this record
This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/mdv-mitteldeutscher/2026-09-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-09-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.