Feed status · checked 2026-08-01
OASA Athens rail transport (metro, electric railway, tram)
Based on the feed this agency publishes
Service mode Tram + Metro
down 0.4 since 2026-07-31
Catalogued in Attikí, Greece.
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 72 minutes ago; last changed 8 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
Add feed_info.txt with feed_start_date and feed_end_date to your export.Likely your export tool
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.
⏱ Two fields, set once in export settings.worth about +15 points in its category
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 in its category
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
129 of 252 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 +13 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
- feed_info.txt is missing its start/end dates (the file itself is absent)
- Next action
- Add feed_info.txt with feed_start_date and feed_end_date to 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
- The feed contains no fare information.
- Next action
- 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.
- 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
- 129 of 252 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- 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_info.txt with feed_start_date and feed_end_date to your export. · 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.
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. 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.
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.
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 30 days.
- Published accessibility data
- Accessibility information is stated for 48.8% of stops and 49.4% 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
The MobilityData validator flagged 3 kinds of issue across 18222 instances (0 error, 90 warning, 18132 informational).
Service data covers the next 30 days.
49% of stops state wheelchair accessibility (49% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
49% of stops state accessibility (49% marked accessible). Reflects what the feed states, not verified physical usability.
Not scored yet. Nothing here counts against the grade.
Routes and stops
This feed has no route shapes, so the map shows its stops only.
This feed has 252 stops.
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.
| Route | Type | Line color |
|---|---|---|
| T7 ΓΡΑΜΜΗ 7 ΤΡΑΜ | Tram / light rail | red (no shape in feed) |
| T6 ΓΡΑΜΜΗ 6 ΤΡΑΜ | Tram / light rail | red (no shape in feed) |
| M3 ΓΡΑΜΜΗ 3 | Subway / metro | blue (no shape in feed) |
| M1 ΓΡΑΜΜΗ 1 | Subway / metro | blue (no shape in feed) |
| M2 ΓΡΑΜΜΗ 2 | Subway / metro | blue (no shape in feed) |
List every stop
- 34ου Συντάγματος
- ΑΓ. ΔΗΜΗΤΡΙΟΣ
- ΧΑΛΑΝΔΡΙ
- ΧΑΛΑΝΔΡΙ
- Ελλήνων Ολυμπιονικών
- Ελλήνων Ολυμπιονικών
- ΧΟΛΑΡΓΟΣ
- ΧΟΛΑΡΓΟΣ
- ΗΛΙΟΥΠΟΛΗ
- ΗΛΙΟΥΠΟΛΗ
- ΗΡΑΚΛΕΙΟ
- ΗΡΑΚΛΕΙΟ
- ΑΓ. ΔΗΜΗΤΡΙΟΣ
- ΕΙΡΗΝΗ
- ΕΙΡΗΝΗ
- ΕΙΡΗΝΗ
- Καλαμάκι
- ΚΑΛΛΙΘΕΑ
- ΚΑΛΛΙΘΕΑ
- Καλαμάκι
- ΚΑΝΤΖΑ
- ΚΑΝΤΖΑ
- ΚΑΤΩ ΠΑΤΗΣΙΑ
- ΑΓΙΟΣ ΕΛΕΥΘΕΡΙΟΣ
- ΚΑΤΩ ΠΑΤΗΣΙΑ
- Γήπεδο ΚαραΙσκάκη
- Κασομούλη
- Κασομούλη
- ΚΑΤΕΧΑΚΗ
- ΚΑΤΕΧΑΚΗ
- ΚΑΤ
- ΚΑΤ
- ΚΕΡΑΜΙΚΟΣ
- ΚΕΡΑΜΙΚΟΣ
- ΑΓΙΟΣ ΕΛΕΥΘΕΡΙΟΣ
- ΚΗΦΙΣΙΑ
- ΚΗΦΙΣΙΑ
- Κέντρο Ιστιοπλοϊας
- Κέντρο Ιστιοπλοϊας
- Κολυμβητήριο (Γλύφαδα)
- Κολυμβητήριο (Γλύφαδα)
- ΚΟΡΥΔΑΛΛΟΣ
- ΚΟΡΥΔΑΛΛΟΣ
- ΚΟΡΩΠΙ
- ΚΟΡΩΠΙ
- ΑΓΙΟΣ ΙΩΑΝΝΗΣ
- Καλλιθέα
- Καλλιθέα
- Λαμπράκη
- Λουτρά Αλίμου
- Λουτρά Αλίμου
- Σ. ΛΑΡΙΣΗΣ
- Σ. ΛΑΡΙΣΗΣ
- Μαρίνα Αλίμου
- Μαρίνα Αλίμου
- ΜΑΝΙΑΤΙΚΑ
- ΑΓΙΟΣ ΙΩΑΝΝΗΣ
- ΜΑΝΙΑΤΙΚΑ
- Μικράς Ασίας
- Μεγάλου Αλεξάνδρου
- Μεγάλου Αλεξάνδρου
- ΜΕΓΑΡΟ ΜΟΥΣΙΚΗΣ
- ΜΕΓΑΡΟ ΜΟΥΣΙΚΗΣ
- ΜΕΤΑΞΟΥΡΓΕΙΟ
- ΜΕΤΑΞΟΥΡΓΕΙΟ
- Μηδείας - Μυκάλης
- Μηδείας - Μυκάλης
- ΑΓΙΟΣ ΝΙΚΟΛΑΟΣ
- ΜΟΝΑΣΤΗΡΑΚΙ
- ΜΟΝΑΣΤΗΡΑΚΙ
- ΜΟΝΑΣΤΗΡΑΚΙ
- ΜΟΝΑΣΤΗΡΑΚΙ
- ΜΟΣΧΑΤΟ
- ΜΟΣΧΑΤΟ
- Μοσχάτο
- Μοσχάτο
- Μουσσών
- Μουσσών
- ΑΓΙΟΣ ΝΙΚΟΛΑΟΣ
- ΝΕΑ ΙΩΝΙΑ
- ΝΕΑ ΙΩΝΙΑ
- ΝΕΡΑΤΖΙΩΤΙΣΣΑ
- ΝΕΡΑΤΖΙΩΤΙΣΣΑ
- Νέο Φάληρο
- Νέο Φάληρο
- ΝΙΚΑΙΑ
- ΝΙΚΑΙΑ
- Ν.ΚΟΣΜΟΣ
- Ν.ΚΟΣΜΟΣ
- ΑΓΙΑ ΠΑΡΑΣΚΕΥΗ
- Νέος Κόσμος
- Νέος Κόσμος
- ΝΟΜΙΣΜΑΤΟΚΟΠΕΙΟ
- ΝΟΜΙΣΜΑΤΟΚΟΠΕΙΟ
- ΟΜΟΝΟΙΑ
- ΟΜΟΝΟΙΑ
- ΟΜΟΝΟΙΑ
- ΟΜΟΝΟΙΑ
- ΠΑΛΛΗΝΗ
- ΠΑΛΛΗΝΗ
- ΑΓΙΑ ΠΑΡΑΣΚΕΥΗ
- ΠΑΝΕΠΙΣΤΗΜΙΟ
- ΠΑΝΕΠΙΣΤΗΜΙΟ
- Παναγίτσα
- Παναγίτσα
- Πλατεία Δεληγιάννη
- Παλαιό Δημαρχείο
- Παλαιό Δημαρχείο
- ΠΕΥΚΑΚΙΑ
- ΠΕΥΚΑΚΙΑ
- ΠΕΙΡΑΙΑΣ
- Αχιλλέως
- 1η Αγίου Κοσμά
- ΠΕΙΡΑΙΑΣ
- ΠΕΡΙΣΤΕΡΙ
- ΠΕΡΙΣΤΕΡΙ
- ΠΕΡΙΣΣΟΣ
- ΠΕΡΙΣΣΟΣ
- Πλατεία Εσπερίδων
- Πλατεία Εσπερίδων
- ΠΕΤΡΑΛΩΝΑ
- ΠΕΤΡΑΛΩΝΑ
- Πάρκο Φλοίσβου
- 1η Αγίου Κοσμά
- Πάρκο Φλοίσβου
- Παραλία Γλυφάδας
- Παραλία Γλυφάδας
- Πικροδάφνη
- Πικροδάφνη
- Πικροδάφνη
- ΠΕΙΡΑΙΑΣ
- ΠΕΙΡΑΙΑΣ
- ΠΕΙΡΑΙΑΣ
- Πλατεία Κατράκη
- 2η Αγίου Κοσμά
- Πλατεία Κατράκη
- Πλατεία Ιπποδαμείας
- Δ. ΠΛΑΚΕΝΤΙΑΣ
- Δ. ΠΛΑΚΕΝΤΙΑΣ
- ΠΑΝΟΡΜΟΥ
- ΠΑΝΟΡΜΟΥ
- Πλατεία Βεργώτη
- Πλατεία Βεργώτη
- ΣΕΦ (Νέο Φάληρο)
- ΣΕΠΟΛΙΑ
- 2η Αγίου Κοσμά
- ΣΕΠΟΛΙΑ
- Σκυλίτση
- ΣΥΝΤΑΓΜΑ
- ΣΥΝΤΑΓΜΑ
- ΣΥΝΤΑΓΜΑ
- ΣΥΝΤΑΓΜΑ
- ΣΥΓΓΡΟΥ-ΦΙΞ
- ΣΥΓΓΡΟΥ-ΦΙΞ
- Σύνταγμα (Κέντρο)
- ΑΚΡΟΠΟΛΗ
- ΤΑΥΡΟΣ
- ΤΑΥΡΟΣ
- ΘΗΣΕΙΟ
- ΘΗΣΕΙΟ
- Τροκαντερό
- Τροκαντερό
- Τζιτζιφιές
- Τζιτζιφιές
- ΑΓΙΑ ΒΑΡΒΑΡΑ
- ΑΓΙΑ ΒΑΡΒΑΡΑ
- ΑΚΡΟΠΟΛΗ
- Βουλιαγμένης
- Βουλιαγμένης
- ΒΙΚΤΩΡΙΑ
- ΒΙΚΤΩΡΙΑ
- Βούλα
- Ζάππειο
- Ζάππειο
- Ζέφυρος
- Ζέφυρος
- ΑΛΙΜΟΣ
- ΑΛΙΜΟΣ
- ΑΓΙΑ ΜΑΡΙΝΑ
- ΑΓΙΑ ΜΑΡΙΝΑ
- Αχιλλέως
- ΜΑΡΟΥΣΙ
- ΜΑΡΟΥΣΙ
- ΑΜΠΕΛΟΚΗΠΟΙ
- ΑΜΠΕΛΟΚΗΠΟΙ
- Αγγ. Μεταξά
- Αγγ. Μεταξά
- Αμφιθέας
- Αμφιθέας
- Ανδρούτσου
- ΑΝΩ ΠΑΤΗΣΙΑ
- Αγίας Φωτεινής
- ΑΝΩ ΠΑΤΗΣΙΑ
- ΑΝΘΟΥΠΟΛΗ
- ΑΝΘΟΥΠΟΛΗ
- Ακτή Ποσειδώνος
- Αγία Παρασκευή
- Αγία Παρασκευή
- ΑΡΓΥΡΟΥΠΟΛΗ
- ΑΡΓΥΡΟΥΠΟΛΗ
- Αγία Σκέπη
- Αγία Σκέπη
- Αγίας Φωτεινής
- Αγία Τριάδα
- ΑΤΤΙΚΗ
- ΑΤΤΙΚΗ
- ΑΤΤΙΚΗ
- ΑΤΤΙΚΗ
- Μπακνανά
- Μπακνανά
- Μπάτης
- Μπάτης
- ΑΓΙΟΣ ΑΝΤΩΝΙΟΣ
- ΣΥΝΔΕΣΗ ΠΡΟΑΣΤΙΑΚΟΥ
- ΣΥΝΔΕΣΗ ΠΡΟΑΣΤΙΑΚΟΥ
- ΔΑΦΝΗ
- ΔΑΦΝΗ
- Δέλτα Φαλήρου
- Δέλτα Φαλήρου
- ΑΓΙΟΣ ΑΝΤΩΝΙΟΣ
- ΔΗΜΟΤΙΚΟ ΘΕΑΤΡΟ
- ΔΗΜΟΤΙΚΟ ΘΕΑΤΡΟ
- Δημαρχείο
- ΕΘΝΙΚΗ ΑΜΥΝΑ
- ΕΘΝΙΚΗ ΑΜΥΝΑ
- Εδέμ
- Εδέμ
- ΑΙΓΑΛΕΩ
- ΑΙΓΑΛΕΩ
- Αιγαίου
- Άγιος Αλέξανδρος
- Αιγαίου
- ΕΛΑΙΩΝΑΣ
- ΕΛΑΙΩΝΑΣ
- ΕΛΛΗΝΙΚΟ
- ΕΛΛΗΝΙΚΟ
- Ελληνικό
- Ελληνικό
- ΕΛ. ΒΕΝΙΖΕΛΟΣ
- ΕΛ. ΒΕΝΙΖΕΛΟΣ
- ΕΥΑΓΓΕΛΙΣΜΟΣ
- Άγιος Αλέξανδρος
- ΕΥΑΓΓΕΛΙΣΜΟΣ
- Ευαγγελική Σχολή
- Ευαγγελική Σχολή
- Ευαγγελίστρια
- ΦΑΛΗΡΟ
- ΦΑΛΗΡΟ
- Φιξ
- Φιξ
- and 2 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — down 0.4 since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 61.3 | first check |
| 2026-07-30 | 59.2 | down 2.1 |
| 2026-07-31 | 58.8 | down 0.4 |
| 2026-08-01 | 58.4 | down 0.4 |
What changed since your last check
- Correctness no change
- Freshness down 1.7
- Rider experience no change
What changed in this feed
Overall score fell 0.4 points 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.
What changed over time
On 2026-07-25 this feed started at grade D. On 2026-07-30 the grade moved from D to F. On 2026-08-01 feed entered the expiry window (30 days of service left). As of 2026-08-01 it holds grade F.
A plain-language history of this feed, newest first.
- 2026-08-01 Feed entered the expiry window (30 days of service left).
- 2026-07-30 Grade went D to F, freshness fell 8 points.
Everything we checked
10 findings, ordered by severity.
Show every finding
- Warning57598 instances
57598 of 75730 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 (opens GTFS Best Practices on an external site)
- Warning38329 instances
38329 of 75730 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the transit vehicle 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 (opens the GTFS Schedule reference on an external site)
- Warning129 instances
129 of 252 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 (opens the GTFS Schedule reference on an external site)
- Warning89 instances
Some rider-facing names are in ALL CAPS or all lowercase.
ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- 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
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.)
Finding code: scorecard_missing_feed_info_dates · 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)
- Info18132 instances
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the transit vehicle ends up, so a midpoint name can send them the wrong way.
Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)
Finding code: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info144 instances
About 144 stop names are written in ALL CAPS.
Mixed-case names are easier to read in apps and are read more naturally by screen readers.
Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)
Finding code: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- 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.)
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 is close to the conformance mark. Service data runs out in 30 days; renew to qualify. States wheelchair access on 49% of stops and 49% 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 49% of stops and 49% 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 30 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
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 87 / 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 35 / 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 37 / 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/oasa-athens-rail/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.