GTFS Scorecard
← All agencies

Feed status · checked 2026-07-18

Waltti (Kouvola)

Based on the feed this agency publishes

Service mode Bus

75.8 / 100

First scorecard for this agency

Catalogued in Kymenlaakso, Finland.

Covers 323 daysAccessibility gapsRealtime not yet published

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

Fix 01

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

1108 of 1152 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 +24 points in its category

Fix 02

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

Fix 03

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

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.

  1. 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.

  2. 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.

  3. 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. 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 3.8% of stops and 100% 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

Correctness78.0 / 100

The MobilityData validator flagged 7 kinds of issue across 20944 instances (0 error, 20919 warning, 25 informational).

Freshness100.0 / 100

Service data covers the next 323 days.

Rider experience53.5 / 100

4% of stops state wheelchair accessibility (1% marked accessible, 3% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.

Accessibility39.9 / 100

4% of stops state accessibility (1% marked accessible). Reflects what the feed states, not verified physical usability.

1 accessibility depth signal

  • 5 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (2, 6, 6K, 6T, 6A).

    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.

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.

Realtime qualityNot yet measured

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 data

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

  • 1 (green)
  • 10 (red)
  • P1 (black)
  • P2 (black)
  • P3 (black)
  • P4 (black)
  • P5 (black)
  • P6 (black)
  • P7 (black)
  • P8 (black)
  • 15 (green)
  • 15B (green)
  • Kvl - Taavetti (gray)
  • 2 (brown)
  • 3 (gray)
  • 32 (black)
  • 34 (black)
  • 35 (black)
  • 44 (black)
  • 44B (black)
  • 48 (black)
  • 5 (brown)
  • 5A (brown)
  • 5B (brown)
  • 53 (black)
  • 53A (black)
  • 54 (black)
  • 55 (black)
  • 56 (black)
  • 59 (black)
  • 6 (teal)
  • 60 (black)
  • 61 (black)
  • 6K (teal)
  • 62 (black)
  • 6T (teal)
  • 63 (black)
  • 63K (black)
  • 6A (teal)
  • 64 (black)
  • 7 (black)
  • 7B (black)
  • 7V (black)
  • 8 (black)
  • 9 (red)
  • 9A (red)
  • 9K (red)
Routes in Waltti (Kouvola)'s feed
RouteTypeLine color
1 Lapinmäki – Kuusankoski – Keskusta – Rekola (Kvl)Busgreen
10 Mielakka – Keskusta – Lehtomäki – Ratamo – Keskusta – MielakkaBusred
P1 Keskusta - Kaunisnurmi - Prisma - VeturiBusblack
P2 Keskusta - Ratamo - Kotiharju - Lehtomäki - Pikku Palomäki - Ratamo - KeskustaBusblack
P3 Keskusta - Vahtero - Eskolanmäki - Rekola (Kvl) - KeskustaBusblack
P4 Voikkaa – Markank. – Tähtee – Ksnk.Busblack
P5 Kuusankoski –Rekola (Ksnk) – Mäkikylä – KuusankoskiBusblack
P6 Kuusankoski – Rantakulma – Kymintehdas – Mäyrämäki – Veturi – Ratamo – KeskustaBusblack
P7 Anjala – Inkeroinen – Myllykoski – UmmeljokiBusblack
P8 Anjala - Inkeroinen - Keltakangas - Myllykoski - Ummeljoki - Koria - Veturi - Prisma - Ratamo - HansaBusblack
15 Matkakeskus - Verla - Repovesi - OrilampiBusgreen
15B Hillosensalmi - RepovesiBusgreen
Kvl - Taavetti Kouvola - TaavettiBusgray
2 Koria - Keskusta - ValkealaBusbrown
3 Lapinmäki - Kuusankoski - Keskusta - Myllykoski - Inkeroinen - AnjalaBusgray
32 Anjala - Ummeljoki - MyllykoskiBusblack
34 Myllykoski - InkeroinenBusblack
35 Anjala - Sippola - AnjalaBusblack
44 Värälä-Koria-Teuroinen-ElimäkiBusblack
44B Värälä - Nappa ABCBusblack
48 Ratula - Koskisto - Villikkala - ElimäkiBusblack
5 Matkakeskus – Valkeala – VekaranjärviBusbrown
5A Matkakeskus – Valkeala – Vekaranjärvi –TuohikottiBusbrown
5B Vekaranjärvi - Tuohikotti - Valkeala - MatkakeskusBusbrown
53 Vuohijärvi - ValkealaBusblack
53A Voikoski - Vuohijärvi - ValkealaBusblack
54 Voikkaa - Harju - ValkealaBusblack
55 Valkeala - Tirva - Utti - ValkealaBusblack
56 Valkeala– Tirva – Kaipiainen – Utti – ValkealaBusblack
59 Valkeala – Selänpää – JaalaBusblack
6 Elimäki – Koria – Keskusta – UttiBusteal
60 Utti - Sippola - Myllykoski - Tornionmäki - MatkakeskusBusblack
61 Kaipiainen – Sippola - Myllykoski – Tornionmäki – RatamoBusblack
6K Elimäki – Koria – Keskusta – UttiBusteal
62 Kaipiainen – Tornionmäki – RatamoBusblack
6T Elimäki – Koria – Keskusta – UttiBusteal
63 Matkakeskus – Tornionmäki – Utti – SippolaBusblack
63K Sippola - Utti - Kopterikuja - MatkakeskusBusblack
6A Elimäki - Koria - Keskusta - KaipiainenBusteal
64 Sippola - UttiBusblack
7 Lehtomäki – Keskusta – Veturi – Kuusankoski – PilkanmaaBusblack
7B Lehtomäki – Keskusta – Veturi – KuusankoskiBusblack
7V Lehtomäki – Keskusta – Veturi – Kuusankoski – PilkanmaaBusblack
8 Lehtomäki – Keskusta – VeturiBusblack
9 Jaala - Voikkaa - Kuusankoski - Keskusta - TornionmäkiBusred
9A Huhdasjärvi-Jaala-Voikkaa-Kuusankoski-Keskusta-TornionmäkiBusred
9K Kimola-Jaala-Voikkaa-Kuusankoski-Keskusta-TornionmäkiBusred

This feed has 1152 stops.

List every stop
  • Ratulantie-Koskistonoikotie th E
  • Ratulantie-Koskistonoikotie th P
  • Ratulantie Teutjoen silta E
  • Ratulantie 795
  • Ratulan koulu E
  • Ratulan koulu P
  • Ratula E
  • Pyöräsuontie E
  • Pyöräsuontie P
  • Myllärinmäki E
  • Myllärinmäki P
  • Isoaho E
  • Isoaho P
  • Ratulantie Haapalansuora E
  • Elimäki-Moisio-Ratula-risteys E
  • Harjunkorpi E
  • Harjunkorpi P
  • Raussilantie 630 E
  • Raussilantie 630 P
  • Nokkalantie L
  • Nokkalantie I
  • Raussila E
  • Raussila P
  • Ronninoja E
  • Ronninoja P
  • Raussilantie Kolkanmetsä E
  • Raussilantie Kolkanmetsä P
  • Raussilantie E
  • Raussilantie P
  • Raussila th Elimäentie E
  • Lidl Inkeroinen P
  • Keskustie E
  • Keskustie P
  • Takahaantie E
  • Takahaantie P
  • Lauttojankulma E
  • Lauttojankulma P
  • Yläpää E
  • Yläpää P
  • Autiontie E
  • Autiontie P
  • Kymenrannantie E
  • Kymenrannantie P
  • Kiskotie E
  • Kiskotie P
  • Rantapelto E
  • Jokisillantie 452
  • Kurenojantie E
  • Jokirinne P
  • Lopotti E
  • Lopotti P
  • Lähteenmäki E
  • Lähteenmäki P
  • Kuolionoja E
  • Kuolionoja P
  • Jokisillantie P
  • Jokisillantie E
  • Rautakorpi th L
  • Kurkisuontie I
  • Kurkisuontie L
  • Narjuksentie Karttenniementie L
  • Mattila I
  • Törröntien risteys Selänpääntie E
  • Törröntien risteys Selänpääntie P
  • Impivaarankuja E
  • Vanumaantie P
  • Nypintie E
  • Nypintie P
  • Sammalsuo E
  • Sammalsuo P
  • Kukonmäki E
  • Kukonmäki P
  • Pihlajasaari E
  • Pihlajasaari P
  • Kankaantien-Vekarantien risteys E
  • Keonmäentie L
  • Keonmäentie I
  • Turkia L
  • Turkia I
  • Kokkokalliontie I
  • Lommintie L
  • Lommintie I
  • Liikkalantie Seppälänmäki I
  • Liikkalantie Seppälänmäki L
  • Liikkalan mylly L
  • Utti Utintien risteys E
  • Lennostontie P
  • Lennostontie E
  • Utin koulu P
  • Utin koulu E
  • Kattilaharju th P
  • Kattilaharju th E
  • Kattilaharju P
  • Kattilaharju E
  • Pahanojankallio E
  • Pahanojankallio P
  • Utintie-Saverontie E
  • Utintie-Saverontie P
  • Pourunmäki E
  • Kiikunjoki P
  • Kiikunjoki E
  • Pöytäsuontie P
  • Pöytäsuontie E
  • Savero entinen kauppa P
  • Savero entinen kauppa E
  • Savero Pihtsalmi th P
  • Savero Pihtsalmi th E
  • Metso th Pasintie P
  • Kiuri E
  • Kiuri P
  • Kiurunvirta P
  • Kiurunvirta E
  • Nurmelankuja E
  • Nurmelankuja P
  • Ukonpolku E
  • Ukonpolku P
  • Hauklahdentie E
  • Hauklahdentie P
  • Tirva th E
  • Tirva th P
  • Pasi E
  • Huhdasjärvi P (Ei pysäkkimerkkiä)
  • Huhdasjärvi E
  • Siikava E
  • Oravakorpi P
  • Oravakorpi E
  • Jaalan koulu Mäntyharjuntie P
  • Vanttola P
  • Soppi Takamaantie E
  • Soppi Takamaantie P
  • Lehtimäentie E
  • Lehtimäentie P
  • Pikkukuja E
  • Pikkukuja P
  • Terveyskeskus (Elimäki) I
  • Terveyskeskus (Elimäki) L
  • Kunnanvirasto (Elimäki) I
  • Kunnanvirasto (Elimäki) L
  • Koulukeskus (Elimäki) I
  • Koulukeskus (Elimäki) L
  • Peippola L
  • Peippola I
  • Peippolan koulu I
  • Peippolan koulu L
  • Kytöaho-Niskala risteys P
  • Nutikkamäki E
  • Nutikkamäki P
  • Niskala P
  • Niskala E
  • Harjuntie th P
  • Harju I
  • Harju L
  • Pessantie L
  • Rohtokalliontie E
  • Rohtokalliontie P
  • Lamminranta E
  • Lamminranta P
  • Sääksniementie E
  • Maitolahti P
  • Maitolahti E
  • Askontie P
  • Horppu L (ei pysäkkimerkkiä)
  • Häkämäki P
  • Jyräänkoski E
  • Keltakangas ympyrä E
  • Keltakangas P
  • Keltakangas E
  • Joentaustantie P
  • Joentaustantie E
  • Säkkijärvenpolku E
  • Säkkijärvenpolku P
  • Säkkijärventie E
  • Säkkijärventie P
  • Karhunkangas P
  • Karhunkangas E
  • Silvasti E
  • Silvasti P
  • Okatie P
  • Okatie E
  • Tehtaanmäen koulu P
  • Pasi L
  • Lehtomäki Utunmäentie P
  • Kotatie I
  • Ahventie L
  • Haukitie L
  • Huovihongantie P
  • Käpylänkatu I
  • Käpylänkatu L
  • Saarennonkatu L
  • Kurvi E
  • Kurvi P
  • Kuusanlammentie E
  • Kuusanlammentie P
  • Suurensuonkatu L
  • Kyllikintie P
  • Kyllikintie E
  • Matkakeskus H1
  • Tapiontie I
  • Ravirata E
  • Ravirata P
  • Pikku-Palomäki
  • Petäjätie E
  • Ratamo PALI
  • Hallituskatu L
  • Kauppaoppilaitos L
  • Kauppaoppilaitos I
  • Utinkatu I
  • Marjoniemi P
  • Torikatu
  • Kauppamiehenkatu
  • Pistokatu E
  • Pistokatu P
  • Prikaatintie L
  • Prikaatintie I
  • Harjunraitti E
  • Harjunraitti P
  • Hongistontie I
  • Savontalontie E
  • Prisma E
  • Tommolankatu P
  • Kaitilankatu L
  • Kymen Lukko P
  • Kotiharjuntie P
  • Sepänkatu E
  • Sepänkatu P
  • Kellomäki E
  • Kellomäki L
  • Torvitie P
  • Torvitie E
  • Kaunisnurmi I
  • Kaitilankatu I
  • Kaunisnurmi L
  • Kaupinkatu L
  • Niittäjänkaari E
  • Myllypuronkatu E
  • Kärrikuja L
  • Lypsäjäntie L
  • Lauttarannantie E
  • Palovartijantie I
  • Haminantie I
  • Vinttikaivontie I
  • Sippolankatu I
  • Eskolanmäki Tasankotie I
  • Kasarminmäki AMK L
  • Kasarminmäki AMK I
  • Vesitorni I
  • Kaarnatie I
  • Koulukatu P
  • Salpausselänkatu I
  • Jaakonpuisto L
  • and 902 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

10 findings, ordered by severity.

Show every finding
  • Warning20916 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

  • Warning1108 instances

    1108 of 1152 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

  • 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

  • Warning1 instance

    Route short name too long (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'route_short_name_too_long' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Validator rule: route_short_name_too_long · See MobilityData GTFS Validator rules

  • Warning1 instance

    Many of the feed's trips don't run at all in the next 7 days.

    It usually means old service periods are still in the export, making the feed bigger and harder to check.

    Fix: Trim past service periods the next time you export. (One setting in most export tools.)

    Validator rule: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules

  • 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

  • Info15 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.)

    Validator rule: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules

  • Info8 instances

    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

  • Info2 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

  • 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

Conformance mark Not yet

This feed is close to the conformance mark. States wheelchair access on 4% 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 323 days.
Accessible Not yet
States wheelchair access on 4% 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.

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 78 / 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 54 / 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.

Waltti (Kouvola) GTFS data quality grade: C

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/waltti-kouvola/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.