Feed status · checked 2026-09-05
Waltti (Raasepori)
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Uusimaa, 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.3, validator 8.0.1.
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
435 of 435 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
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool
201 of 201 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ A default or per-trip field in your export.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
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
- 435 of 435 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
- 201 of 201 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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
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.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · 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 274 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% 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 11 kinds of issue across 84 instances (0 error, 40 warning, 44 informational).
Service data covers the next 274 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.
1 accessibility depth signal
22 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (41, 107L, 107k, 111, 111H, 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.
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 435 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.
- 103k (green)
- 104n (green)
- 107 (green)
- 107L (blue)
- 107k (blue)
- 111 (blue)
- 111H (blue)
- 115 (blue)
- 115H (blue)
- 116 (blue)
- 134 (green)
- 134n (green)
- 140k (green)
- 144k (green)
- 191 (blue)
- 192 (blue)
- 192F (blue)
- 192S (blue)
- 192T (blue)
- 192V (blue)
- 192k (blue)
- 201 (green)
- 201m (green)
- 201s (green)
- 202k (green)
- 206k (green)
- 251 (green)
- 261 (green)
- 41 (blue)
- 502 (green)
- 502k (green)
- 550 (green)
- 904 (yellow)
- 905 (yellow)
- 915 (yellow)
- 918 (yellow)
- 925 (yellow)
- 926 (yellow)
- 927 (yellow)
| Route | Type | Line color |
|---|---|---|
| 103k Karjaa-Persböle | Bus | green |
| 104n Fiskars_NG_Karjaa | Bus | green |
| 107 Mustio-Karjaa | Bus | green |
| 107L (Lohja)_Gerknäsmalmen_Mustio_Karjaa | Bus | blue |
| 107k Mustio-Karjaa-Kiilan koulu | Bus | blue |
| 111 (Hanko)_Tammisaari_Karjaa_Mustio_(Lohja) | Bus | blue |
| 111H (Hanko)-Skogby-Tammisaari-Karjaa-Mustio-(Lohja) | Bus | blue |
| 115 Karjaa-Mustio-Gerknäsmalmen-(Lohja) | Bus | blue |
| 115H Karjaa-Mustio-Gerknäsmalmen-(Lohja) | Bus | blue |
| 116 Karjaa_NG_Pohja_Fiskars_Ansku_(Sammatti_Lohja) | Bus | blue |
| 134 Fiskars-Pohja-Karjaa | Bus | green |
| 134n Fiskars-Pohja-KarjaaNG | Bus | green |
| 140k Kiilan koulu-Fiskars-Ansku | Bus | green |
| 144k Kiilan koulu-Karjaa-Ansku | Bus | green |
| 191 Karjaa_Kaunislahti_(Kirkkonummi) | Bus | blue |
| 192 Tammisaari_Karjaa_Kaunislahti-(HKI) | Bus | blue |
| 192F Fiskars-Pohja-Karjaa-(HKI) | Bus | blue |
| 192S Bromarv-Tammisaari-Helsinki | Bus | blue |
| 192T Tammisaari_Karjaa_Kaunislahti-(HKI) | Bus | blue |
| 192V Bromarv_Tenhola_Tammisaari_Karjaa_(HKI) | Bus | blue |
| 192k 192k_1_(HKI)_KL_Karjaa_Tsr_Tenhola_Höjdens_Bromarv | Bus | blue |
| 201 Tammisaari-Karjaa | Bus | green |
| 201m Österby_Tammisaari_Karjaa_Stenåker | Bus | green |
| 201s Karjaa-Tammisaari-Sairaala | Bus | green |
| 202k Horsbäck-Langansböle-Tammisaari | Bus | green |
| 206k Tammisaari-koulut-Snappertuna | Bus | green |
| 251 Tammisaari-Persböle | Bus | green |
| 261 Karjaa-Snappertuna-Tammisaari | Bus | green |
| 41 (Karjalohja)_Mustio_(Lohja) | Bus | blue |
| 502 Bromarv-Tenhola-Tammisaari | Bus | green |
| 502k Koulut-Tammisaari-Tenhola-Bromarv | Bus | green |
| 550 Tammisaari-Tenhola | Bus | green |
| 904 Antby-Karjaa-Antby | Bus | yellow |
| 905 Karjaan koulualue-Lövkulla-Backgränd-Brasby | Bus | yellow |
| 915 Ekenäs-Prästkulla-Höjdens | Bus | yellow |
| 918 Svenskby-Finby Post-Svedjekulla-Tenhola | Bus | yellow |
| 925 Snappertuna_Baggö_Tsaari-koulualue | Bus | yellow |
| 926 Skogby-Leksvall-Tsaaren koulualue | Bus | yellow |
| 927 Seminarieskolan_Langansböle_Gammelboda | Bus | yellow |
List every stop
- Bromarvs butik V
- Törvesbro vs Ö
- Törvesbro vs V
- Trollböle Ö
- Trollböle L
- Krokby Ö
- Krokby V
- Knipnäs N
- Knipnäs S
- Djupbäck Ö
- Djupbäck S
- Kasaby
- Backgränd
- Malmkulla Ö
- Malmkulla V
- Hammarvägen S
- Hammarvägen N
- Österby skola S
- Österby skolan N
- Svedenvägen V
- Svedenvägen Ö
- Brinkbacka V
- Brinkbacka Ö
- Broby N
- Broby S
- Brokarls Ö
- Raseborgs Slottsväg vs V
- Raseborgs Slottsväg vs Ö
- Huskvarn V
- Tenala No
- Begravningsplats V
- Germundbyvägen N
- Brudbäck V
- Brudbäck Ö
- Kyrkmalm Ö
- Kyrkmalm V
- Talludden Ö
- Talludden V
- Brorskulla Ö
- Brorskulla V
- Bondböle Ö
- Bondböle V
- Lindö S
- Lindö V
- Gretarby Ö
- Gretarby V
- Bergbyvägen Ö
- Bergby vs
- Högböle Ö
- Högböle V
- Seukovägen Ö
- Seuko vs
- Tapels Ö
- Tapels V
- Moderviken V
- Moderviken Ö
- Framnäs V
- Framnäs Ö
- Solböle-Kägra Ö
- Solböle-Kägra V
- Kivitok Ö
- Kivitok V
- Gröna Lund Ö
- Gröna Lund V
- Pålarvbacken Ö
- Pålarvbacken V
- Rilax vs
- Huskvarn N
- Finby N
- Finby S
- Smedjebacksvägen Ö
- Smedjebacksvägen V
- Tvillinggränden Ö
- Tvillinggränden V
- Sandtagsgränd Ö
- Sandtagsgränd V
- Pojovägens korsning S
- Brasby V
- Romsarby vs
- Sannäsvägen N
- Sannäsvägen S
- Malmkulla V
- Malmkulla Ö
- Tokkola
- Fredriksstad V
- Fredriksstad Ö
- Nyby vs V
- Nyby vs Ö
- Sandbacka V
- Sandbacka Ö
- Åkerändavägen V
- Åkerändavägen Ö
- Mangårdvägen V
- Mangårdsvägen Ö
- Prästbackavägen S
- Prästbackavägen N
- Svartå bruk S
- Svartå bruk N
- Gropvägen V
- Gropv Ö
- Ekåsen Ö
- Ekåsen V
- Dragsvik V
- Dragsvik Ö
- Dragsviksvägen
- Gamla begravningsplats V
- Langasbölevägen
- Bäljars V
- Kilavägen N
- Kiilan koulu V
- Kiilan koulu Ö
- Nesslingsgatan V
- Svartå skola V
- Svartå Matkahuolto
- Lindersvägen Ö
- Askvägen V
- Svartå spannmålsförråd Ö
- Svartå spannmålsförråd V
- Svartå skola Ö
- Bollstad
- Stegelbacken V
- Stegelbacken Ö
- Grangränd Ö
- Dönsbyvägen
- Dönsbyvägen V
- Näckens gränd Ö
- Lindersvägen V
- Marknadsplan
- Hakarinneskolan N
- Hakarinneskolan S
- Ekenäs simhall
- Raseborgsvägen V
- Raseborgsvägen Ö
- Gamla begravningsplats Ö
- Nya begravninsplats Ö
- Nya begravninsplats V
- Sandgropen V
- Bulevarden
- Bäljars rondell V
- Bäljars Ö
- Bäljars rondell Ö
- Volmarsvägen V
- Kanaltorget Ö
- Grangränd V
- Karis begravningsplats Ö
- Karis begravningsplats V
- Lilla prästgård V
- Råckerstorg Ö
- Landsbro Ö
- Landsbro V
- Langansbölevägen V
- Formis S
- Slickovägen N
- Sköldargård 2 N
- Vistjärnavägen vs Ö
- Vistjärnavägen vs V
- Brokarls V
- Åminnefors Ö
- Tallbacka Ö
- Fiskarsvägen Ö
- Grabbskog S
- Sköldargård 2 S
- Pojo busstation
- Fiskars (Pojo)
- Bromarvs butik Ö
- Snappertuna skola
- Ekenäs busstation
- Gamla Tenalavägen N
- Högkulla S
- Högkulla N
- Storsvängen N
- Sköldargård 1 Ö
- Sköldargård 1 V
- Formis N
- Gamla Tenalavägen S
- Storsvängen S
- Västerby skola Ö
- Sockenvägen
- Tenhola Bygdegården Ö
- Lilla prästgård Ö
- Albackavägen Ö
- Svedjaträsket Ö
- Svedjaträsket V
- Svedjaträsket vägskäl N
- Trollbövägen Ö
- Trollbövägen V
- Västerby skola V
- Leksvallsvägen N
- Harparskog
- Tenhola Bygdegården V
- Alingsåsgatan Ö
- Albackavägen V
- Almasvägen Ö
- Almasvägen V
- Svedjaträsket västra V
- Baggövägen N
- Baggövägen S
- Högbacka Ö
- Högbacka V
- Tenala skola
- Bromarv kyrka V
- Raseborgs sjukhus
- Karis Resecenter 1
- Karis Resecenter 2
- Karis Resecenter 3
- Karis Resecenter 4
- Karis Resecenter
- Fiskars Wärdshus N
- Österby Neste N
- Askvägen Ö
- Gålisjövägen N
- Polishusets ramp Ö
- Norråkersgatan Ö
- Svedjaträsket västra Ö
- Pentby omfartsvägen Ö
- Pentby omfartsvägen V
- Orrgatan
- Parkourparken
- Skogby V
- Skogby Ö
- Leksvall västra vs Ö
- Storträskskogen V
- Storträskskogen Ö
- Mellankärrsvägen V
- Mellankärrsvägen Ö
- Plantskolevägen V
- Plantskolevägen Ö
- Harabastuvägen V
- Harabastuvägen Ö
- Leksvall östra vs V
- Leksvall östra vs Ö
- Prästkullavägen V
- Prästkullavägen Ö
- Trollböle Ö
- Trollböle V
- Västerby V
- Västerby Ö
- Österby V
- Österby Ö
- Dragsvik riksväg Ö
- Langansböle gamla riksvägen V
- Langansböle gamla riksvägen Ö
- Langansböle nya riksvägen V
- Langansböle nya riksvägen Ö
- Gropvägen Ö
- Horsbäck Sparhallen V
- Horsbäcksvägen V
- Horsbäcksvägen Ö
- Snappertuna västra vs V
- Snappertuna västra vs Ö
- and 185 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
15 findings, ordered by severity.
Show every finding
- Warning435 instances
435 of 435 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)
- Warning201 instances
201 of 201 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the bus 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)
- Warning22 instances
Some route colors don't contrast with their text color.
Route badges get hard to read, most of all for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Finding code: route_color_contrast · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning7 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.)
Finding code: unexpected_enum_value · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning6 instances
Some rider-facing names are in ALL CAPS or all lowercase.
ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 instances
Some scheduled trips move faster between stops than a bus can.
Usually a typo'd stop time; riders get arrival times no bus can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: 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
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)
- 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.)
Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info13 instances
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info9 instances
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)
- Info4 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.)
Finding code: platform_without_parent_station · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info3 instances
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the bus 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)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Conformance mark Not yet
One requirement remains for this feed to earn the conformance mark. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 274 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 0% 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 274 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 67 / 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 38 / 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/waltti-raasepori/2026-09-05.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-09-05. 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.