Feed status · checked 2026-07-17
Zarząd Transportu Miejskiego w Gdańsku
Based on the feed this agency publishes
Service mode Tram + Bus
First scorecard for this agency
Catalogued in Pomorskie, Poland.
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.2, validator 8.0.1.
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
Re-export with a validity window that reaches at least 60 days out.Likely your export tool
Service data runs out in 14 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
⏱ One export setting.worth about +66 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
1620 of 1620 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 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 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
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.
Re-export with a validity window that reaches at least 60 days out. · 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.
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.
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 14 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 96.1% 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.
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
The MobilityData validator flagged 6 kinds of issue across 111 instances (0 error, 111 warning, 0 informational).
Service data runs out in 14 day(s). Publish an updated feed soon or riders will lose trip planning.
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.
2 accessibility depth signals
11 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (10, 11, 12, 2, 3, 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.
23 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Urząd Wojewódzki / Marszałkowski 02", "Teatr Miniatura / Radio Gdańsk 04", "Teatr Miniatura / Radio Gdańsk 03", 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.
- 10 (red)
- 100 (blue)
- 106 (blue)
- 107 (blue)
- 108 (blue)
- 11 (red)
- 110 (blue)
- 111 (blue)
- 112 (blue)
- 113 (blue)
- 115 (blue)
- 116 (blue)
- 117 (blue)
- 118 (blue)
- 12 (red)
- 120 (blue)
- 122 (blue)
- 123 (blue)
- 124 (blue)
- 126 (blue)
- 127 (blue)
- 130 (blue)
- 131 (blue)
- 132 (blue)
- 136 (blue)
- 138 (blue)
- 143 (blue)
- 148 (blue)
- 149 (blue)
- 154 (blue)
- 155 (blue)
- 156 (blue)
- 157 (blue)
- 158 (blue)
- 162 (blue)
- 166 (blue)
- 167 (blue)
- 168 (blue)
- 169 (blue)
- 171 (blue)
- 174 (blue)
- 175 (blue)
- 176 (blue)
- 178 (blue)
- 179 (blue)
- 183 (blue)
- 184 (blue)
- 186 (blue)
- 189 (blue)
- 195 (blue)
- 199 (blue)
- 2 (red)
- 200 (blue)
- 205 (blue)
- 207 (blue)
- 208 (blue)
- 210 (blue)
- 212 (blue)
- 213 (blue)
- 227 (blue)
- 232 (blue)
- 255 (blue)
- 256 (blue)
- 258 (blue)
- 262 (blue)
- 267 (blue)
- 268 (blue)
- 269 (blue)
- 283 (blue)
- 289 (blue)
- 295 (blue)
- 3 (red)
- 307 (blue)
- N1 (blue)
- N2 (blue)
- N3 (blue)
- N4 (blue)
- N5 (blue)
- N6 (blue)
- N8 (blue)
- N9 (blue)
- N14 (blue)
- N16 (blue)
- N56 (blue)
- N78 (blue)
- N89 (blue)
- 5 (red)
- 512 (blue)
- 6 (red)
- 60 (red)
- 600 (blue)
- 606 (blue)
- 607 (blue)
- 612 (blue)
- 622 (blue)
- 63 (red)
- 658 (blue)
- 8 (red)
- T8 (blue)
- 9 (red)
- 911 (blue)
| Route | Type | Line color |
|---|---|---|
| 10 | Tram / light rail | red |
| 100 | Bus | blue |
| 106 | Bus | blue |
| 107 | Bus | blue |
| 108 | Bus | blue |
| 11 | Tram / light rail | red |
| 110 | Bus | blue |
| 111 | Bus | blue |
| 112 | Bus | blue |
| 113 | Bus | blue |
| 115 | Bus | blue |
| 116 | Bus | blue |
| 117 | Bus | blue |
| 118 | Bus | blue |
| 12 | Tram / light rail | red |
| 120 | Bus | blue |
| 122 | Bus | blue |
| 123 | Bus | blue |
| 124 | Bus | blue |
| 126 | Bus | blue |
| 127 | Bus | blue |
| 130 | Bus | blue |
| 131 | Bus | blue |
| 132 | Bus | blue |
| 136 | Bus | blue |
| 138 | Bus | blue |
| 143 | Bus | blue |
| 148 | Bus | blue |
| 149 | Bus | blue |
| 154 | Bus | blue |
| 155 | Bus | blue |
| 156 | Bus | blue |
| 157 | Bus | blue |
| 158 | Bus | blue |
| 162 | Bus | blue |
| 166 | Bus | blue |
| 167 | Bus | blue |
| 168 | Bus | blue |
| 169 | Bus | blue |
| 171 | Bus | blue |
| 174 | Bus | blue |
| 175 | Bus | blue |
| 176 | Bus | blue |
| 178 | Bus | blue |
| 179 | Bus | blue |
| 183 | Bus | blue |
| 184 | Bus | blue |
| 186 | Bus | blue |
| 189 | Bus | blue |
| 195 | Bus | blue |
| 199 | Bus | blue |
| 2 | Tram / light rail | red |
| 200 | Bus | blue |
| 205 | Bus | blue |
| 207 | Bus | blue |
| 208 | Bus | blue |
| 210 | Bus | blue |
| 212 | Bus | blue |
| 213 | Bus | blue |
| 227 | Bus | blue |
| 232 | Bus | blue |
| 255 | Bus | blue |
| 256 | Bus | blue |
| 258 | Bus | blue |
| 262 | Bus | blue |
| 267 | Bus | blue |
| 268 | Bus | blue |
| 269 | Bus | blue |
| 283 | Bus | blue |
| 289 | Bus | blue |
| 295 | Bus | blue |
| 3 | Tram / light rail | red |
| 307 | Bus | blue |
| N1 | Bus | blue |
| N2 | Bus | blue |
| N3 | Bus | blue |
| N4 | Bus | blue |
| N5 | Bus | blue |
| N6 | Bus | blue |
| N8 | Bus | blue |
| N9 | Bus | blue |
| N14 | Bus | blue |
| N16 | Bus | blue |
| N56 | Bus | blue |
| N78 | Bus | blue |
| N89 | Bus | blue |
| 5 | Tram / light rail | red |
| 512 | Bus | blue |
| 6 | Tram / light rail | red |
| 60 | Tram / light rail | red |
| 600 | Bus | blue |
| 606 | Bus | blue |
| 607 | Bus | blue |
| 612 | Bus | blue |
| 622 | Bus | blue |
| 63 | Tram / light rail | red |
| 658 | Bus | blue |
| 8 | Tram / light rail | red |
| T8 | Bus | blue |
| 9 | Tram / light rail | red |
| 911 | Bus | blue |
This feed has 1620 stops.
List every stop
- Plac Solidarności 03
- Aksamitna 01
- Rybaki Górne 01
- Śródmieście SKM 04
- Toruńska 01
- Łagiewniki 01
- Plac Solidarności 04
- Port Lotniczy 01
- Plac Komorowskiego 03
- Dworzec Główny 18
- Dworzec Główny 05
- Dworzec Główny 14
- Dworzec Główny 07
- Dworzec Główny 12
- Dworzec Główny 10
- Port Lotniczy 02
- Dworzec Główny 11
- Dworzec Główny 08
- Dworzec Główny 13
- Dworzec Główny 06
- Tamka 01
- Hucisko 94
- Brama Wyżynna 05
- Chłodna 01
- Port Lotniczy 03
- Brama Wyżynna 03
- Cygańska Góra 03
- Cygańska Góra 04
- Brama Wyżynna 04
- Pomorskie Szkoły Rzemiosł 04
- Chłodna 02
- Żabi Kruk 04
- Żabi Kruk 03
- Długie Ogrody 01
- Brama Żuławska 03
- Bajki 01
- Elbląska 05
- Dickensa 01
- Andruszkiewicza 03
- Kaczeńce - Sienna 01
- Wawelska 01
- Wawelska 02
- Sucharskiego 03
- Królowej Bony 02
- Królowej Bony 01
- Sówki 01
- Stogi 06
- Steczka 01
- Sówki 02
- Kępna 01
- Steczka 02
- Baza Manipulacyjna 01
- Kępna 02
- Łęczycka 01
- Baza Manipulacyjna 02
- Łowicka 01
- Łęczycka 02
- Wosia Budzysza 01
- Łowicka 02
- Sucharskiego - PKP 01
- Sucharskiego - PKP 02
- Ku Ujściu 02
- Muzeum Westerplatte – Terminal Promowy 01
- Muzeum Westerplatte – Terminal Promowy 02
- Ku Ujściu 03
- Ku Ujściu 04
- Borska 01
- Brodnicka 01
- Brodnicka 02
- Europejskie Centrum Solidarności 01
- Żarnowiecka 02
- Siennicka 01
- Siennicka 02
- Przetoczna 01
- Przetoczna 02
- Przejazd Kolejowy 01
- Przejazd Kolejowy 02
- Kujawska 01
- Kujawska 02
- Brama Żuławska 04
- Muzeum II Wojny Światowej 02
- Mostek 01
- Miałki Szlak 02
- Miałki Szlak 01
- Węzeł Elbląska 02
- Błonia 01
- Błonia 02
- Tarcice 01
- Tarcice 02
- Michałki 01
- Michałki 02
- Rafineria 01
- Rafineria 02
- Rejenta 02
- Rejenta 01
- Zosi 02
- Zosi 01
- Domeyki 01
- Świtezianki 02
- Soplicy 01
- Soplicy 02
- Chrobrego 01
- Ostroroga 01
- Klonowicza 01
- Klonowicza 02
- Leszczyńskich 03
- Meissnera 01
- Meissnera 02
- Olsztyńska 03
- Olsztyńska 04
- Sobieszewo 01
- Kanałowa 01
- Kanałowa 02
- Pole Namiotowe 01
- Pole Namiotowe 02
- Lazurowa 01
- Lazurowa 02
- Orlinki 01
- Orlinki 02
- Wrzeszcz PKP 03
- Kwiatowa 01
- Kwiatowa 02
- Trałowa Szkoła 01
- Trałowa Szkoła 02
- Kempingowa 01
- Kempingowa 02
- Węgorzowa 01
- Węgorzowa 02
- Przystań 01
- Przystań 02
- Wrzeszcz PKP 04
- Świbnieńska I 01
- Świbnieńska I 02
- Uzdrowiskowa 01
- Uzdrowiskowa 02
- Świbnieńska III 01
- Świbnieńska III 02
- Przegalińska 01
- Przegalińska 02
- Benzynowa 01
- Benzynowa 02
- Wrzeszcz PKP 05
- Oczyszczalnia 01
- Oczyszczalnia 02
- Naftowa 01
- Naftowa 02
- Płońska 01
- Płońska 02
- Zagroble 01
- Zagroble 02
- Migdałowa 02
- Migdałowa 01
- Oliwa PKP 04
- Cedrowa 02
- Cedrowa 01
- Nowa Gdańska 02
- Nowa Gdańska 01
- Jodowa 01
- Jodowa 02
- Tęczowa 01
- Tęczowa 02
- Nadwiślańska 01
- Nadwiślańska 02
- Oliwa PKP 02
- Ornitologów 01
- Ornitologów 02
- Sierpowa 01
- Bratki 01
- Gęsia 01
- Olszynka Niwki 01
- Zawodzie 01
- Maki 01
- Oliwa PKP 03
- Muzeum Narodowe 01
- Muzeum Narodowe 02
- Wróbla 01
- Urząd Wojewódzki / Marszałkowski 02
- Brama Nizinna 01
- Brama Nizinna 02
- Mostowa 01
- Mostowa 02
- Oliwa 07
- Zaroślak 01
- Zaroślak 02
- Brama Oruńska 01
- Brama Oruńska 02
- Stare Szkoty 01
- Stare Szkoty 02
- Sandomierska 01
- Sandomierska 02
- Rejtana 01
- Rejtana 02
- Żabianka SKM 02
- Gościnna 01
- Gościnna 02
- Nowiny 01
- Nowiny 02
- Urząd Dozoru Technicznego 01
- Ukośna 02
- Ukośna 01
- Niegowska 02
- Niegowska 01
- Węzeł Lipce 02
- Jelitkowo Kapliczna 03
- Kokoszki PKP 01
- Ostróżek 02
- Ostróżek 01
- Św. Wojciech 02
- Ptasia 02
- Ptasia 01
- Małomiejska 02
- Przymorze SKM 03
- Małomiejska 01
- Platynowa 03
- Platynowa 01
- Uranowa 01
- Dom Pomocy Społecznej 01
- Dom Pomocy Społecznej 02
- Zaroślak 03
- Zaroślak 04
- Cmentarna 01
- Stoczniowców 02
- Zaspa SKM 02
- Reformacka 01
- Wronki 01
- Kokoszki PKP 02
- Rondo Kuronia 01
- Rondo Kuronia 02
- Cieszyńskiego 03
- Sikorskiego 03
- Pohulanka 03
- Pohulanka 04
- Nowy Port Szaniec Zachodni 02
- Odrzańska 03
- Odrzańska 04
- Worcella 01
- Drwęcka 01
- Chałubińskiego 03
- Chałubińskiego 04
- Węzeł Elbląska 01
- Dworzec PKS 03
- Urząd Miejski 02
- Bema 01
- Zakopiańska 04
- Zakopiańska 03
- Emaus 01
- Siedlce 06
- Zielony Stok 01
- Zielony Stok 02
- Pagórkowa 01
- and 1370 more (see the full list on the map or in the GeoJSON)
Over time
This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.
Everything we checked
12 findings, ordered by severity.
Show every finding
- Warning3694 instances
3694 of 93654 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.)
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning1620 instances
1620 of 1620 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)
- Warning101 instances
Unexpected enum value (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unexpected_enum_value' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: unexpected_enum_value · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning5 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.)
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
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Validator rule: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
This feed's service calendar runs out within the next 30 days.
If a new feed isn't published before it ends, trip planners will drop your agency and riders will see no service.
Fix: Schedule a feed re-export now so the new calendar is live well before the current one ends. (Usually a re-export from your scheduling software.)
Validator rule: feed_expiration_date30_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Missing feed contact email and url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_feed_contact_email_and_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt does not state when this feed starts and ends.
Without stated dates, apps can't warn anyone before your data goes stale; it just disappears one day.
Fix: Fill in feed_start_date and feed_end_date in feed_info.txt. (Two fields, likely set once in your export settings.)
Validator rule: missing_feed_info_date · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Service data runs out in 14 day(s).
When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
Fix: Re-export with a validity window that reaches at least 60 days out. (One export setting.)
Validator rule: scorecard_feed_expiring_soon · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning1 instance
feed_info.txt is missing its start/end dates
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.)
Validator rule: 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.)
Validator rule: scorecard_no_fare_data · 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.)
Validator rule: 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 14 days; renew to qualify. States wheelchair access on 0% of stops and 96% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data runs out in 14 days; renew to qualify.
- Accessible Not yet
- States wheelchair access on 0% of stops and 96% 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.
- 5 of 1620 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.
At risk for the Google and Apple Maps four-week coverage bar. This feed has 14 days of service left. Maps needs at least four weeks (28 days) of upcoming service, so your agency will fall out of trip planners soon. Re-export with a longer calendar.
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 8 / 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 52 / 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/ztm-gdansk/2026-07-17.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-07-17. 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.