Feed status · checked 2026-07-18
Föli (Turku region)
Based on the feed this agency publishes
Service mode Bus + Ferry
First scorecard for this agency
Catalogued in Varsinais-Suomi, Finland.
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
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
3647 of 3647 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
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
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. 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.
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.
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 323 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 98% 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.
Ungraded capability read
Ferry data profile
A ferry-specific view of what this GTFS feed publishes. Schedule measurements use ferry routes and trips only; fare and realtime facts are labelled as whole-feed. Unknown values are not treated as no.
- Ferry service
- 2 routes · 46 trips
- Terminal structure
- 8 ferry boarding locations; no parent-station hierarchy is published.
- Terminal access
- Not applicable: no ferry boarding location is linked to a parent station, so stop_access is not permitted here.
- Published accessibility
- Unknown: none of the 8 ferry boarding locations publish wheelchair_boarding. 100% of ferry trips publish a value; 0% of all ferry trips explicitly say allowed (0 of 46). Unstated values remain unknown. This reports published values, not verified physical usability.
- Bicycles
- Unknown: none of the 46 ferry trips publish bikes_allowed.
- Cars
- Unknown: none of the 46 ferry trips publish cars_allowed.
- Fares
- Whole feed: no applied fare data is published. This is not evidence that ferry service is free.
- Realtime
- Whole feed: no GTFS-Realtime endpoints are configured in this scorecard.
Descriptive only. This profile does not change the grade or verify vessels, terminal facilities, vehicle carriage, fares, or accessibility in the real world. Field meanings follow the GTFS Schedule reference.
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 14 kinds of issue across 35354 instances (0 error, 35021 warning, 333 informational).
Service data covers the next 323 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.
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.
- 1 (teal)
- 100 (yellow)
- 5 (orange)
- 5A (orange)
- 6 (green)
- 6A (green)
- 6T (green)
- 8 (red)
- 9 (gray)
- 180 (teal)
- 9A (gray)
- 1A (teal)
- 10 (teal)
- 201 (yellow)
- 203 (yellow)
- 206 (yellow)
- 10A (teal)
- 20 (yellow)
- 220 (yellow)
- 21 (yellow)
- 22 (yellow)
- 23 (yellow)
- 24 (yellow)
- 25 (yellow)
- 25A (yellow)
- 26 (yellow)
- 301 (yellow)
- 302 (yellow)
- 303 (yellow)
- 27 (yellow)
- 27A (yellow)
- 28 (yellow)
- 28A (yellow)
- 28T (yellow)
- 33 (yellow)
- 33A (yellow)
- 39 (yellow)
- 41 (yellow)
- 2 (pink)
- 42 (yellow)
- 401 (yellow)
- 402 (yellow)
- 42A (yellow)
- 43 (yellow)
- 44 (yellow)
- 45 (yellow)
- 46 (yellow)
- 50 (yellow)
- 50A (yellow)
- 51 (yellow)
- 51A (yellow)
- 2Y (pink)
- 52 (yellow)
- K1 (yellow)
- K2 (yellow)
- K3 (yellow)
- K4 (yellow)
- K6 (yellow)
- 53 (yellow)
- L1 (yellow)
- L2 (yellow)
- L3 (yellow)
- L4 (yellow)
- L5 (yellow)
- L6 (yellow)
- L7 (yellow)
- L8 (yellow)
- L9 (yellow)
- 62 (yellow)
- L10 (yellow)
- L11 (yellow)
- L12 (yellow)
- L13 (yellow)
- L14 (yellow)
- 67 (yellow)
- N1 (yellow)
- N2 (yellow)
- N3 (yellow)
- N4 (yellow)
- N5 (yellow)
- N6 (yellow)
- N7 (yellow)
- N8 (yellow)
- N9 (yellow)
- N10 (yellow)
- N11 (yellow)
- N12 (yellow)
- N13 (yellow)
- N14 (yellow)
- P1 (yellow)
- P2 (yellow)
- P3 (red)
- P4 (yellow)
- P5 (yellow)
- P6 (red)
- P7 (red)
- 72 (yellow)
- R1 (yellow)
- R2 (yellow)
- 73 (yellow)
- V1 (yellow)
- V2 (yellow)
- V3 (yellow)
- V4 (yellow)
- V5 (yellow)
- 74 (yellow)
- 75 (yellow)
- 3 (brown)
- 600 (yellow)
- 601 (yellow)
- 77 (yellow)
- 612 (green)
- 614 (green)
- 615 (green)
- 78 (yellow)
- 79 (yellow)
- 79A (yellow)
- 82 (yellow)
- 90 (yellow)
- 98 (yellow)
- 5T (orange)
- 3A (brown)
- 700 (yellow)
- 701 (yellow)
- 703 (yellow)
- 704 (yellow)
- 705 (yellow)
- 706 (yellow)
- 708 (yellow)
- 709 (yellow)
- 711 (red)
- 720 (green)
- 720P (green)
- 721 (green)
- 722 (green)
- 722S (green)
- 723 (green)
- 723H (green)
- 723K (green)
- 723S (green)
- 801 (orange)
- 802 (green)
- 4 (yellow)
- 901 (green)
- 902 (green)
- 903 (green)
- 904 (green)
- Lautta (teal)
| Route | Type | Line color |
|---|---|---|
| 1 Lentoasema-Keskusta-Satama | Bus | teal |
| 4T Varissuo, Itäkeskus-Skanssi-Keskusta, Halinen-Keskusta | Bus | yellow (no shape in feed) |
| 100 Keskusta-Turkuhalli | Bus | yellow |
| 101 Keskusta-Logomo | Bus | yellow (no shape in feed) |
| 102 Kupittaan palloiluhalli-Keskusta | Bus | yellow (no shape in feed) |
| 5 Ylioppilaskylä-Keskusta-Haarla | Bus | orange |
| 5A Ylioppilaskylä-Keskusta-Toijainen-Haarla | Bus | orange |
| 6 Lieto-Turku-Naantali | Bus | green |
| 6A Kaarina-Turku-Naantali | Bus | green |
| 6T Lieto-Turku, Naantali-Turku | Bus | green |
| 8 Runosmäki-Keskusta-Harittu | Bus | red |
| 8T Runosmäki-Keskusta, Harittu-Keskusta | Bus | red (no shape in feed) |
| 9 Uittamo-Keskusta-Härkämäki | Bus | gray |
| 180 Martinsilta-Forum Marinum-Ruissalo | Ferry | teal |
| 9A Uittamo-Keskusta-Suikkila | Bus | gray |
| 1A Linja-autoasema-Keskusta-Satama | Bus | teal |
| 10 Uittamo-Skanssi-Kupittaa-Länsikeskus-Satama | Bus | teal |
| 201 Puutori-Kaanaa-Naantali-Luonnonmaa | Bus | yellow |
| 203 Puutori-Kaanaa-Naantali-Merimasku-Velkua | Bus | yellow |
| 206 Puutori-Raisio-Kaanaa | Bus | yellow |
| 10A Varissuo-Lauste-Kupittaa-Mylly-Raisio-Perno | Bus | teal |
| 20 Keskusta-Muhkuri | Bus | yellow |
| 220 Ylioppilaskylä-Keskusta-Ihala-Raisio-Petäsmäki | Bus | yellow |
| 21 Paattinen-Keskusta | Bus | yellow |
| 22 Jäkärlä-Yli-Maaria-Moisio-Keskusta-Ilpoinen | Bus | yellow |
| 22T Jäkärlä-Yli-Maaria-Moisio-Keskusta-Ilpoinen | Bus | yellow (no shape in feed) |
| 23 Tortinmäki-Paattinen-Keskusta | Bus | yellow |
| 24 Puutori-Erikvalla | Bus | yellow |
| 25 Puutori-Brinkhall-Kakskerta | Bus | yellow |
| 25A Puutori-Myllykylä-Kakskerta | Bus | yellow |
| 1T Lentoasema-Keskusta, Satama-Keskusta | Bus | teal (no shape in feed) |
| 26 Metsämäki-Oriketo-Puutori | Bus | yellow |
| 301 Keskusta-Rusko (Päällistönmäki) | Bus | yellow |
| 302 Keskusta-Rusko-Vahto | Bus | yellow |
| 303 Keskusta-Rusko (Paasniittu)-Vahto | Bus | yellow |
| 27 Varissuo-Keskusta-Kirstinpuisto-Herttuankulma | Bus | yellow |
| 27A Varissuo-Keskusta-Port Arthur-Herttuankulma | Bus | yellow |
| 28 Auvaismäki-Jäkärlä-Keskusta-Ruissalo | Bus | yellow |
| 28A Puutori-Keskusta-Ruissalo | Bus | yellow |
| 28T Auvaismäki-Jäkärlä-Keskusta | Bus | yellow |
| 33 Vienola-Perno-Pansio | Bus | yellow |
| 33A Vienola-Perno-Pansio, laivastoasema | Bus | yellow |
| 39 Ylioppilaskylä-Itäinen Pitkäkatu-Uittamo | Bus | yellow |
| 41 Lehmusvalkama-Keskusta-Kasarminkatu | Bus | yellow |
| 2 Kohmo-Keskusta-Nättinummi-Mylly | Bus | pink |
| 42 Skanssi-Kohmo-Keskusta | Bus | yellow |
| 401 Ilmarinen-Puutori | Bus | yellow |
| 402 Lieto as-Ilmarinen-Puutori | Bus | yellow |
| 42A Skanssi-Varissuo-Keskusta | Bus | yellow |
| 43 Ilpoinen-Keskusta-Mälikkälä | Bus | yellow |
| 44 Runosmäki-Länsikeskus | Bus | yellow |
| 45 Impivaaran uimahalli-Keskusta-Vienola | Bus | yellow |
| 46 Rautalankatu-Pansio | Bus | yellow |
| 50 Moikoinen-Kukola-Oriniemi-Häppilä-Moikoinen | Bus | yellow |
| 50A Moikoinen-Kukola-Oriniemi-Häppilä-Maanpää-Moikoinen | Bus | yellow |
| 51 Moikoinen-Häppilä-Oriniemi-Kukola-Moikoinen | Bus | yellow |
| 51A Moikoinen-Maanpää-Häppilä-Oriniemi-Kukola-Moikoinen | Bus | yellow |
| 2Y Kohmo-Keskusta-Länsinummi | Bus | pink |
| 52 Papinsaari-Kaistarniemi-Syvälahti | Bus | yellow |
| K1 Auranlaakso-Oskarinaukio | Bus | yellow |
| K2 Keskusta-Piispanristi-Keskusta-Kesämäki-Keskusta | Bus | yellow |
| K3 Keskusta-Sorro-Keskusta-Voivala-Keskusta | Bus | yellow |
| K4 Piikkiö-Harvaluoto | Bus | yellow |
| K6 Toivonlinna-Piikkiö-Varissuo | Bus | yellow |
| 53 Pikisaari-Moikoinen-Kaistarniemi-Papinsaari | Bus | yellow |
| L1 Koulukeskus-Suopohja-Littoinen | Bus | yellow |
| L2 Koulukeskus-Loukinainen-Littoinen | Bus | yellow |
| L3 Ilmarinen-Arosuo-Paavola | Bus | yellow |
| L4 Ilmarinen-Rauhakylä-Vintala-keskusta-Koulukeskus | Bus | yellow |
| L5 Jokilaakso-Koulukeskus-Saukonoja-Liedonperä-Tarvasjoki | Bus | yellow |
| L6 Koulukeskus-Vt 10-Tarvasjoki-Liedonperä-Nuolemo | Bus | yellow |
| L7 Koulukeskus-Ilmarinen | Bus | yellow |
| L8 Keskusta-Hämeentie-Yliskulma | Bus | yellow |
| L9 Kaurinkoski-Pahkamäen koulu-Rähälä-Jokilaakson koulu | Bus | yellow |
| 62 Keskusta-Itäinen Pitkäkatu-Moikoinen-Papinsaari | Bus | yellow |
| L10 Jokilaakson koulu-Suopohja/Loukinainen-Littoisten koulu | Bus | yellow |
| L11 Tarvasjoki-Yliskulma-Jokilaakson koulu | Bus | yellow |
| L12 Yliskulma-Jokilaakson koulu | Bus | yellow |
| L13 Liedon keskusta-Loukinainen-Littoinen | Bus | yellow |
| L14 Jalosenkuja-Rauhakylä-Haaganmäki-Ilmaristen koulu | Bus | yellow |
| 67 Katariina-Harittu-Ilpoisten koulu | Bus | yellow |
| N1 Keskusta-Murikko-Keskusta | Bus | yellow |
| N2 Naantali-Rymättylä | Bus | yellow |
| N3 Naantali-Linnavuori-Rymättylä | Bus | yellow |
| N4 Naantali-Merimasku | Bus | yellow |
| N5 Naantali-Merimasku-Velkua | Bus | yellow |
| N6 Naantali-Merimasku-Velkua | Bus | yellow |
| N7 Keskusta-Linnavuori-Porhonkallio-Keskusta | Bus | yellow |
| N8 Merimaskun koulu-Killainen-Iskola-Merimaskun koulu | Bus | yellow |
| N9 Teersalo-Pohjanpääntie | Bus | yellow |
| 70 Syvälahden koulu-Kukola-Haarla-Papinsaari | Bus | yellow (no shape in feed) |
| N10 Rymättylä-Aikkola-Poikko | Bus | yellow |
| N11 Rymättylä-Ahteentaka | Bus | yellow |
| N12 Rymättylä-Aasla | Bus | yellow |
| N13 Naantali-Haapala | Bus | yellow |
| N14 Naantalin keskusta-Naantalin satama | Bus | yellow |
| 71 Moikoinen-Syvälahden koulu-Pikisaari-Maanpää-Oriniemi-Haarla-Moikoinen | Bus | yellow (no shape in feed) |
| P1 Keskusta-Oinila-Keskusta | Bus | yellow |
| P2 Keskusta-Huso-Kurki-Kevola-Vistan koulu-Jokelan koulu | Bus | yellow |
| P3 Keskusta-Oinila-Juntola-Suksela-Keskusta | Bus | red |
| P4 Keskusta-Paimion metsäkoulu | Bus | yellow |
| P5 Asematie-Senioritalo-Tervesyasema-Neste K Paimio | Bus | yellow |
| P6 Taatila-Kaleva-Vistan koulu | Bus | red |
| P7 Keskusta-Jokelan koulu-Veikkari-Teerlaki | Bus | red |
| 72 Syvälahden koulu-Haarla-Kakskerta | Bus | yellow |
| R1 Petäsmäki-Tikanmaa-Kaanaa-Keo-Petäsmäki | Bus | yellow |
| R2 Petäsmäki-Keo-Kaanaa-Tikanmaa-Petäsmäki | Bus | yellow |
| 73 Saramäki-Turun Lyseon koulu | Bus | yellow |
| V1 Järvijoki-Lavamäki-Laukolan koulu | Bus | yellow |
| V2 Soisalontie-Leinainen-Laukolan koulu | Bus | yellow |
| V3 Lähteenmäki-Kajamo-Kahari-Hiidenvainion koulu | Bus | yellow |
| V4 Kahari-Päällistönmäki-Hiidenvainion koulu-Merttelän koulu-Isovuori-Laukolan koulu | Bus | yellow |
| V5 Ohjaluoto-Isovuori-Ravaste-Merttelän koulu-Hiidenvainion koulu | Bus | yellow |
| 74 Varissuo-Nummenpakan koulu | Bus | yellow |
| 75 Perno-Topeliuksen koulu | Bus | yellow |
| 3 Varissuo-Keskusta-Perno | Bus | brown |
| 76 Jäkärlä-Kärsämäen väistötilat | Bus | yellow (no shape in feed) |
| 600 Littoinen-Varissuo-Kohmo-Skanssi | Bus | yellow |
| 601 Skanssi-Kohmo-Varissuo-Littoinen | Bus | yellow |
| 77 Tortinmäki-Yli-Maarian koulu | Bus | yellow |
| 612 Marttila-Lieto-Turku | Bus | green |
| 614 Koski tl-Marttila-Lieto-Turku | Bus | green |
| 615 Somero-Koski tl-Marttila-Lieto-Turku | Bus | green |
| 78 Auvaismäki-Yli-Maarian koulu | Bus | yellow |
| 79 Varissuo-Halinen | Bus | yellow |
| 79A Kohmo-Halinen | Bus | yellow |
| 82 Tortinmäki-Paattinen-Moisio-Jäkärlä-Keskusta | Bus | yellow |
| 89 Halinen-Ylioppilaskylä-Keskusta-Ilpoinen | Bus | yellow (no shape in feed) |
| 90 Varissuo-Harittu-Uittamo-Perno | Bus | yellow |
| 98 Runosmäki-Härkämäki-Perno | Bus | yellow |
| 5T Keskusta-Haarla | Bus | orange |
| 3A Varissuo-Keskusta-Raisio | Bus | brown |
| 700 Piikkiö-Puutori | Bus | yellow |
| 701 Toivonlinna-Piikkiö-Puutori | Bus | yellow |
| 703 Paimio-Naskarla-Piikkiö-Puutori | Bus | yellow |
| 704 Paimio-Piikkiö-Puutori | Bus | yellow |
| 705 Paimion parantola-Paimio-Naskarla-Piikkiö-Puutori | Bus | yellow |
| 706 Paimion parantola-Paimio-Piikkiö-Puutori | Bus | yellow |
| 707 Paimio-Hepojoki-Piikkiö-Puutori | Bus | yellow (no shape in feed) |
| 708 Huso th-Paimio-Piikkiö-Puutori | Bus | yellow |
| 709 Paimion parantola-Paimio-VT1-Puutori | Bus | yellow |
| 711 Paimio-Sauvo | Bus | red |
| 720 Sauvo-Turku | Bus | green |
| 720P Sauvo-Paimio-Turku | Bus | green |
| 721 Kemiö-Sauvo-Turku | Bus | green |
| 721S Kemiö-Sauvo-Turku-Turun satama | Bus | green (no shape in feed) |
| 722 Taalintehdas-Kemiö-Sauvo-Turku | Bus | green |
| 722S Taalintehdas-Kemiö-Sauvo-Turku-Turun satama | Bus | green |
| 723 Kasnäs-Taalintehdas-Kemiö-Sauvo-Turku | Bus | green |
| 723H Kasnäs-Svartnäs-Taalintehdas-Kemiö-Sauvo-Turku | Bus | green |
| 723K Kasnäs-Kemiö-Sauvo-Turku | Bus | green |
| 723S Kasnäs-Taalintehdas-Kemiö-Sauvo-Turku-Turun satama | Bus | green |
| 3T Varissuo-Keskusta | Bus | brown (no shape in feed) |
| 801 Parainen-Turku | Bus | orange |
| 802 Parainen-Turku, pikavuoro | Bus | green |
| 4 Varissuo, Itäkeskus-Skanssi-Keskusta-Halinen | Bus | yellow |
| 901 Korppoo-Nauvo-Parainen-Turku | Bus | green |
| 902 Korpoström-Korppoo-Nauvo-Parainen-Turku | Bus | green |
| 903 Houtskari-Korppoo-Nauvo-Parainen-Turku | Bus | green |
| 904 Houtskari-Korppoo | Bus | green |
| Lautta Houtskari-Korppoo | Ferry | teal |
This feed has 3647 stops.
List every stop
- Turun satama (Silja)
- Sairashuoneenpuisto
- Wärtsilänpolku
- Takamaantie
- Jäkäläpolku
- Rieskalähteentie
- Konevarikko
- Rieskalähteentie
- Vaunukatu
- Vaunukatu
- Takamaantie
- Kanslerintie
- Merimiehenkatu
- Pansiontie
- Pansiontie
- Vienola
- Parolanpuisto
- Kiikku
- Runosmäen vanhuskeskus
- Vähäheikkiläntie
- Tonttumäki
- Vienola
- Lukoilantie
- Ruohonpäänkatu
- Untolankatu
- Itäpellontie
- Kähärintie
- Paasirinne
- Ieskatu
- Tiilentekijänkatu
- Hammasklinikka
- Datacity
- Urheiluhalli
- Kupittaan palloiluhalli
- Miljoonatie
- Hippoksentie
- Vaapukkatie
- Alhomaantie
- Alhomaantie
- Martinkirkko
- Vaapukkatie
- Karhunaukio
- Hippoksentie
- Miljoonatie
- Kupittaan palloiluhalli
- Urheiluhalli
- Datacity
- Hammasklinikka
- Martinsilta
- Paasirinne
- Kähärintie
- Itäpellontie
- Untolankatu
- Ruohonpäänkatu
- Lukoilantie
- Aunelantie
- Linnankatu
- Vaistentie
- Suihkarintie
- Karhulantie
- Moision koulu
- Paimionkatu
- Moisio
- Isosuontie
- Mittumaarintie
- Koulukatu
- Saarenoja
- Haverintie
- Saarenoja
- Mittumaarintie
- Isosuontie
- Moisionramppi
- Moisionramppi
- Moisio
- Paimionkatu
- Käsityöläiskatu
- Moision koulu
- Karhulantie
- Suihkarintie
- Vaistentie
- Huhkonmaantie
- Huiskulantie
- Kristiinankatu
- Paimala
- Keinumäentie
- Urheilutalo
- Myllyoja
- Puolniituntie
- Suvannontie
- Jäkärlän puistokatu
- Kylmäalhonkatu
- Jäkärlän puistokatu
- Merovinkikatu
- Borenpuisto
- Hirvensalonsilta
- Jäkärlän liittymä
- Ruskonojantie
- Auvaismäki
- Ruskonojantie
- Jäkärlän liittymä
- Merovinkikatu
- Suvannontie
- Puolniituntie
- Myllyoja
- Urheilutalo
- Kyyrläntie
- Keinumäentie
- Paimala
- Huiskulantie
- Huhkonmaantie
- Suokallionkatu
- Haverintie
- Mäntysaarentie
- Auvaistentie
- Brahenkatu
- Krouvintie
- Krouvinkuja
- Tiravantie
- Kreivilän koulu
- Sakontie
- Männistöntie
- Paattisten kirkko
- Aluetalo
- Iskoistenkatu
- Toijainen
- Alakartanontie
- Levauksentie
- Viikkalantie
- Tiipiläntie
- Joenperäntie
- Yli-Rokki
- Kaivastentie
- Tuomisentie
- Valuntie
- Haavikko
- Akatemiantalo
- Ikkalantie
- Jokelantie
- Purolantie
- Kaarlejoentie
- Mäkeläntie
- Perttelmäentie
- Välimaantie
- Jaakolantie
- Tortinmäentie
- Tortinmäki
- Yliopisto (TYKS U-sairaala)
- Tortinmäentie
- Jaakolantie
- Välimaantie
- Perttelmäentie
- Mäkeläntie
- Kaarlejoentie
- Purolantie
- Jokelantie
- Ikkalantie
- Haavikko
- TYKS T-sairaala
- Valuntie
- Tuomisentie
- Kaivastentie
- Yli-Rokki
- Joenperäntie
- Tiipiläntie
- Viikkalantie
- Levauksentie
- Alakartanontie
- Aluetalo
- Aninkaistensilta
- Paattisten kirkko
- Paattisten kirkko
- Männistöntie
- Männistöntie
- Sakontie
- Kreivilän koulu
- Auvaismäentie
- Krouvinkuja
- Krouvintie
- Auvaistentie
- Savikatu
- Mäntysaarentie
- Suokallionkatu
- Ketussuontie
- Ollinkuja
- Urpontie
- Rykmentintie
- Ojarinne
- Hannunniittu
- Karjakuja
- C. O. Malmin koulu
- Tanhuankatu
- Jaaninpuisto
- Jaaninpuisto
- Tanhuankatu
- C. O. Malmin koulu
- Klassikonpolku
- Tammitie
- Metsätie
- Ketussuontie
- Uittamo City
- Kannuskatu
- Kannuskatu
- Uittamo City
- Jäkäläpuisto
- Jäkäläpuisto
- Rautatehtaankatu
- Kotimäenkatu
- Rautatehtaankatu
- Rautatehtaankatu
- Ahtolantie
- Polttolaitos
- Kytkinkatu
- Polttolaitos
- Ruopanhaara
- Hannunniittu
- Urushaara
- Vajossuonkatu
- Urusvuori
- Vajossuonkatu
- Urushaara
- Niemenkulmantie
- Lustikullantie
- Kollinmetsäntie
- Kakskertatalo
- Raustvuorentie
- Järvi-Peniläntie
- Kesäniementie
- Kierläntie
- Myllykyläntie
- Mäyrämäentie
- Kalliolantie
- Lemppäläntie
- Aatilan rantatie
- Aatilanhaka
- Kenraalintie
- Kutterintie
- Ollinkuja
- Sinapintie
- Orvontie
- Järvenpääntie
- Tiisalantie
- Hiidenkiukaantie
- Käpälämäki
- Vedenvuotama
- Brinkhall
- Latokari
- Lehtikuusitie
- Kakskerran kirkko
- Varvintie
- Kollintie
- and 3397 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
20 findings, ordered by severity.
Show every finding
- Warning28495 instances
Equal shape distance same coordinates (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'equal_shape_distance_same_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: equal_shape_distance_same_coordinates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3647 instances
3647 of 3647 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)
- Warning3077 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.)
Validator rule: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1814 instances
Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'equal_shape_distance_diff_coordinates_distance_below_threshold' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1424 instances
Some service calendars have no days of the week switched on.
Trips tied to these calendars never run; they are dead data that can mask real schedule problems.
Fix: Delete the empty calendars or set their service days. (A few minutes in your scheduling software.)
Validator rule: service_has_no_active_day_of_the_week · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning496 instances
496 of 24426 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)
- Warning99 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.)
Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning60 instances
Some scheduled trips move faster between stops than a transit vehicle can.
Usually a typo'd stop time; riders get arrival times no transit vehicle can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Validator rule: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning46 instances
Missing bike allowance (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_bike_allowance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: missing_bike_allowance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 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)
- Warning3 instances
3 of 24426 trips have no headsign.
Riders at the stop can't tell which direction a transit vehicle is going.
Fix: Populate trip_headsign to match what the transit vehicle displays. (Usually a bulk edit in your scheduling software.)
Validator rule: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning2 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.)
Validator rule: mixed_case_recommended_field · 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 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)
- Info264 instances
Big gap in service (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'big_gap_in_service' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: big_gap_in_service · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info36 instances
Platform without parent station (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'platform_without_parent_station' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: platform_without_parent_station · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info32 instances
Trip headsign matches intermediate stop (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'trip_headsign_matches_intermediate_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Unknown file (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unknown_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: 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).
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. States wheelchair access on 0% of stops and 98% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 323 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 98% 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 323 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 31 / 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 85 / 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/foli-turku/2026-07-18.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-18. 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.