← All agencies

Feed status · checked 2026-07-24

Kaunas city public transport

Based on the feed this agency publishes

Service mode Bus + Trolleybus

FDCBA

68.1 / 100

First scorecard for this agency

Catalogued in Kauno miestas, Lithuania.

Covers 342 daysAccessibility 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.

Checked for changes 44 minutes ago; last changed 44 minutes ago.

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

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

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

⏱ A default or per-trip field in your export.worth about +15 points in its category

Fix 03

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 (the file itself is absent) Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.

⏱ Two fields, set once in export settings.worth about +15 points in its category

How to make and check these changes

Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.

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 feed_info.txt with feed_start_date and feed_end_date to your export. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

Rider view: what this feed publishes

A quick read of rider-facing information in this feed.

Schedule visibility: The feed's last published service date is in 342 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.

Hi,

Our GTFS feed (Kaunas city public transport) scored D (68.1 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
   What: 996 of 996 stops don't say whether a wheelchair user can board there.
   Validator notice: scorecard_wheelchair_boarding_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_boarding_unknown/

2. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
   What: 6803 of 6803 trips don't say whether the vehicle is wheelchair accessible.
   Validator notice: scorecard_wheelchair_accessible_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_accessible_unknown/

3. Add feed_info.txt with feed_start_date and feed_end_date to your export.
   What: feed_info.txt is missing its start/end dates (the file itself is absent)
   Validator notice: scorecard_missing_feed_info_dates
   Guide: https://gtfsscorecard.org/fix/scorecard_missing_feed_info_dates/

Full scorecard: https://gtfsscorecard.org/agency/kaunas-city-public-transport/

Score by category

Correctness80.2 / 100

The MobilityData validator flagged 6 kinds of issue across 240 instances (0 error, 223 warning, 17 informational).

Freshness85.0 / 100

Service data covers the next 342 days.

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

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.

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

15 (green)
7 (green)
5 (green)
1 (green)
57 (red)
69B (red)
6B (red)
69 (red)
29 (red)
34 (red)
48B (red)
48C (red)
71T (red)
2 (green)
66 (red)
0 (red)
81 (red)
6G (teal)
3 (red)
6A (red)
28 (red)
6 (red)
35 (red)
32 (red)
33 (red)
38 (red)
39 (red)
36 (red)
37 (red)
14 (green)
46 (red)
13 (green)
43 (red)
16 (green)
44 (red)
41 (red)
10 (green)
48 (red)
18 (red)
19 (red)
17 (red)
23 (red)
21 (red)
22 (red)
61 (red)
4 (green)
47 (red)
63 (red)
65 (red)
45 (red)
26 (red)
42 (red)
40 (red)
8 (green)
35A (red)
54 (red)
64 (red)
68 (red)
67 (red)
65A (red)
31A (red)
20 (red)
49 (red)
31 (red)
10A (green)
47M (red)
11 (green)
12 (green)
9 (green)

Routes in Kaunas city public transport's feed
Route	Type	Line color
15 Partizanų g. - Centras - Partizanų g.	Trolleybus	green
7 Partizanų g. - Kaniūkai	Trolleybus	green
5 Petrašiūnai - Kėdainių g.	Trolleybus	green
1 Islandijos pl. - Vaidoto g.	Trolleybus	green
57 Urmo turgus - Šilainiai (Kumpiai)	Bus	red
69B Kovo 11-osios g. - Karmėlavos kapinės	Bus	red
6B Kauno pilis - Mastaičiai	Bus	red
69 Kovo 11-osios g. - LEZ - Neveronių žiedas	Bus	red
29 Kauno oro uostas - Geležinkelio stotis	Bus	red
34 Kauno ligoninė (Šilainiai) - Prancūzų g.	Bus	red
48B Raudondvaris (Šilelis) - Kaniūkai	Bus	red
48C Raudondvaris (Didvyriai) - Kaniūkai	Bus	red
71T Romainiai - Kaniūkai	Bus	red
2 Islandijos pl. - Parodos g. - Kauno pilis	Trolleybus	green
66 R. Kalantos g. - Sporto mokykla	Bus	red
0 Tilto g. - Vaišvydavos pl. - Lentpjūvė	Bus	red
81 Romainiai - Šilainiai - Romainiai	Bus	red
6G Technikos g. - Garliava	Bus	teal
3 Kauno ligoninė (Šilainiai) - Onkologijos ligoninė	Bus	red
6A Kauno ligoninė (Šančiai) - Garliava	Bus	red
28 Urmo turgus (Partizanų g.) - Švenčionių g.	Bus	red
6 Technikos g. - Garliava	Bus	red
35 Vytėnai - Freda	Bus	red
32 Geležinkelio stotis - Ringaudai	Bus	red
33 Technikos g. - Palemonas	Bus	red
38 Geležinkelio stotis - Mega	Bus	red
39 Kauno ligoninė (Šilainiai) - Neveronių g. (Neveronys)	Bus	red
36 Prūsų g. - Technikos g.	Bus	red
37 Juozo Grušo meno gimnazija - Partizanų g. (Kauno termofikacijos elektrinė)	Bus	red
14 Islandijos pl. - Centras - Islandijos pl.	Trolleybus	green
46 Šlienava (Žiegždriai) - Kauno pilis	Bus	red
13 Islandijos pl. - Centras - islandijos pl.	Trolleybus	green
43 Vičiūnai (Slaugos ligoninė) - Kauno pienas	Bus	red
16 Partizanų g. - Centras - Partizanų g.	Trolleybus	green
44 Kauno pilis - Liucijanavos g.	Bus	red
41 Chemijos g. - Kaniūkai	Bus	red
10 Partizanų g. - Kėdainių g.	Trolleybus	green
48 Raudondvaris - Kauno pilis	Bus	red
18 VDU Žemės ūkio akademija (Ringaudai) - Geležinkelio stotis	Bus	red
19 Skubios pagalbos centras - Palemono keramika	Bus	red
17 Kauno ligoninė (Šilainiai) - Neveronių g.	Bus	red
23 Domeikava - Rokai	Bus	red
21 Kauno pilis - Saliai	Bus	red
22 Geležinkelio stotis - H. ir O. Minkovskių g.	Bus	red
61 Geležinkelio stotis - Vainatrakio kapinės	Bus	red
4 Islandijos pl. - Vaidoto g.	Trolleybus	green
47 Kleboniškis - Onkologijos ligoninė (Kreidos g.)	Bus	red
63 Kaniūkai - Mega	Bus	red
65 Kazliškiai - Bitininkų g. - Geležinkelio stotis	Bus	red
45 Kauno ligoninė (Šančiai) - Palemonas	Bus	red
26 Kauno pienas (Kitron-Novameta) - Kazliškiai	Bus	red
42 Technikumo g. - Kauno ligoninė (Šančiai)	Bus	red
40 Urmo turgus (Partizanų g.) - Kauno ligoninė (Šilainiai)	Bus	red
8 Draugystės g. - Varnių g.	Trolleybus	green
35A Vilniaus g. - Freda	Bus	red
54 Sargėnai - Onkologijos ligoninė	Bus	red
64 E. Volterio g. - Šilainių poliklinika - E. Volterio g.	Bus	red
68 Tilto g. - Vaišvydava	Bus	red
67 Tirkiliškiai - Skubios pagalbos centras	Bus	red
65A Prezidento V. Adamkaus gimnazija - Geležinkelio stotis	Bus	red
31A Technikumo g. - S. Dariaus ir S. Girėno g. - Kauno pilis	Bus	red
20 Partizanų g. - 2-asis fortas	Bus	red
49 Kauno pilis - Lampėdžiai	Bus	red
31 Technikumo g. - S. Dariaus ir S. Girėno g. - Mega	Bus	red
10A Partizanų g. - Kauno pilis	Trolleybus	green
47M Kleboniškis - Kalniečiai	Bus	red
11 Islandijos pl. - Kaniūkai	Trolleybus	green
12 Petrašiūnai - Klinikos - Petrašiūnai	Trolleybus	green
9 Petrašiūnai - Klinikos - Petrašiūnai	Trolleybus	green

This feed has 996 stops.

List every stop

Kalniečių turgavietė
Kalniečių turgavietė
Margava
Margava
Balio Buračo gimnazija
Narėpai
Narėpai
Biruliškės
K. Petrausko
Biruliškės
Karmėlava
Karmėlava
2-oji Karmėlava B
2-oji Karmėlava A
Akademijos miestelis
Savanorių pr. A
Savanorių pr. B
Kaniūkų 1-oji g.
Breslaujos g. A
2-oji Karmėlava B
Griunvaldo g. A
Moliakelio g. B
Moliakelio g. A
Užvingių g. A
Užvingių g. B
9-ojo Forto g. A
9-ojo Forto g. B
Senukai B
Saliai
S. Žukausko g. A
Alsėdžių g. B
Oro uosto g. B
Kėdainių g. B
Panerys B
Panerys A
Vinčų g. B
Prūsų g. A
Prietilčio g. B
Prietilčio g. A
M. K. Čiurlionio tiltas E
Ašmenos 1-oji g. A
Ašmenos 1-oji g. B
Akademijos miestelis B
Avilių g.
Radviliškio g.
Kaniūkai B
VDU klasikinio ugdymo licėjus A
A. Juozapavičiaus pr. B
A. Juozapavičiaus pr. A
Ledos kapinės
Tylos g. A
Oro uosto g. A
Pėsčiųjų tiltas A
Kleboniškio miško parkas B
Rokakiemio g. A
Lazdynėlių g. C
Europos pr.
Volungių g. A
Volungių g. B
M. ir P. Šalčių g. A
Romainiškių g. A
Romainiškių g. B
Romainių g. B
Romainių g. A
Sakalų g.
Būrio g.
Technikumo g.
Upytės g. A
Upytės g. B
Vaitapilės g.
Pėsčiųjų tiltas B
Birutės g. B
Aukštutinių Kaniūkų g. B
Aukštutinių Kaniūkų g. A
Paštuvos g. B
Paštuvos g. A
Liucijanavos g. A
Vijūkų g. A
Vijūkų g. B
Kudrėnų g. A
Kudrėnų g. B
Medekšinės g. B
Medekšinės g. A
Paltiškių g. B
Paltiškių g. A
Šilagirio g. A
Šilagirio g. B
Liucijanavos g. B
Žvalgų g.
Biruliškių g.
Biurų centras
Varžupio g.
Varžupio g.
Noreikiškės A
Noreikiškės B
Užupio g. A
Užupio g. B
Rambyno g. A
Stirnų g. A
Stirnų g. B
Kauno šiltadaržiai A
Vainatrakio kapinės
Švyturių g.
Keleivių išlaipinimo aikštelė
Kauno ligoninė C
Skubios pagalbos centras
Kauno ligoninė A
Urmo turgus
Seniava B
Titnago g. B
Titnago g. A
Seniavos kapinės B
Seniavos kapinės A
Rietavo g.
Tilto g. D
Rambyno g. B
Kleboniškio miško parkas A
Didvyriai
Jūros g.
Kauno pienas D
Urmo turgaus aikštelė
Chemijos g. A
Jonučių g.
Vaitiškės g. A
Vaitiškės g. B
Mokolų g. B
Mokolų g. A
Lygioji g. A
Lygioji g. B
Svirplių takas B
Mastaičiai
2-ieji Rokai B
Paraželiai B
Raželiai B
Vainatrakio sankryža A
Raželiai A
Paraželiai A
2-ieji Rokai A
Amalė B
Amalė A
Rasos g.
Aluonos g. B
1-ieji Ramučiai
Gėlių g. B
Gėlių g. A
Balio Buračo gimnazija
Žiedų g.
Hella B
E. Volterio g. A
Fitsout B
Hella A
LEZ3
LEZ1
LEZ2
Vilties g. B
Naujadvario g. A
Naujadvario g. B
Pilviškių g. B
Vaišvydava C
Tirkiliškių g. A
Tirkiliškių g. B
Chodkevičių g. B
Chodkevičių g. A
S. Banaičio g. B
S. Banaičio g. A
A. Žmuidzinavičiaus g. B
A. Šapokos g. B
K. Čerbulėno g. A
B. Brazdžionio g. B
B. Brazdžionio g. A
Lazdynėlių g. B
Lazdynėlių g. A
Liucijanavos g. C
Vilties g. A
Alšėnų g. B
Jono Basanavičiaus gimnazija A
Jono Basanavičiaus gimnazija B
Vytauto Didžiojo tiltas B
Knygnešių g. A
Knygnešių g. B
Rokelių g. B
Rokelių g. A
A. Žmuidzinavičiaus g. A
Neveronių žiedas
Gandrų g. B
Gandrų g. A
Jovarų g. A
Jovarų g. B
Pilėnų g. B
Pilėnų g. A
Naujosios Karmėlavos kapinės B
Svirplių takas A
Alšėnų g. A
Tirkiliškiai
Kauno IX forto muziejus
Marių g. B
Marių g. A
Jazminų g. B
Jazminų g. A
Dieverių g.
Lavyso g. A
Lavyso g. B
Spindulio g. A
Prezidento V. Adamkaus gimnazija C
Fitsout A
Continental C
Vaidoto g. A
9-asis fortas A
Hollister
Continental A
Senosios Vainatrakio kapinės A
Senosios Vainatrakio kapinės B
Girionių aikštelė
Ramučių kultūros centras B
1-ieji Sergeičikai B
2-ieji Sergeičikai B
Lelijų g. B
Krašto g. B
Krašto g. A
Lelijų g. A
2-ieji Sergeičikai A
1-ieji Sergeičikai A
Ramučių kultūros centras A
Garažų g. C
Raudondvario seniūnija
A. ir A. Kriauzų pradinė mokykla
Pilies g.
J.Naujalio g.
Eglių g.
J.Janonio g.
Kaniūkai išlaipinimas
Žalgirio g. -1
Žalgirio g. -2
Dobilų g.
Vejuonos g.
Lomankos g.
Svarstyklės A
Sankryža B
Sankryža A
Romaškiai B
Voškoniai B
Voškonių aikštelė
Romaškiai A
Šilelis
9-asis fortas B
Giraitė B
Giraitė A
Hegelmann
Didvyriai B
Tvenkinys
and 746 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

11 findings, ordered by severity.

Show every finding

Warning6803 instances
6803 of 6803 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)
Warning996 instances
996 of 996 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)
Warning193 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)
Warning29 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no transit vehicle is scheduled to arrive.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Validator rule: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
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 (opens the validator rules on an external site)
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 (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)
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 (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 transit vehicle 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.)
Validator rule: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info1 instance
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.)
Validator rule: big_gap_in_service · 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 0% of trips; the mark needs 90% of each.

Valid Met: Passes validation with no errors.
Current Met: Service data covers the next 342 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.

Can riders use it?

Checks beyond structural validation: places where the feed is valid but a rider still could not travel.

29 of 996 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.

These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.

Clears the Google and Apple Maps four-week coverage bar. This feed has 342 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 80 / 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 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.

[![Kaunas city public transport GTFS data quality grade: D](https://gtfsscorecard.org/data/artifacts/kaunas-city-public-transport/badge.svg)](https://gtfsscorecard.org/agency/kaunas-city-public-transport/)

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/kaunas-city-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.

GTFS Scorecard. (2026). Kaunas city public transport GTFS feed-quality record, dated 2026-07-24 (grade D (68.1/100), rubric v1.2, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 68bd440ec4f7…). https://gtfsscorecard.org/data/artifacts/kaunas-city-public-transport/2026-07-24.json

@misc{gtfsscorecard-kaunas-city-public-transport-2026-07-24,
  title        = {Kaunas city public transport GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/kaunas-city-public-transport/2026-07-24.json}},
  note         = {Checked 2026-07-24; rubric v1.2; gtfs-validator 8.0.1; reader archive profile raw-v1; grade D (68.1/100)}
}

Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.