Feed status · checked 2026-08-31
Tallinn public transport (TLT)
Based on the official feed source on file
Service mode Tram + Bus
unchanged since 2026-08-30
Catalogued in Harjumaa, Estonia.
Heads-up: Days until the service window ends dropped by 84 between 2026-08-07 and 2026-08-30, but only 23 day(s) passed. The feed's calendar appears to have moved backward, which can happen when an older export is republished. Worth confirming the latest export is the one being served. (checked 2026-08-30). 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 8 days ago; last changed 10 days ago.
Measured 3 of 4 score categories from the official feed URL on file.
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 official feed URL on file.
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
18046 of 18046 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
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
Only change the flagged IDs if an app needs basic ASCII values. Update each place that uses the ID. Keep all names and headsigns in their original language.
Some internal IDs use characters outside the basic text set. These IDs are valid UTF-8 data. This warning is only about support in older apps. It does not mean that names in other languages are wrong.
⏱ A planned ID change, not a quick text cleanup.worth about +8 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
- 18046 of 18046 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
- 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
- Some internal IDs use characters outside the basic text set.
- Next action
- Only change the flagged IDs if an app needs basic ASCII values. Update each place that uses the ID. Keep all names and headsigns in their original language.
- 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.
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. See this feed's finding-clearance log.
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. See this feed's finding-clearance log.
Only change the flagged IDs if an app needs basic ASCII values. Update each place that uses the ID. Keep all names and headsigns in their original language.
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
- The feed's last published service date is in 61 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 99.6% 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 6 kinds of issue across 60163 instances (0 error, 36853 warning, 23310 informational).
Service data covers the next 61 days.
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 not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
3 accessibility depth signals
5 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (83, 72, 81, 84, 85).
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.
2 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Männiku/Tagadi", "Männiku/Tagadi").
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
This feed models stations or entrances but has no pathways.txt and levels.txt.
Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.
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.
This feed has 18046 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.
- 1 (red)
- 10 (red)
- 11 (red)
- 12 (red)
- 13 (red)
- 15 (red)
- 16 (red)
- 18 (red)
- 19 (red)
- 2 (red)
- 20 (red)
- 21 (red)
- 22 (red)
- 23 (red)
- 24 (red)
- 24A (red)
- 25 (red)
- 26 (red)
- 26A (red)
- 27 (red)
- 28 (red)
- 3 (red)
- 30 (red)
- 31 (red)
- 31A (red)
- 32 (red)
- 33 (red)
- 34 (red)
- 35 (red)
- 36 (red)
- 37 (red)
- 38 (red)
- 39 (red)
- 4 (red)
- 40 (red)
- 41 (red)
- 42 (red)
- 44 (red)
- 45 (red)
- 46 (red)
- 47 (red)
- 48 (red)
- 49 (red)
- 5 (red)
- 50 (red)
- 54 (red)
- 55 (red)
- 57 (red)
- 58 (red)
- 59 (red)
- 6 (red)
- 60 (red)
- 61 (red)
- 62 (red)
- 63 (red)
- 65 (red)
- 66 (red)
- 67 (red)
- 7 (red)
- 73 (red)
- 8 (red)
- 8A (red)
- 9 (red)
- 91 (red)
- 92 (red)
- 93 (red)
- 94 (red)
- 95 (red)
- 96 (red)
- T1 (green)
- T2 (green)
- T3 (green)
- T4 (green)
- T5 (green)
- 72 (green)
- 81 (green)
- 83 (green)
- 84 (green)
- 85 (green)
| Route | Type | Line color |
|---|---|---|
| 1 Vana-Pääsküla - Viru - Viimsi | Bus | red |
| 10 Väike-Õismäe - Nõmme - Vana-Pääsküla | Bus | red |
| 11 Kadaka - Kaubamaja | Bus | red |
| 12 Väike-Õismäe - Seli | Bus | red |
| 13 Väike-Õismäe - Priisle | Bus | red |
| 15 Estonia - Bussijaam - Sõjamäe | Bus | red |
| 16 Väike-Õismäe - Estonia - Tallinn-Väike | Bus | red |
| 18 Viru keskus - Urda | Bus | red |
| 19 Reisadama D-terminal - Laagri alevik | Bus | red |
| 2 Balti jaam - Mõigu | Bus | red |
| 20 Viru keskus - Teelise | Bus | red |
| 21 Viru keskus - Landi | Bus | red |
| 22 Väike-Õismäe - Kakumäe | Bus | red |
| 23 Kadaka - Bussijaam | Bus | red |
| 24 Kadaka - Estonia | Bus | red |
| 24A Kadaka - Estonia | Bus | red |
| 25 Tiskre - Reisisadama D-terminal | Bus | red |
| 26 Väike-Õismäe - Paljassaare | Bus | red |
| 26A Väike-Õismäe - Paljassaare põik | Bus | red |
| 27 Harkujärve - Laagri alevik | Bus | red |
| 28 Vana-Lõuna - Väike-Õismäe | Bus | red |
| 3 Vana-Lõuna - Pelguranna | Bus | red |
| 30 Seli - Iru - Kärmu | Bus | red |
| 31 Priisle - Estonia | Bus | red |
| 31A Priisle - Iru hooldekodu - Estonia | Bus | red |
| 32 Männiku - Kopli | Bus | red |
| 33 Männiku - Kopli | Bus | red |
| 34 Viru keskus - Muuga aedlinn | Bus | red |
| 35 Seli - Pelguranna | Bus | red |
| 36 Väike-Õismäe - Nõmme - Viru | Bus | red |
| 37 Mustamäe - Kakumäe sadam | Bus | red |
| 38 Viru keskus - Muuga | Bus | red |
| 39 Vana-Lõuna - Liikuri | Bus | red |
| 4 Väike-Õismäe - Tiskre | Bus | red |
| 40 Priisle - Estonia - Pelguranna | Bus | red |
| 41 Balti jaam - Kakumäe | Bus | red |
| 42 Väike-Õismäe - Estonia - Priisle | Bus | red |
| 44 Viru keskus - P. Pinna | Bus | red |
| 45 Väike-Õismäe - Nõmme - Ülemiste | Bus | red |
| 46 Väike-Õismäe - Estonia - Seli | Bus | red |
| 47 Lennujaam - Peetri kool | Bus | red |
| 48 Pirita keskus - Vesse | Bus | red |
| 49 Viimsi keskus - Lennujaam | Bus | red |
| 5 Männiku - Viru - Metsakooli tee | Bus | red |
| 50 Seli - Majaka põik | Bus | red |
| 54 Väike-Õismäe - Bussijaam - Priisle | Bus | red |
| 55 Hobujaama - P. Pinna | Bus | red |
| 57 Raudalu - Kalev | Bus | red |
| 58 Priisle - Majaka põik | Bus | red |
| 59 Balti jaam - Pikakari | Bus | red |
| 6 Merivälja pansion - Metsakooli tee | Bus | red |
| 60 Seli - Maneeži | Bus | red |
| 61 Kotermaa - Järve haigla | Bus | red |
| 62 Väike-Õismäe - Mäeküla | Bus | red |
| 63 Priisle - Maneeži | Bus | red |
| 65 Priisle - Lennujaam | Bus | red |
| 66 Priisle - Balti jaam - Pelguranna | Bus | red |
| 67 Seli - Bussijaam - Sütiste | Bus | red |
| 7 Seli - Sõjamäe | Bus | red |
| 73 Vana-Lõuna - Viru - Kopli liinid | Bus | red |
| 8 Väike-Õismäe - Balti jaam - Äigrumäe | Bus | red |
| 8A Viru keskus - Äigrumäe | Bus | red |
| 9 Kadaka - Estonia - Priisle | Bus | red |
| 91 ÖÖ Balti jaam - Mustamäe | Bus | red |
| 92 ÖÖ Balti jaam - Väike-Õismäe | Bus | red |
| 93 ÖÖ Balti jaam - Pelguranna | Bus | red |
| 94 ÖÖ Balti jaam - Priisle | Bus | red |
| 95 ÖÖ Balti jaam - Viimsi keskus | Bus | red |
| 96 ÖÖ Balti jaam - Vana-Pääsküla | Bus | red |
| T1 Kopli - Kadriorg | Tram / light rail | green |
| T2 Kopli - Lennujaam | Tram / light rail | green |
| T3 Tondi - Kadriorg | Tram / light rail | green |
| T4 Tondi - Lennujaam | Tram / light rail | green |
| T5 Kopli - Vana-Lõuna | Tram / light rail | green |
| 72 Mustamäe - Kopli (trollibuss) | Bus | green |
| 81 Mustamäe - Kaubamaja (trollibuss) | Bus | green |
| 83 Mustamäe - Kaubamaja (trollibuss) | Bus | green |
| 84 Keskuse - Balti jaam (trollibuss) | Bus | green |
| 85 Mustamäe - Balti jaam (trollibuss) | Bus | green |
List every stop
- Kaare
- Valdeku
- Valdeku
- Valdeku
- Nurme
- Nurme
- Sutlema
- Mikitamäe kool
- Sikassaare
- Teelahkme
- Sutlema
- Kiviraie
- Kellamäe
- Turja
- Kudjape
- Hageri
- Haava
- Kalmistu (Kudjape)
- Haava
- Vihasoo kool
- Karusmarja
- Karusmarja
- P. Kerese
- Reisisadama D-terminal
- Kõlviku tee
- Kõlviku tee
- Kose 1
- P. Kerese
- Ravila tee
- Kraavi
- Astri
- Tallinn
- Tallinn
- Männiku
- Männiku
- Kauge
- Kauge
- Pihlaka
- Laagri market
- Pihlaka
- Kraavi
- Astri
- Keila raudteejaam
- Rahumäe
- Rahumäe
- Kalmistu
- Kalmistu
- Kasemäe
- Rahumäe
- Vaida
- Rahumäe
- Näituse
- Karulaugu
- Rannarahva
- Tamme
- Leppneeme
- Leppneeme
- Mäe
- Mäe
- Luhaääre
- Näituse
- Luhaääre
- Lohu
- Pällu
- Pällu
- Väljaotsa
- Väljaotsa
- Tammneeme keskus
- Tammneeme keskus
- Tammneeme tee
- Tammneeme tee
- Lubjamäe
- Risti
- Lubjamäe
- Viievelle tee
- Viievelle tee
- Lohu
- Risti
- Risti
- Kirde
- Kirde
- Patika
- Kuuli
- Rae
- Kivi
- Liiva
- Raudteejaam
- Paldiski sadam
- Liiva
- Karjaküla
- Vatsla
- Leesika
- Estonia 2
- Estonia
- Leesika
- Värava
- Estonia 7
- Värava
- A. Laikmaa
- Kivisilla
- Saue tee
- Tondi
- Kalmu
- Tondi
- Lilleküla
- Lilleküla
- Järve
- Järve
- Kalmu
- Liiva kalmistu
- Liiva kalmistu
- Raudalu
- Raku
- Saku Kingu
- Raku
- Kooli
- Kaarla
- Järve
- Kaarla
- Raudalu
- Assaku
- Assaku
- Graniidi
- Energia
- Kernu koolimaja
- Energia
- Vikerkaare
- Tuisu
- Muuga aedlinn
- Pirnipuu puiestee
- Kardheina tee
- Kabelikivi
- Kabelikivi
- Kallavere
- Järve
- Virve
- Ööbiku
- Kehra kool
- Kehra raudteejaam
- Koolimaja
- Hauka
- Klooga raudteejaam
- Klooga raudteejaam
- Klooga pood
- Kotka
- Kotka
- Tuulevälja
- Nõmme tee
- Vaskjala
- Räägu
- Västriku
- Tondi
- Tondi
- Ööbiku
- Tuisu
- Tüve
- Kellamäe
- Marsi
- Merivälja pansion
- Kastevarre tee
- Piira
- Kellavere tee
- Kopli
- Kissa
- Rohu
- Rahkla
- Väljaotsa
- Marsi
- Kurni
- Nõmme tee
- Västriku
- Västriku
- Kajamaa
- Kajamaa
- Rahumäe
- Västriku
- Rahumäe
- Nõmme
- Nõmme
- Hiiu
- Hiiu
- Kivimäe
- Kivimäe
- Sõjakooli
- Pääsküla
- Pääsküla
- Laagri
- Laagri
- Saue
- Saue
- Sõjakooli
- Valingu
- Valingu
- Keila
- Keila
- Tallinn-Väike
- Niitvälja
- Niitvälja
- Klooga
- Klooga
- Tallinn-Väike
- Klooga aedlinn
- Klooga aedlinn
- Tallinn-Väike
- Põllküla
- Põllküla
- Laoküla
- Laoküla
- Paldiski
- Kalev
- Paldiski
- Gaasi
- Gaasi
- Pikamägi
- Pikamägi
- Pirita jõgi
- Pirita jõgi
- Lagedi tee
- Lagedi tee
- Väo
- Kalev
- Väo
- Laastu
- Laastu
- Linnu tee
- Kumu
- Kumu
- Kalev
- Hallivanamehe
- Hallivanamehe
- Aegviidu
- Aegviidu
- Mustjõe
- Mustjõe
- Tondi
- Lahinguvälja
- Lahinguvälja
- Kehra
- Kehra
- Parila
- Tondi
- Parila
- Raasiku
- Raasiku
- Aruküla
- Aruküla
- Tallinn-Väike
- Kulli
- Kulli
- Lagedi
- and 17796 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-08-30.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-06 | 75.6 | first check |
| 2026-08-07 | 75.6 | no change |
| 2026-08-30 | 79.1 | up 3.5 |
| 2026-08-31 | 79.1 | 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-08-30.
Same feed file as 2026-08-30; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.
What changed over time
On 2026-08-06 this feed started at grade C. On 2026-08-30 the check no longer reported: some service calendars in the feed have already ended; some rider-facing names are in ALL CAPS or all lowercase. As of 2026-08-31 it holds grade C.
A plain-language history of this feed, newest first.
- 2026-08-30 Score rose 4 points, correctness rose 8 points.
Everything we checked
10 findings, ordered by severity.
Show every finding
- Warning19922 instances
Some internal IDs use characters outside the basic text set.
These IDs are valid UTF-8 data. This warning is only about support in older apps. It does not mean that names in other languages are wrong.
Fix: Only change the flagged IDs if an app needs basic ASCII values. Update each place that uses the ID. Keep all names and headsigns in their original language. (A planned ID change, not a quick text cleanup.)
Finding code: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning18046 instances
18046 of 18046 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)
- Warning16931 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no transit vehicle 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 (opens the validator rules on an external site)
- Warning74 instances
74 of 19655 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)
- 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
This feed models stations or entrances but has no pathways.txt.
Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.
Fix: Add pathways.txt to link entrances, platforms, and elevators. Give each one a level. (Worth it for multi-level or large stations; flat stops don't need it.)
Finding code: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info19650 instances
Unsorted stop times (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unsorted_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: unsorted_stop_times · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info3648 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)
- Info11 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 (opens the validator rules on an external site)
- Info1 instance
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)
Conformance mark Not yet
One requirement remains for this feed to earn the conformance mark. States wheelchair access on 0% of stops and 100% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 61 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 100% 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.
- 16931 of 18045 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 61 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 81 / 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 100 / 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 60 / 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/tallinn-public-transport-tlt/2026-08-31.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-31. 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.