← All agencies

Feed status · checked 2026-07-24

Panevėžys city public transport

Based on the feed this agency publishes

Service mode Bus

FDCBA

69.6 / 100

First scorecard for this agency

Catalogued in Panevėžio 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.

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

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

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

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 (Panevėžys city public transport) scored D (69.6 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: 254 of 254 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: 1753 of 1753 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/panevezys-city-public-transport/

Score by category

Correctness83.8 / 100

The MobilityData validator flagged 6 kinds of issue across 325 instances (0 error, 8 warning, 317 informational).

Freshness85.0 / 100

Service data covers the next 342 days.

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

N2 (black)
10A (teal)
15 (teal)
14 (teal)
16 (teal)
11 (teal)
10 (teal)
13 (teal)
12 (teal)
4 (teal)
3 (teal)
6A (teal)
3A (teal)
1 (teal)
8 (teal)
7 (teal)
6 (teal)
5 (teal)
N1 (black)
9 (teal)
1E (teal)

Routes in Panevėžys city public transport's feed
Route	Type	Line color
N2 Pažalvaičių g. - Autobusų parkas	Bus	black
10A Savitiškio g. - Paliūniškio g.	Bus	teal
15 Dariaus ir Girėno g. - Piniava	Bus	teal
14 Vakarinė g. - Tinklų g.	Bus	teal
16 Pažagieniai - Molainių g.	Bus	teal
11 Velžio kelias - Techninės apžiūros centras	Bus	teal
10 Savitiškio g. - Tinklų g.	Bus	teal
13 Velžio kelias - Savitiškio g.	Bus	teal
12 Kniaudiškių g. - Pažalvaičių g.	Bus	teal
4 Molainiai - Vaivadai	Bus	teal
3 Aguonų g. - Projektuotojų g. - Savitiškio g.	Bus	teal
6A Dembava - J. Janonio g.	Bus	teal
3A Aguonų g. - Klaipėdos g.	Bus	teal
1 Rožių g. - Kniaudiškių g. - Vakarinė g.	Bus	teal
8 Taikos alėja - Rožių g.	Bus	teal
7 Velžio kelias - Tiekimo g.	Bus	teal
6 Pajuostis - J. Janonio g.	Bus	teal
5 Parko g. - Venslaviškiai	Bus	teal
N1 UAB "Devold" - Velžio kelias	Bus	black
9 Jonažolių g. - Geležinkelio stotis	Bus	teal
1E Kniaudiškių g. - A. Jakšto g.	Bus	teal

This feed has 254 stops.

List every stop

Aeroklubas
Parko g.
Dariaus ir Girėno g.
Konsultacijų poliklinika
Jonažolių g.
Stetiškių g.
Stetiškių g.
Aeroklubas
Panevėžio LEZ
Panevėžio LEZ
Bernatonių g.
Bernatonių g.
Pažalvaičių g.
Pažalvaičių g.
Švyturio g.
Pažagieniai
Rėklių g.
Rėklių g.
Amerikos g.
Amerikos g.
Šiaurinė g.
Pušyno g.
Techninės apžiūros centras
Gamtos mokykla
Prekybos centras "Rožynas''
Veteranų g.
Piniava
V. Alanto g.
HARJU ELEKTER UAB
J. Jablonskio g.
J. Jablonskio g.
Savivaldybė
Savivaldybė
S. Daukanto g.
Naujamiesčio g.
A. Vienuolio g.
Nemuno g.
F. Vaitkaus g.
Statybininkų g.
Plukiai
Plukiai
Dariaus ir Girėno g.
Statybininkų g.
F. Vaitkaus g.
Ukmergės g.
Ukmergės g.
Ligoninė
Ligoninė
Šermukšnių g.
Šermukšnių g.
AB "Linas"
AB "Linas"
Varpo g.
Beržų g.
"Tulpė"
"Tulpė"
5-oji gimnazija
J. Tilvyčio g.
J. Zikaro g.
Poliklinika
Tulpių g.
''Kalnapilio'' arena
Taikos alėja
Taikos alėja
UAB "Atra"
Tiltas
Tiltas
AB "Lietkabelis"
AB "Lietkabelis"
Pramonės g.
Pramonės g.
"Aurida"
"Aurida"
AB "Panevėžio stiklas" Pramonės g.
Pušaloto g.
Pušaloto g.
Įmonių g.
Įmonių g.
Poliklinika
J. Zikaro g.
J. Tilvyčio g.
J. Miltinio mokykla
Autobusų parkas
Autobusų parkas
Beržų g.
AB "Panevėžio stiklas" Pramonės g.
Projektuotojų g.
Prekybos centras "Iki"
Žvaigždžių g.
Prekybos centras "Iki"
Projektuotojų g.
Prekybos bazė
Kapinės
Kapinės
Ramygalos g.
Autobusų parkas
Algirdo g.
Liepų alėja
Liepų alėja
Marijonų g.
Nevėžio g.
Darželis "Žibutė"
Raginėnų g.
J. Janonio g.
Raginėnų g.
Darželis "Žibutė"
Algirdo g.
Autobusų parkas
Klaipėdos g.
Prekybos centras "Maxima"
Pelkių g.
Alyvų g.
F. Vaitkaus g.
Prekybos centras "Maxima"
Varpo g.
Pilėnų g.
Staniūnų g.
AB "Panevėžio duona"
Įmonių g.
AB "Panevėžio stiklas" Pušaloto g.
Tiekimo g.
Gilėnai
Tiekimo g.
AB "Panevėžio stiklas" Pušaloto g.
Geležinkelio stotis
Kniaudiškių g.
Tinklų g. galinė
Techninės apžiūros centras
Taikos alėja
Švyturio g.
Kauno g.
Kauno g.
Savitiškio g.
Geležinkelio stotis
Įmonių g.
Teatro g.
"Vyturio" progimnazija
Gražinos g.
"Sodra"
Anykščių g.
Stoties g.
Katedros g.
Staniūnų g.
Vandentiekis
Vandentiekis
Elektros g.
J. Balčikonio gimnazija
Stoties g.
UAB "Panevėžio ketus"
UAB "Panevėžio ketus"
AB "Panevėžio pienas"
AB "Mažeikių nafta"
Prekybos centras "Maxima"
Navadolio g.
Projektuotojų g.
Aguonų skg.
Smėlynės g.
Smėlynės g.
Smėlynės g.
"Rožyno" mokykla
Rožių g.
A. Baranausko g.
A. Baranausko g.
E. Liutkevičiaus g.
E. Liutkevičiaus g.
J. Miltinio gimnazija
J. Miltinio gimnazija
S. Kerbedžio g.
S. Kerbedžio g.
Senamiesčio g.
J. Tilvyčio g.
Aguonų g.
Miško g.
Miško g.
Aguonų skg.
Varpo g.
Amerikos g.
Amerikos g.
"Rožyno" mokykla
Aukštaičių g.
Aukštaičių g.
Vilniaus g.
J. Biliūno g.
Velžio kelias
Medžiotojų g.
Kniaudiškių g.
Kosmonautų g.
Kosmonautų g.
Parkas
Parkas
Elektronikos g.
Nevėžio užtvanka
Tinklų g.
Pajuostis
Meteorologijos stotis
Meteorologijos stotis
Dembava
Medelynas
Dembava
Medelynas
Projektuotojų g.
"Šaltinio" mokykla
"Šaltinio" mokykla
Sodai
Sodai
V. Alanto g.
Topolių alėja
A. Smetonos g.
Venslaviškiai
Paupio
Paupio
AB "Panevėžio pienas"
Nevėžio užtvanka
Molainių g.
Dariaus ir Girėno g.
Raginėnų g.
Raginėnų g.
Geležinkelio stotis
Vaivadai
Centras "RYO" Vakarinė g.
Paliūniškio g.
Vaivadai
Elektronikos g.
"Sodra"
Turgus
Smėlynės g.
Smėlynės g.
J. Elisono g.
J. Elisono g.
Įstra
Įstra
Kolektyviniai sodai
Kolektyviniai sodai
Piniava
Centras "RYO" Klaipėdos g.
Elektros tinklai
Ateities g.
Ateities g.
Garažai
Garažai
Dembava
Kėdainių g.
Paliūniškio g.
Molainiai
Medžiotojų g.
Pagojo g.
K. Naruševičiaus g.
UAB "Devold"
Vaivadėlių g.
Katedros g.
and 4 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

Warning1753 instances
1753 of 1753 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the bus itself can take them.
Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Warning254 instances
254 of 254 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)
Warning6 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)
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
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no bus 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
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)
Info303 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.)
Validator rule: trip_headsign_matches_intermediate_stop · 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.)
Validator rule: unknown_column · Read the fix guide · 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.

1 of 254 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 84 / 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 37 / 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.

[![Panevėžys city public transport GTFS data quality grade: D](https://gtfsscorecard.org/data/artifacts/panevezys-city-public-transport/badge.svg)](https://gtfsscorecard.org/agency/panevezys-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/panevezys-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). Panevėžys city public transport GTFS feed-quality record, dated 2026-07-24 (grade D (69.6/100), rubric v1.2, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 b47703eb859b…). https://gtfsscorecard.org/data/artifacts/panevezys-city-public-transport/2026-07-24.json

@misc{gtfsscorecard-panevezys-city-public-transport-2026-07-24,
  title        = {Panevėžys city public transport GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/panevezys-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 (69.6/100)}
}

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