Feed status · checked 2026-09-07
Kretinga public transport
Based on the official feed source on file
Service mode Bus
unchanged since 2026-09-06
Catalogued in Kretinga, Lithuania.
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 72 minutes ago; last changed 31 hours ago.
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
272 of 272 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
322 of 322 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
- 272 of 272 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
- 322 of 322 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. 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 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. 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 1941 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 6 kinds of issue across 1119 instances (0 error, 1082 warning, 37 informational).
Service data covers the next 1941 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
2 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Kalotės st.", "Kalotės 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.
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 272 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.
- P (green)
- 80 (green)
- 82 (green)
- 41 (green)
- 40 (green)
- 20 (green)
- 42 (green)
- 23 (green)
- 45 (green)
- 22 (green)
- 47 (green)
- 46 (green)
- 27 (green)
- Ž1J (green)
- Ž2 (green)
- Ž1 (green)
- Ž3 (green)
- 50 (green)
- 72 (green)
- 93 (green)
- 74 (green)
- 73 (green)
- 75 (green)
- 34 (green)
- 11 (green)
- 14 (green)
- 40D (green)
- 94 (green)
- 61 (green)
- 60 (green)
| Route | Type | Line color |
|---|---|---|
| P Rotušės aikštė - Kretingos autobusų stotis | Bus | green |
| 80 Kretinga - Laukžemė - Naujoji Įpiltis | Bus | green |
| 82 Laukžemė - Naujoji Įpiltis | Bus | green |
| 41 Kretinga - Juodupėnai | Bus | green |
| 40 Kretinga - Kartena - Salantai | Bus | green |
| 20 Kretinga (AP) - Budriai | Bus | green |
| 42 Kretinga - Salantai | Bus | green |
| 23 Kretinga - Baubliai | Bus | green |
| 45 Salantai - Juodupėnai | Bus | green |
| 22 Budriai - Nausodis - Baubliai - Kretinga | Bus | green |
| 47 Salantai - Gargždelė | Bus | green |
| 46 Salantai - Tuzai | Bus | green |
| 27 Kretinga - Baubliai - Žutautai - Budriai | Bus | green |
| Ž1J Autobusų parkas - J. Jablonskio g. - Briedžio g. | Bus | green |
| Ž2 Autobusų parkas - Briedžio g. | Bus | green |
| Ž1 Autobusų parkas - Briedžio g. | Bus | green |
| Ž3 Autobusų parkas - S. Daukanto mokykla | Bus | green |
| 50 Kretinga (AP) - Klaipėda | Bus | green |
| 72 Kretinga - Šukė - Grūšlaukė - Plokščiai | Bus | green |
| 93 Kretinga (AP) - Rūdaičiai - Atostogų parkas | Bus | green |
| 74 Grūšlaukė - Plokščiai | Bus | green |
| 73 Kretinga - Grūšlaukė - Plokščiai | Bus | green |
| 75 Kretinga - Darbėnai - Kumpikai - Grūšlaukė | Bus | green |
| 34 Kretinga - Balsiškiai - Kalniškiai - Kartena | Bus | green |
| 11 Kretinga - Jokūbavas | Bus | green |
| 14 Kretinga - Petrikaičių kapinės - Jokūbavas | Bus | green |
| 40D Kretinga - Salantai | Bus | green |
| 94 Kretinga - Genčai | Bus | green |
| 61 Kretinga (AP) - Palanga | Bus | green |
| 60 Kretinga (AP) - Pryšmančiai - Palanga | Bus | green |
List every stop
- Laiviai
- Kalniškiai
- Kalnalis
- Voveraičiai
- Medšarkė
- Kurmaičiai c. III
- Mančiai
- Nasrėnai
- Akmena
- Basanavičiaus g.
- Sūdėnai
- Laukžemė
- Kęstučio g.
- Barzdžiai
- Kurmaičiai
- Sodai
- Kūlupėnai II
- Benaičiai II
- Šukė
- Salantų kr.
- Naujoji Įpiltis
- Kupšiai
- Padvariai
- Gaudučiai
- Latveliai
- Barzdžiai
- Asteikiai
- Šatilgalis
- Petrikaičiai
- Melioratorių g.
- Šatilgalis
- Laiviai
- Sūdėnai
- Tūbausiai
- Kūlupėnai
- Asteikiai
- Kašučiai
- Kurmaičiai c. II
- Darbėnai
- Kašučių g.
- Kūlupėnai II
- Gintarai
- Ankštakiai
- Kalnalis
- Senkai
- Kašučių g.
- Jokūbavas
- Benaičiai I
- Akmenaliai
- Benaičiai I
- Užpelkiai
- Žalgiris
- Raguviškiai
- Budriai
- Daubėnai
- Mišučiai
- Šventosios g.
- Kretingos autobusų stotis II
- Kryžkelė
- Dupulčiai
- Mokykla
- Daubėnai
- Salantų kr.
- Senkai
- Lubiai
- Kupšiai
- Pasertupis
- Palangos autobusų stotis
- Klaipėdos autobusų stotis
- Kretingos autobusų stotis III
- Salantai
- Kretingos autobusų stotis IV
- Autobusų parkas II
- Rotušės aikštė
- Vytauto g.
- Pranciškonų gimnazija
- Balandžių g.
- Balandžių g.
- Vytauto g.
- Kretingos grūdai
- Dienos veiklos centras
- S. Daukanto mokykla
- Laidojimo namai "Rimtis"
- Žvėrininkystės ūkis
- Geštautai
- Geštautai
- Erlėnai
- Technologijos ir verslo mokykla
- Tūbausiai II
- Tūbausiai III
- Genčai
- Šukės centras
- Kumpikų centras
- Plokščiai
- Kiaupiškė
- Medamiškė
- Budrių centras
- Durpynas
- Kryžkelė I
- Technologijos ir verslo mokykla
- Briedžio g. I
- Kalno g.
- Kalotės st.
- Kalotės st.
- Balsiškiai
- Rotušės aikštė
- Norfa
- Kretingalė
- Kretingalė
- M. Daujoto mokykla
- Kopūstai
- Kalnuvėnai
- Nemuno g.
- Stančiai
- Šventosios g.
- Nemuno g.
- Bajorai
- Malūno g.
- Šlikiai
- Briedžio g.
- Briedžio g.
- Šlikiai
- Malūno g.
- Bajorai
- Kalnuvėnai
- Kopūstai
- Stančiai
- Taikos g.
- Taikos g.
- Rubiniškė
- Medelynas
- Prūdgaliai
- Šlaveitai
- Knėžai
- Knėžai
- Sodai
- Tuzai
- Akmena
- Žemaitės al.
- Žvėrininkystės ūkis
- Autobusų parkas I
- Laidojimo namai "Rimtis"
- Jablonskio g.
- Jablonskio g.
- Veislininkystės stotis
- Budriai
- Kryžkelė I
- Kretingsodis
- Petrikaičių kapinės
- Tuopa
- Gaisrinė
- "Autoratas"
- S.Daukanto mokykla
- Pasieniečių g.
- Balsiškiai
- Jablonskio g.
- Jablonskio
- Mišučiai
- Minijos tiltas
- Kalniškiai
- Lubiai
- Leliūnai
- Erlėnai
- Plokščiai
- Mančiai
- Pryšmančiai
- Durpynas
- Kašučiai
- Šukė
- Akmenaliai
- Rubiniškė
- Kumpikų centras
- Vaineikiai
- Tūbausiai III
- Tūbausiai II
- Mokykla Tūb.
- Mokykla Tūb.
- Kurmaičiai c. III
- Kurmaičiai c. II
- Kryžkelė
- Kryžkelė
- Medamiškė
- Laukžemė
- Kiaupiškė
- Rūdaičiai II
- Gaisrinė
- Kretingos grūdai
- Atostogų parkas
- Gargždelė
- Kretingsodis
- M. Daujoto mokykla
- Aukštkalviai
- Ankštakiai
- Padvariai
- Užpelkiai
- Klibiai
- Klibiai
- Latveliai
- Voveraičiai
- Baubliai
- Minijos tiltas
- Vaineikiai
- Žalgiris
- Kryžkelė
- Senoji Įpiltis
- Medšarkė
- Dupulčiai
- Veislininkystės stotis
- Tuzai
- Medelynas
- Rūdaičiai I
- Petreikiai
- Laumaliai
- Medelyno raštinė
- AB "Akmena"
- Mokykla
- Šlaveitai
- Rūdaičiai II
- Prūdgaliai
- SB "Ąžuolas"
- Vandens bokštas
- Gaudučiai
- Leliūnai
- Veterinarija
- Ligoninė
- AB "Akmena"
- Technologijos ir verslo mokykla
- SB "Ąžuolas"
- Kretingos autobusų stotis I
- SB "Rubuliai"
- Rubuliai
- Kartena
- Ligoninė
- SB "Rubuliai"
- Žadeikiai
- Vydmantai
- Grūšlaukė
- Rūdaičiai I
- Žemaitės al.
- Aukštkalviai
- Slučkai
- SB "Minija"
- Kveciai
- Technologijos ir verslo mokykla
- Kveciai
- Rubuliai
- Žadeikiai
- Gintarai
- Vandens bokštas
- Slučkai
- and 22 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-09-06.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-06 | 60.7 | first check |
| 2026-08-07 | 60.7 | no change |
| 2026-09-06 | 70.4 | up 9.7 |
| 2026-09-07 | 70.4 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-09-06.
Same feed file as 2026-09-06; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.
What changed over time
On 2026-08-06 this feed started at grade D. On 2026-09-06 the grade moved from D to C. On 2026-09-06 the check no longer reported: equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator); some route lines list the same point twice in a row; some rider-facing names are in ALL CAPS or all lowercase; 270 of 270 trips lack rider-facing destination or direction text. As of 2026-09-07 it holds grade C.
A plain-language history of this feed, newest first.
- 2026-09-06 Grade went D to C, rider experience rose 15 points.
Everything we checked
11 findings, ordered by severity.
Show every finding
- Warning1081 instances
Some internal IDs use characters outside the basic text set.
These IDs are valid UTF-8 data. This warning is only about support in older apps. It does not mean that names in other languages are wrong.
Fix: Only change the flagged IDs if an app needs basic ASCII values. Update each place that uses the ID. Keep all names and headsigns in their original language. (A planned ID change, not a quick text cleanup.)
Finding code: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning322 instances
322 of 322 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)
- Warning272 instances
272 of 272 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)
- 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)
- Info19 instances
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.)
Finding code: service_extends_far_in_the_future · See MobilityData GTFS Validator rules (opens the validator rules 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)
- Info3 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).
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 1941 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 1941 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 86 / 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.
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/kretinga-public-transport/2026-09-07.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-07. 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.