GTFS Scorecard
← All agencies

Feed status · checked 2026-07-24

Rokiškis public transport

Based on the feed this agency publishes

Service mode Bus

67.1 / 100

First scorecard for this agency

Catalogued in Rokiškis, Lithuania.

Review service end dateAccessibility gapsRealtime not yet published

Official municipality-level export from the national GTFS directory. Counted as one feed record, not as a census of distinct operators.

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

308 of 308 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

Fix 02

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

184 of 184 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

Fix 03

Populate trip_headsign to match what the bus displays.Likely your export tool

184 of 184 trips have no headsign. Riders at the stop can't tell which direction a bus is going.

⏱ Usually a bulk edit in your scheduling software.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.

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

  3. Populate trip_headsign to match what the bus displays. · 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 states that service is published through 2099-12-31. This may be intentional or a placeholder; confirm current service with the transit operator.
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

Correctness88.8 / 100

The MobilityData validator flagged 4 kinds of issue across 32 instances (0 error, 18 warning, 14 informational).

Freshness85.0 / 100

Service is published through 2099-12-31. It may be intentional, but confirm the end date before treating the feed as maintained.

Rider experience22.5 / 100

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.

Accessibility0 / 100

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

1 accessibility depth signal

  • 1 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Panemunėlio g. st.").

    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.

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.

  • 4M (green)
  • 4L (green)
  • 13 (green)
  • 3 (green)
  • 72 (green)
  • 74 (green)
  • 60 (green)
  • 51 (green)
  • 53 (green)
  • 19 (green)
  • 31 (green)
  • 11 (green)
  • 30 (green)
  • 23 (green)
  • 12 (green)
  • 14 (green)
  • 21 (green)
  • 27 (green)
  • 32 (green)
  • 4 (green)
  • 18 (green)
Routes in Rokiškis public transport's feed
RouteTypeLine color
4M Geležinkelio stotis-Miškų urėdija-Geležinkelio stotisBusgreen
4L Geležinkelio stotis-Psichiatrijos ligoninė-Geležinkelio stotisBusgreen
13 Rokiškis-Obeliai-Zarinkiškis-KriaunosBusgreen
3 Centras - KavoliškisBusgreen
72 Rokiškis - KazliškisBusgreen
74 Rokiškis - Pandėlys per KazliškįBusgreen
60 Jūžintai-Aušrėnai-RokiškisBusgreen
51 Rokiškis--Lašai-Jūžintai-KamajaiBusgreen
53 Duokiškis-KamajaiBusgreen
19 Rokiškis - JūžintaiBusgreen
31 Rokiškis - Skemų socialinės globos namaiBusgreen
11 Rokiškis - ObeliaiBusgreen
30 Rokiškis -Duokiškis- Kamajai - SalosBusgreen
23 Rokiškis - Lukštai - Bučiūnai - ObeliaiBusgreen
12 Rokiškis - Onuškis - AlksniaiBusgreen
14 Rokiškis - Juodupė-DidsodėBusgreen
21 Rokiškis - Laibgaliai - KriaunosBusgreen
27 Rokiškis - Žiobiškis - PanemunisBusgreen
32 Rokiškis - Čedasai - Daliečiai - SuvainiškisBusgreen
4 Geležinkelio stotis - Psichiatrijos ligoninė - Miškų ūrėdijaBusgreen
18 Rokiškis - Panemunėlio geležinkelio stotis - AugustinavaBusgreen

This feed has 308 stops.

List every stop
  • Lukštai
  • Pasarčiai
  • Baršėnai
  • Kurkliečiai
  • Radišiai
  • Pagojė
  • Jutkiai
  • Jūžintai
  • Lukšiai
  • Pagojė
  • Laibgaliai
  • Dideliškis
  • Spiečiūnai II
  • Mikrorajonas
  • Onuškis 2
  • Steponiai
  • Baltakarčiai
  • Čedasai
  • Mičiūnai
  • Baltušiai
  • Skemai I
  • Mickūnai
  • Palūšniai
  • Sėlynė
  • Pervaža
  • Suvainiškis
  • Rokiškėlės
  • Degsniai
  • Ežeras
  • Kurkliečiai
  • Girininkija
  • Minkūnai
  • Panemunis
  • Dambrotiškis
  • Antanašė
  • Apuniškis
  • Vajetėliai
  • Lašai
  • Zarinkiškiai
  • Joneliškės
  • Mickūnai
  • Panemuniai
  • Daliečiai I
  • Bulvėniškis
  • Maineivos
  • Sodai
  • Skemai II
  • Čepeliškė
  • Obelių dirbtuvės
  • Joneliškės
  • Pagrundžiai
  • Aušros
  • Naujasodė
  • Piepaliai
  • Didėja
  • Kesčionys
  • Aleksandravėlė
  • Radišiai
  • Kontora
  • Naujasodė
  • Radutė
  • Kirvelkiai
  • Papartynė
  • Centras
  • Sodai
  • Apuniškis
  • Baršėnai
  • Uljanava
  • Gediškiai
  • Dideliškis
  • Keležeriai
  • Gel. stotis
  • Skrebiškis I
  • Stramiliai
  • Skemų kelias
  • Salos
  • Ilgalaukiai
  • Obeliai
  • Parduotuvė
  • Galažeriai
  • Grybas
  • Varliai
  • Aukštakojai
  • Patilčiai
  • Sodeliai 1
  • Skriduliai
  • Beičiai
  • Pasarčiai
  • Kirvelkiai
  • Lukštai
  • Kriaunos
  • Degsniai
  • Misiūniškis
  • Medelynas
  • Vilkoliai
  • Mokykla
  • Skriduliai
  • Vyžuona
  • Minkūnai
  • Rokiškėlės
  • Pandėlio g.
  • Mitragalys
  • Šemetos
  • Vajetėliai
  • Paliepis
  • Simoniškis
  • Mokykla
  • Palūšniai
  • Varaščina
  • Degeniai
  • Kavoliškis
  • Gel. stotis
  • Žiobiškis II
  • Poliklinika
  • Ilgalaukiai
  • Stoniškiai
  • Trakas
  • Daliečiai II
  • Juozapava
  • Laibgaliai
  • Panemunis
  • Girininkija
  • Dagiliai
  • Suvainiškis
  • Mikrorajonas
  • Kavoliškis
  • Andronys
  • Bagdoniškis II
  • Kumpelka
  • Ziboliai
  • Dumbliai 2
  • Mičiūnai
  • Mičiūnai
  • Ignotiškis
  • Gačionys
  • Radutė
  • Vyžuona
  • Jutkiai
  • Brizgiai
  • Taručiai
  • Uljanava
  • Cipriškis
  • Brizgiai
  • Simoniškis
  • Paliepis
  • Onuškis 1
  • Medelynas
  • Ligoninė
  • Rokiškio autobusų stotis
  • Alksniai
  • Onuškio dvaras 1
  • Onuškio dvaras 2
  • Alksniai
  • Panemunėlio g. st.
  • Aukštakalniai
  • Viadukas
  • Skemai III
  • Dirbtuvės
  • Perkūno
  • Perkūno
  • Centras
  • Kumpelka
  • Šileikiai
  • Šileikiai
  • Juodalungė
  • Juodalungė
  • Juodupė
  • Lašai
  • Šilagalys
  • Poliklinika
  • Geležinkelio stotis
  • P.C. Senukai
  • Duokiškis
  • Trumponys
  • Gaveikiai
  • Nemeniūnai
  • Kamajų dvaras
  • P.C. Senukai
  • Kavoliškis
  • Kazliškis
  • Mokykla
  • Taikos
  • Draugystė
  • Miškų urėdija
  • P.Cvirkos
  • P.Cvirkos
  • Pervaža
  • Autobusų stotis
  • Autobusų stotis
  • Centas
  • Aušros
  • Laisvės
  • Kalneliškis
  • Posūkis
  • Posūkis
  • Kavoliškis II
  • Kavoliškis I
  • Kavoliškis I
  • Vaneikiai
  • Titeliai
  • Klišiai
  • Petrešiūnai
  • Sniegiai
  • Greviškiai
  • Žeimiai
  • Poilsiavietė
  • Audronys
  • Paužolka
  • VMĮ
  • Papiškiai
  • Centras
  • Spečiūnai II
  • Durpynas
  • Baltakarčiai
  • Spiečiūnai I
  • Skrebiškis I
  • Juozapava
  • Didsodė
  • Čedasų km.
  • Rukšiai
  • Kaireliai
  • Gagiškiai
  • Panemunėlis
  • Steponiai
  • Mokykla
  • Sodeliai 2
  • Steponiai
  • Taručiai
  • Onuškis 1
  • Varaščina
  • Čepeliškė
  • Degeniai
  • Spečiūnai I
  • Skrebiškis II
  • Gerkonys
  • Gerkonys
  • Žiobiškis I
  • Stramiliai
  • Durpynas
  • Aukštakojai
  • Bulvėniškis
  • Jūžintai
  • Maineivos
  • Pandėlio g.
  • Dagiliai
  • Moškėnai
  • Sėlynė
  • Kamajai
  • Einikiai
  • Kapinės
  • and 58 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
  • Warning308 instances

    308 of 308 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

  • Warning184 instances

    184 of 184 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.)

    Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference

  • Warning184 instances

    184 of 184 trips have no headsign.

    Riders at the stop can't tell which direction a bus is going.

    Fix: Populate trip_headsign to match what the bus displays. (Usually a bulk edit in your scheduling software.)

    Validator rule: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices

  • Warning17 instances

    Some route lines list the same point twice in a row.

    Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.

    Fix: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. (Usually one export setting.)

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

  • Warning1 instance

    A file GTFS asks for (usually feed_info.txt) is missing.

    feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.

    Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)

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

  • Warning1 instance

    feed_info.txt is missing its start/end dates (the file itself is absent)

    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

  • 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

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

  • Info1 instance

    Service extends far in the future (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Validator rule: service_extends_far_in_the_future · 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 0% of stops and 0% of trips; the mark needs 90% of each.

Valid Met
Passes validation with no errors.
Current Met
The published window is current, but its service end date is unusually distant; confirm that date is intentional.
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 clears the four-week coverage window, but its service end date is unusually distant. Confirm that date is intentional before treating it as evidence of ongoing maintenance. 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 89 / 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 22 / 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.

Rokiškis public transport GTFS data quality grade: D

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/rokiskis-public-transport/2026-07-24.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-24. 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.