← All agencies

Feed status · checked 2026-08-01

Klaipėda city public transport

Based on the feed this agency publishes

Service mode Bus

FDCBA

72.3 / 100

up 2.8 since 2026-07-31 · D → C

Catalogued in Klaipėdos miestas, Lithuania.

Covers 356 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.3, validator 8.0.1.

Checked for changes 9 hours ago; last changed 9 hours 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

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

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

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

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: 907 of 907 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

Agency: Klaipėda city public transport
Finding: scorecard_wheelchair_boarding_unknown
Feed evidence: 907 of 907 stops don't say whether a wheelchair user can board there.
Why it matters: Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Requested change: 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.
Evidence: https://gtfsscorecard.org/agency/klaipeda-city-public-transport/?finding=scorecard_wheelchair_boarding_unknown#finding-handoff

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. See this feed's finding-clearance log.
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. See this feed's finding-clearance log.
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. See this feed's finding-clearance log.

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 356 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 (Klaipėda city public transport) scored C (72.3 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: 907 of 907 stops don't say whether a wheelchair user can board there.
   Finding code: 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: 6903 of 6903 trips don't say whether the vehicle is wheelchair accessible.
   Finding code: 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)
   Finding code: scorecard_missing_feed_info_dates
   Guide: https://gtfsscorecard.org/fix/scorecard_missing_feed_info_dates/

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

Score by category

Correctness90.0 / 100

The MobilityData validator flagged 5 kinds of issue across 28 instances (0 error, 5 warning, 23 informational).

Freshness85.0 / 100

Service data covers the next 356 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.

This feed has 907 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.

102 (teal)
105 (teal)
41 (teal)
115 (teal)
29 (teal)
15B (teal)
19 (teal)
45 (teal)
112 (teal)
40 (teal)
1 (teal)
9A (teal)
5 (teal)
11A (teal)
26 (teal)
104 (teal)
16 (teal)
8E (green)
36 (teal)
109 (teal)
8 (teal)
43 (teal)
20 (teal)
27 (teal)
103 (teal)
34 (teal)
106 (teal)
11 (teal)
11B (teal)
116 (orange)
107 (teal)
110 (teal)
7 (teal)
25 (teal)
101 (teal)
108 (teal)
28 (teal)
10 (teal)
30 (teal)
31 (orange)
M8 (orange)
21 (teal)
M6 (orange)
21A (teal)
14A (teal)
2A (teal)
17 (teal)
2 (teal)
22A (teal)
4 (teal)
9 (teal)
22B (teal)
3 (teal)
14 (teal)
22 (teal)
46 (teal)
18 (teal)
6 (teal)
12A (teal)
12 (teal)
15 (teal)
1A (teal)
24 (teal)
23 (teal)
42 (teal)
4A (teal)
L1 (teal)

Routes in Klaipėda city public transport's feed
Route	Type	Line color
102 Gargždai - Endriejavas - Žadeikiai	Bus	teal
105 Gargždai - Šiūpariai - Svencelė	Bus	teal
41 Klaipėda (Autobusų stotis) - Dituva	Bus	teal
115 Klaipėda - Rusnė	Bus	teal
29 Kurėno st. - Agluonėnai	Bus	teal
15B Ligoninės - Normantai	Bus	teal
19 Autobusų parkas - Jūrininkų st.	Bus	teal
45 Klaipėda - Priekulė - Dreverna - Svencelė	Bus	teal
112 Gargždai - Antkoptis - Judrėnai	Bus	teal
40 Klaipėda (Naujojo Turgaus st.) - Dituva	Bus	teal
1 Autobusų stotis - VLG	Bus	teal
9A Turgus - VLG	Bus	teal
5 Žiedo st. (Kretingos g.) - Jūrininkų st.	Bus	teal
11A Kurėno st. - Šernų sodai	Bus	teal
26 Atgimimo aikštė - Radailiai - Eketė	Bus	teal
104 Gargždai - Pakalniškiai	Bus	teal
16 Mogiliovo g. - Smiltelės g. - VLG	Bus	teal
8E Ligoninės - Jūrininkų st.	Bus	green
36 Klaipėda - Ginduliai - Klemiškė II - Klaipėda	Bus	teal
109 Gargždai - Vaitelių sodai	Bus	teal
8 Autobusų stotis - Jūrininkų st.	Bus	teal
43 Klaipėda (Naujojo Turgaus st.) - SB Spengiai	Bus	teal
20 Smeltė - Taikos pr. - Naikupės g. - Smeltė	Bus	teal
27 Akropolis - SB Tolupis - SB Aisė	Bus	teal
103 Gargždai - Dovilai - Medsėdžiai	Bus	teal
34 Naujojo Turgaus st. - Šernų sodai	Bus	teal
106 Gargždai - Utriai	Bus	teal
11 Turgus - Lėbartai	Bus	teal
11B Kurėno st. - Dovilai	Bus	teal
116 Gargždai - Klaipėda	Bus	orange
107 Gargždai - Plikiai	Bus	teal
110 Gargždai - Dovilai - Klaipėda	Bus	teal
7 Klipščiai - Trušeliai - Klipščiai	Bus	teal
25 Autobusų stotis - Vaiteliai	Bus	teal
101 Vėžaičiai - Klaipėda	Bus	teal
108 Gargždai - Judrėnai	Bus	teal
28 Autobusų stotis - Šernų sodai	Bus	teal
10 Autobusų parkas - Statybininkų pr. - Smiltelės g. - Autobusų parkas	Bus	teal
30 Klaipėda - Ginduliai - Smilgynai - Slengiai - Klaipėda	Bus	teal
31 Klaipėda - Palanga - Palangos Oro Uostas	Bus	orange
M8 Jūrininkų st. - Taikos pr. - Ligoninės	Bus	orange
21 Akropolis - Jakai - Sudmantai - Ermitažas PROMO - Akropolis	Bus	teal
M6 Mogiliovo g. - Taikos pr. - Melnragė	Bus	orange
21A Turgus - Jakai	Bus	teal
14A Naujasis turgus - Turgus (Taikos pr.) - Turgus (Tilžės g.)	Bus	teal
2A Sportininkų g. - Debreceno g.	Bus	teal
17 Paupiai - Kalotė	Bus	teal
2 Kurėno st. - Sportininkų g.	Bus	teal
22A Statybininkų pr. - LEZ	Bus	teal
4 Statybininkų pr. - Giruliai	Bus	teal
9 Jūrininkų st. - Ligoninės	Bus	teal
22B Panevėžio g. - LEZ	Bus	teal
3 Naikupės g. - Ligoninės	Bus	teal
14 Arena - Klipščiai	Bus	teal
22 Jūrininkų st. - LEZ	Bus	teal
46 Klaipėda - Priekulė - Kintai - Ventė	Bus	teal
18 Kurėno st. - Panevėžio g.	Bus	teal
6 Mogiliovo g. - Melnragė	Bus	teal
12A Turgus - Draugystės geležinkelio stotis	Bus	teal
12 Turgus - VLG	Bus	teal
15 Mogiliovo g. - Ligoninės	Bus	teal
1A Turgus - VLG	Bus	teal
24 Universiteto st. - Karklė - Kunkiai	Bus	teal
23 Ligoninės - Žaliasis slėnis - Ligoninės	Bus	teal
42 Klaipėda (Naujojo Turgaus st.) - Vaiteliai - Rasa	Bus	teal
4A Statybininkų pr. - Giruliai	Bus	teal
L1 Pilies tiltas - Tauralaukio tiltas	Bus	teal

List every stop

Pilies st.
Turgaus st.
Turgaus st.
Nemuno st.
Senosios perkėlos st.
Teatro st.
Naujoji uosto st.
Naujoji uosto st.
J.Janonio st.
Atgimimo st.
Atgimimo st.
Bibliotekos st.
Bibliotekos st.
Lietuvininkų st.
Lietuvininkų st.
Žiedo st.
Kaštonų st.
Minijos st.
Skulptūrų parko st.
Skulptūrų parko st.
Viaduko st.
Viaduko st.
Autobusų parko st.
Medienos st.
Jaunystės st.
Paupių st.
Klemiškės st.
Klemiškės st.
Joniškės st.
Žemaičių st.
Žemaičių st.
Verpėjų st.
Verpėjų st.
Nendrių st.
Mokyklos st.
Kretingos st.
LCC tarptautinis universitetas
Treko st.
Treko st.
Panevėžio st.
Panevėžio st.
Mažojo kaimelio st.
Mažojo kaimelio st.
Nendrių st.
Sodų st.
Sodų st.
Botanikos sodo st.
Botanikos sodo st.
Ligoninės st.
Tauralaukio st.
Liepojos st.
Upelio st.
Liepojos st.
P.Lideikio st.
P.Lideikio st.
Universiteto st.
Universiteto st.
Girulių plento st.
Melnragės st.
Melnragės st.
Švyturio st.
Švyturio st.
Kopų st.
2-osios Melnragės st.
2-osios Melnragės st.
Pajūrio st.
Pajūrio st.
Girulių st.
Upelio st.
Kaštonų st.
Joniškės st.
J.Janonio st.
Sportininkų st.
Sportininkų st.
Stadiono st.
Lakštučių st.
Bijūnų st.
Bijūnų st.
Pietinės st.
Bangų st.
Bangų st.
Pasažo st.
Mogiliovo st.
Rimkų st.
Rimkų st.
Smiltelės st.
Smiltelės st.
Volungėlės st.
Volungėlės st.
I.Simonaitytės st.
I.Simonaitytės st.
Jūrininkų st.
Skardžio st.
Jūrininkų st.
Plytinės st.
Labrenciškės st.
Medienos st.
Lėbartų st.
Kapinių st.
Vyturio st.
Vyturio st.
Bandužių st.
Bandužių st.
Budelkiemio st.
Budelkiemio st.
Berželio st.
Berželio st.
Švepelių st.
Baseino st.
Baseino st.
Vienkiemio st.
Vienkiemio st.
Debreceno st.
Mogiliovo st.
Naujojo sodo st.
Savivaldybės st.
Vilniaus st.
Autobusų stotis
Kopų st.
Šlaito st.
Šlaito st.
Minijos st.
Kino studijos st.
Kurėno st.
Kapinių st.
Liepų st.
Molo st.
Molo st.
Markučių st.
Rambyno st.
Rambyno st.
Skibalės st.
Švepelių st.
Trinyčių st.
Trinyčių st.
Statybininkų st.
Vingio st.
Vingio st.
Miško st.
Miško st.
LCC tarptautinis universitetas
Geležinkelio stoties st.
Priestočio st.
Priestočio st.
Pasažo st.
Giruliai
Kurėno st.
Aula Magna st.
Kapitonų st.
Kapitonų st.
Škunų st.
Škunų st.
Senosios Smiltelės st.
Senoji Panevėžio st.
Kristijono Donelaičio st.
Kristijono Donelaičio st.
Šiaurės st.
Prospekto st.
Prospekto st.
Šilutės st.
Studentų st.
Onkologijos departamento st.
Debreceno st.
Kino studijos st.
Kuncų st.
Laistų sodų st.
Laistų sodų st.
Dragūnų st.
Dragūnų st.
Autobusų stotis
Lypkių st.
Pramonės st.
Verslo st.
Pramonės st.
Metalo st.
Verslo st.
Metalo st.
Vasaros estrados st.
Vasaros estrados st.
Girininkijos st.
Girininkijos st.
Butigeidžio bataliono st.
Butigeidžio bataliono st.
Baltijos žiedo st.
Ligoninės st.
Žiedo st.
Naikupės st.
Šilutės st.
Girulių st.
Giruliai
Stadiono st.
Autobusų parko st.
Geležinkelio stoties st.
Turgaus st.
Šilutės st.
Šilutės st.
Jūrininkų st.
Jūrininkų st.
Vakarų st.
Senosios Smiltelės st.
Ermitažas; Promo
LEZo st.
Šlapžemės st.
Kraštinės st.
Kraštinės st.
Šlapžemės st.
Lypkių st.
Aukštkiemių st.
Peskojų st.
Karklės st.
Jaunystės st.
Ąžuolyno st.
Ąžuolyno st.
Dainavos st.
Turistų st.
Senamiesčio st.
Senamiesčio st.
Purmalių st.
Pakrantės st.
Apynių st.
Gedminų st.
Žuvėdros st.
Žuvėdros st.
Kukuliškių st.
Kukuliškių st.
Olandų kepurės st.
Olandų kepurės st.
Jaunimo st.
Pajūrio regioninio parko lankytojų centro st.
Polimerų st.
Gėlių st.
Lelijų st.
Sniegenų st.
Linų st.
Rasa
Plikių st.
Radailių st.
Radailių st.
Šimkų st.
Pajūrio regioninio parko lankytojų centro st.
Gedminų st.
Gindulių st.
Gindulių st.
Slengių st.
Slengių st.
Trušelių st.
Trušelių st.
Baukštininkų st.
Baukštininkų st.
Žemgrindžių st.
and 657 more (see the full list on the map or in the GeoJSON)

Over time

Overall score across the last 4 checks — up 2.8 since 2026-07-31.

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-07-25	70.5	first check
2026-07-30	69.5	down 1.0
2026-07-31	69.5	no change
2026-08-01	72.3	up 2.8

What changed since your last check

Correctness up 6.5
Freshness no change
Rider experience no change

What changed in this feed

Grade improved from D to C since 2026-07-31.

The feed file was re-published since 2026-07-31.

Changed counts

down Some trip headsigns name a stop along the way, not the final destination. (74 → 2) (trip_headsign_matches_intermediate_stop)

No longer reported since 2026-07-31 (1 finding)

Some service calendars in the feed have already ended. (expired_calendar)

This records the later feed state. It does not establish who made a change or why.

Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.

What changed over time

On 2026-07-25 this feed started at grade C. On 2026-07-30 the grade moved from C to D. On 2026-08-01 the grade moved from D to C. On 2026-08-01 the check no longer reported: some service calendars in the feed have already ended. As of 2026-08-01 it holds grade C.

A plain-language history of this feed, newest first.

2026-08-01 Grade went D to C, correctness rose 6 points.
2026-07-30 Grade went C to D.

Everything we checked

10 findings, ordered by severity.

Show every finding

Warning6903 instances
6903 of 6903 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)
Warning907 instances
907 of 907 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)
Warning4 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)
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.)
Finding code: 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.)
Finding code: 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.)
Finding code: 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.)
Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info8 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)
Info2 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).
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.)
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

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 356 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 356 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 90 / 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.

[![Klaipėda city public transport GTFS data quality grade: C](https://gtfsscorecard.org/data/artifacts/klaipeda-city-public-transport/badge.svg)](https://gtfsscorecard.org/agency/klaipeda-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/klaipeda-city-public-transport/2026-08-01.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-08-01. 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). Klaipėda city public transport GTFS feed-quality record, dated 2026-08-01 (grade C (72.3/100), rubric v1.3, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 77aca6bb49c1…). https://gtfsscorecard.org/data/artifacts/klaipeda-city-public-transport/2026-08-01.json

@misc{gtfsscorecard-klaipeda-city-public-transport-2026-08-01,
  title        = {Klaipėda city public transport GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/klaipeda-city-public-transport/2026-08-01.json}},
  note         = {Checked 2026-08-01; rubric v1.3; gtfs-validator 8.0.1; reader archive profile raw-v1; grade C (72.3/100)}
}

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