Feed status · checked 2026-08-01
Plungė public transport
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Plungė, 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 71 minutes ago; last changed 19 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
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
303 of 303 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
417 of 417 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 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
- 303 of 303 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
- 417 of 417 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
- feed_info.txt is missing its start/end dates (the file itself is absent)
- Next action
- Add feed_info.txt with feed_start_date and feed_end_date to your export.
- 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 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 3439 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 5 kinds of issue across 2188 instances (0 error, 2156 warning, 32 informational).
Service data covers the next 3439 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
3 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("S/B „Babrungas“", "S/B „Babrungas“", "S/B „Vaivorykštė“").
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 303 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.
- 27 (green)
- 28A (green)
- 7A (green)
- 25 (green)
- 24A (green)
- 21B (green)
- 7D (green)
- 6 (green)
- 24C (green)
- 25A (green)
- 28B (green)
- 22B (green)
- 3 (green)
- 7B (green)
- 7 (green)
- 27A (green)
- 5 (green)
- 21A (green)
- 22 (green)
- 23 (green)
- 2 (green)
- 26 (green)
- 4 (green)
- 7C (green)
- 21 (green)
- 1 (green)
- 22A (green)
- 23A (green)
- 24B (green)
| Route | Type | Line color |
|---|---|---|
| 27 Plungė - Paukštakiai - Kantaučiai - Plungė | Bus | green |
| 28A Plungė - Pakerai - Purvaičiai - Medingėnai - Plungė | Bus | green |
| 7A Stotis - Baseinas - Truikiai | Bus | green |
| 25 Plungė - Alsėdžiai - Ž.Kalvarija - Plungė | Bus | green |
| 24A Plungė - Plateliai per Gintališkę | Bus | green |
| 21B Plungė - Stalgėnai - Plungė | Bus | green |
| 7D Baseinas - Stotis - Prūsaliai - Linelis - sodai - baseinas | Bus | green |
| 6 Ligoninė - Stotis - Sodai - Noriškės - Ligoninė | Bus | green |
| 24C Plungė - Plateliai - Gilaičiai - Gintališkė - Rūdaičiai - Plateliai - Plungė | Bus | green |
| 25A Plungė - Vilkai - Virkšai - Plateliai - Pučkoriai - Ž.Kalvarija - Šarnelė - Plungė | Bus | green |
| 28B Plungė - Glaudžiai - Žlibinai - Keturakiai - Plungė | Bus | green |
| 22B Plungė - Juodeikiai - Karklėnai - Stonaičiai - Plungė | Bus | green |
| 3 Stotis - Ligoninė - Noriškės Sodai | Bus | green |
| 7B Baseinas - Glaudžiai | Bus | green |
| 7 Stotis - Bendruomenės centrai - Stotis | Bus | green |
| 27A Plungė - Paukštakiai - Kantaučiai - Plungė | Bus | green |
| 5 Ligoninė - Lentpjūvės g. - Vingio g. - Stotis | Bus | green |
| 21A Plungė - Daugėdai - Rietavas - Plungė | Bus | green |
| 22 Plungė - Kuliai - Plungė | Bus | green |
| 23 Plungė - Šateikiai - Aleksandravas - Plungė | Bus | green |
| 2 Stotis - N. Kapinės - Glaudžiai | Bus | green |
| 26 Plungė - Alsėdžiai - Plungė | Bus | green |
| 4 Ligoninė - Prūsaliai - Linelis | Bus | green |
| 7C Baseinas - Varkaliai | Bus | green |
| 21 Plungė - Rietavas - Plungė | Bus | green |
| 1 Varkaliai - Stotis - Truikiai | Bus | green |
| 22A Plungė - Karklėnai - Juodeikiai - Mižuikiai - Kuliai - Plungė | Bus | green |
| 23A Plungė - Aleksandravas - Pakutuvėnai - Sėleniai - Šateikai - Plungė | Bus | green |
| 24B Plungė - Plateliai - Žvirblaičiai - Plungė | Bus | green |
List every stop
- „Linelis“
- A. Jucio progimnazija
- Kepurėnai II
- Kepurėnai II
- Keturakiai I
- Keturakiai I
- Keturakiai II
- Kryžkelė
- Kryžkelė
- Kučinsko g.
- Kučinsko g.
- Kuliai
- A. Vaišvilos g
- Lekemė
- Lekemė
- Lentpjūvės g. I
- Lentpjūvės g. II
- Liepgiriai
- Liepgiriai
- Liepkalnis
- Liepkalnis
- Ligoninė
- Aikštė
- Mardosai
- Mardosai
- Maxima X
- Maxima X
- Mažieji Mostaičiai
- Mažieji Mostaičiai
- Medingėnai
- Medsėdžiai
- Medsėdžiai
- Medsėdžiai
- Aikštė
- Medžsėdžiai
- Meno mokykla
- Meno mokykla
- Merkeliai
- Merkeliai
- Milašaičiai
- Milašaičiai
- Minijos tiltas
- Minijos tiltas
- Mižuikiai
- Aleksandravas
- Narvaišiai
- Narvaišiai
- Naujosios kapinės
- Naujosios kapinės
- Nausodis
- Nausodis
- Noriškės I
- Noriškės I
- Noriškės II
- Noriškės II
- Aleksandravas
- Nugariai
- Nugariai
- Oginskio rūmai
- Oginskio rūmai
- Paburgė
- Paburgė
- Paežerė
- Paežerė
- Pakerai
- Pakerai
- Alksnėnai
- Pakerai
- Pakerai
- Pakutuvėnai
- Paminijis
- Paminijis
- Papieviai
- Paplatelė
- Paplatelė
- Paprūdžio g.
- Paprūdžio g.
- Alksnėnai
- Paukštakiai
- Paukštynas
- Pauošniai
- Pauošniai
- Pauošniai
- Pauošniai
- Platakiai
- Platakiai
- Plateliai
- Plungės vandenys
- Alsėdžiai
- Plungės vandenys
- Pramogų c. „Porto“
- Prūsaliai
- Pučkoriai
- Pučkoriai
- Purvaičiai I
- Purvaičiai I
- Purvaičiai II
- Purvaičiai II
- Rietavo AS
- Antsieniai
- Rūdaičiai
- S/B „Babrungas“
- S/B „Babrungas“
- S/B „Vaivorykštė“
- Salantų g.
- Santakiai
- Santakiai
- „Lytagra“
- Antsieniai
- Šateikiai
- Savivaldybė
- Savivaldybė
- Sėleniai
- Senamiesčio mokykla
- Senamiesčio mokykla
- Senosios kapinės
- Senosios kapinės
- Šeško šaltinis
- Šeško šaltinis
- Autobusų parkas
- Sinagogų g.
- Sinagogų g.
- Skirpščiai
- Skirpščiai
- Skurvydai
- Skurvydai
- Smilgiai
- Smilgiai
- Sodai
- Stalgėnai
- Autobusų parkas
- Stalgėnai
- Staneliai
- Staneliai
- Staneliai
- Staneliai
- Stonaičiai
- Stonaičiai
- Stonaičiai
- Stonaičiai
- Stonaičiai
- Babrungėnai
- Stotis
- Stotis
- Stotis
- Tech. apž. centras
- Tech. apž. centras
- Truikiai I
- Truikiai I
- Truikiai II
- Truikiai II
- Turgus
- Babrungėnai
- Turgus
- Uogučiai
- Užlieknis
- Užlieknis
- Užpeliai
- Užpeliai
- Užpelkiai
- Užpelkiai
- Užupiai I
- Užupiai I
- Babrungėnai I
- Užupiai II
- Užupiai II
- V. Mačernio g.
- V. Mačernio g.
- Varkaliai
- Varkaliai
- Varkaliai
- Vičiūnai
- Vičiūnai
- Videikiai I
- Babrungėnai I
- Vydeikiai I
- Vydeikiai II
- Vydeikiai II
- Vidurinės kapinės
- Vidurinės kapinės
- Vieštovėnai I
- Vieštovėnai I
- Vieštovėnai II
- Babrungėnai II
- Vieštovėnai II
- Vilkai
- Vilkai
- Vilkai
- Vilkai
- Vingio g.
- Virkšai
- Virkšai
- Visvainiai
- Visvainiai
- Babrungėnai II
- Vitkai
- Vitkai
- Vydeikiai
- Vydeikiai
- Žemaičių Kalvarija
- Žemaitijos grūdai
- Žerniai
- Žerniai
- Žiedas
- Žiedas
- Babrungo g.
- Žlibinai
- Zobielai
- Zobielai
- Žvirblaičiai
- Žvirblaičiai
- Irkiniai
- „Lytagra“
- Babrungo g.
- Baseinas
- Baseinas
- Kalniškiai
- Kalniškiai
- Pabrėžos g.
- Pabrėžos g.
- Klevų
- Klevų
- Rasytės g.
- Atžalyno
- Beržoras
- Ryšininkų
- Sruoja
- Rotinėnai
- Padago
- Sodo
- Beržoras
- Beržoro girininkija
- Beržoro girininkija
- Bubėnai
- Bubėnai
- Budrikiai
- Budrikiai
- Dariaus ir Girėno g.
- „Ryto“ pagrindinė mokykla
- Dariaus ir Girėno g.
- Darželis
- Darželis
- Darželis „Rūtelė“
- Darželis „Rūtelė“
- Daugėdai
- Didvyčiai
- Didvyčiai
- Dovainiai I
- Dovainiai I
- „Ryto“ pagrindinė mokykla
- and 53 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 68.8 | first check |
| 2026-07-30 | 69.1 | up 0.3 |
| 2026-07-31 | 69.1 | no change |
| 2026-08-01 | 69.1 | 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-07-31.
The feed file was re-published since 2026-07-31.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
10 findings, ordered by severity.
Show every finding
- Warning2153 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.)
Finding code: equal_shape_distance_same_coordinates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning417 instances
417 of 417 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)
- Warning303 instances
303 of 303 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)
- Warning2 instances
Some scheduled trips move faster between stops than a bus can.
Usually a typo'd stop time; riders get arrival times no bus can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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)
- 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 3439 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 3439 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 82 / 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/plunge-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.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.