← All agencies

Feed status · checked 2026-08-01

Vilnius public transport (JUDU)

Based on the feed this agency publishes

Service mode Bus + Ferry + Trolleybus

FDCBA

70.1 / 100

up 0.1 since 2026-07-31 · C → C

Catalogued in Vilniaus miestas, Lithuania.

Covers 365 daysAccessibility gapsRealtime not yet published

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 65 minutes ago; last changed 65 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

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

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

Fix 03

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: 1535 of 1535 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: Vilnius public transport (JUDU)
Finding: scorecard_wheelchair_boarding_unknown
Feed evidence: 1535 of 1535 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/vilnius-public-transport-judu/?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.
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.
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 365 days.
Published accessibility data: Accessibility information is stated for 0% of stops and 84.6% 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.

Ungraded capability read

Ferry data profile

A ferry-specific view of what this GTFS feed publishes. Schedule measurements use ferry routes and trips only; fare and realtime facts are labelled as whole-feed. Unknown values are not treated as no.

Ferry service: 1 routes · 32 trips
Terminal structure: 7 ferry boarding locations; no parent-station hierarchy is published.
Terminal access: Not applicable: no ferry boarding location is linked to a parent station, so stop_access is not permitted here.
Published accessibility: Unknown: none of the 7 ferry boarding locations publish wheelchair_boarding. Unknown: none of the 32 ferry trips publish wheelchair_accessible. This reports published values, not verified physical usability.
Bicycles: 100% of ferry trips publish a value; 100% of all ferry trips explicitly say allowed (32 of 32). Unstated values remain unknown.
Cars: Unknown: none of the 32 ferry trips publish cars_allowed.
Fares: Whole feed: no applied fare data is published. This is not evidence that ferry service is free.
Realtime: Whole feed: no GTFS-Realtime endpoints are configured in this scorecard.

Descriptive only. This profile does not change the grade or verify vessels, terminal facilities, vehicle carriage, fares, or accessibility in the real world. Field meanings follow the GTFS Schedule reference.

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 (Vilnius public transport (JUDU)) scored C (70.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: 1535 of 1535 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. 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/

3. 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.
   What: The feed contains no fare information.
   Finding code: scorecard_no_fare_data
   Guide: https://gtfsscorecard.org/fix/scorecard_no_fare_data/

Full scorecard: https://gtfsscorecard.org/agency/vilnius-public-transport-judu/

Score by category

Correctness75.8 / 100

The MobilityData validator flagged 7 kinds of issue across 5370 instances (0 error, 39 warning, 5331 informational).

Freshness85.0 / 100

Service data covers the next 365 days.

Rider experience50.2 / 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.

Accessibility31.7 / 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 1535 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.

1 (teal)
10 (teal)
11 (teal)
114 (teal)
115 (teal)
116 (teal)
117 (teal)
118 (teal)
119 (teal)
12 (teal)
120 (teal)
121 (teal)
122 (teal)
123 (teal)
125 (teal)
13 (teal)
14 (teal)
15 (teal)
16 (teal)
17 (teal)
18 (teal)
19 (teal)
2 (teal)
20 (teal)
21 (teal)
22 (teal)
24 (teal)
25 (teal)
26 (teal)
27 (teal)
28 (teal)
29 (teal)
3 (teal)
30 (teal)
31 (teal)
32 (teal)
33 (teal)
34 (teal)
35 (teal)
36 (teal)
37 (teal)
38 (teal)
39 (teal)
4 (teal)
40 (teal)
41 (teal)
42 (teal)
43 (teal)
46 (teal)
48 (teal)
49 (teal)
5 (teal)
50 (teal)
51 (teal)
52 (teal)
53 (teal)
54 (teal)
55 (teal)
56 (teal)
57 (teal)
58 (teal)
59 (teal)
61 (teal)
62 (teal)
63 (teal)
65 (teal)
66 (teal)
67 (teal)
68 (teal)
69 (teal)
7 (teal)
73 (teal)
74 (teal)
75 (teal)
76 (teal)
78 (teal)
8 (teal)
82 (teal)
87 (teal)
88 (teal)
89 (teal)
9 (teal)
1G (green)
2G (green)
3G (green)
3G-A (green)
3GA (green)
4G (green)
5G (green)
6G (green)
L1 (teal)
N1 (black)
N2 (black)
N3 (black)
N4 (black)
N5 (black)
N6 (black)
N7 (black)
N8 (black)
N9 (black)
1 (red)
10 (red)
12 (red)
15 (red)
16 (red)
17 (red)
18 (red)
19 (red)
2 (red)
20 (red)
21 (red)
3 (red)
4 (red)
6 (red)
7 (red)
9 (red)

Routes in Vilnius public transport (JUDU)'s feed
Route	Type	Line color
1 Stotis–Vikingų g.–Oro uostas–Rodūnios sodai	Bus	teal
10 Fabijoniškės–Baltupiai–Markučiai	Bus	teal
11 Žvėrynas–Senamiestis–Užupis	Bus	teal
114 Šiaurės miestelis–Antakalnis–Mileišiškių –S.Kerbedžio g.–Dvarčionys–Vinciūniškės	Bus	teal
115 Antakalnis–Rokantiškės–Parko–Linksmoji g.	Bus	teal
116 Žvėrynas–Gudelių šilas–Lazdynai–Ungurių g. (Apylanka)	Bus	teal
117 Pilaitė–Kriaučiūnai–Platiniškės	Bus	teal
118 Pilaitė–Varnės g.–Perkūnkiemis	Bus	teal
119 Šiaurės miestelis–Antakalnis–Rokantiškės–Egliškės	Bus	teal
12 Stotis–Rudamina–Skaidiškės	Bus	teal
120 Visoriai–Santariškės–Žaliųjų Ežerų g.–Kryžiokai	Bus	teal
121 Santariškės–Mažieji Gulbinai–Didžiųjų Gulbinų g.	Bus	teal
122 Naujininkai–Kalnėnai–Guriai–Pavilnys–Naujoji Vilnia (Apylanka)	Bus	teal
123 Žemieji Paneriai (Vaduvos g.) – Centras (Lukiškių g.)	Bus	teal
125 Gabijos progimnazija–Visorių g.–Bajorai– Visoriai	Bus	teal
13 Žemasis Pavilnys–Markučiai–Stotis–Vilkpėdė	Bus	teal
14 Rudamina–Didžiasalis–Grigaičiai–Parko–Arimų g.	Bus	teal
15 Žolyno g.–Antakalnis–Turniškės	Bus	teal
16 Stotis–Nemėžis–Skaidiškės	Bus	teal
17 Antakalnis–Nemenčinės pl.–Antaviliai	Bus	teal
18 Antakalnis–Dvarčionys–Parko g.	Bus	teal
19 Stotis–Lydos pl.–Salininkai	Bus	teal
2 Stotis–Liepkalnio–Vikingų g.–Oro uostas	Bus	teal
20 Žemieji Paneriai–Mūrinė Vokė–Lazdynai	Bus	teal
21 Lazdynėliai–Lazdynai–Centras	Bus	teal
22 Lazdynai–Oslo g.–Centras	Bus	teal
24 Fabijoniškės–Ukmergės g.–Žemieji Paneriai (Apylanka per P. Žadeikos g.)	Bus	teal
25 Žemieji Paneriai–Kazbėjų–V. A. Graičiūno g.–Vaidotai	Bus	teal
26 Ozo g.–Kalvarijų g.–Santariškės–Didžioji Riešė–Didieji Gulbinai	Bus	teal
27 Kalvarijų–Tuskulėnų–Olandų–Arimų g.	Bus	teal
28 Žemieji Paneriai–Grigiškės–Valai	Bus	teal
29 Vilkpėdė–Žemaitės g.–Lazdynai–Grigiškės	Bus	teal
3 Stotis–Eišiškių pl.–Dilgynė–Salininkai–Vaidotai	Bus	teal
30 Pilaitė–Konstitucijos pr.–Apkasų g.–Šiaurės miestelis	Bus	teal
31 Stotis–Pavilnys–Naujoji Vilnia (Apylanka)	Bus	teal
32 Žvėrynas–Zujūnai–Gineitiškės–Perkūnkiemis	Bus	teal
33 Šiaurės miestelis–Rinktinės–Olandų g.–Sukilėlių g.–Guriai	Bus	teal
34 Stotis–Olandų g.–Baltupiai–Jeruzalės g.–Visoriai	Bus	teal
35 Žalgirio–Kalvarijų g.–Naujieji Verkiai–Ožkiniai	Bus	teal
36 Žalgirio–Kalvarijų g.–Balsiai–Naujaneriai–Pagubė	Bus	teal
37 Kalvarijų–Tuskulėnų–Olandų g.–Rokantiškės	Bus	teal
38 Antakalnis–Dvarčionys–Šilėnų g.	Bus	teal
39 Antakalnis–Nemenčinės pl.–Balžio g.	Bus	teal
4 Stotis–Rodūnios kelias–Kirtimai	Bus	teal
40 Perkūnkiemis–Fabijoniškės–S.Stanevičiaus g.–Centras (Apylanka)	Bus	teal
41 Stotis–Eišiškių pl.–Užusienis	Bus	teal
42 Stotis–Eišiškių pl.–Salininkai	Bus	teal
43 Justiniškės–Šeškinė–Žaliasis tiltas–Centras (Apylanka Rygos g.)	Bus	teal
46 Perkūnkiemis–Laisvės pr.–A.Goštauto g.–Centras	Bus	teal
48 Šeškinė–Pašilaičiai–Santariškės	Bus	teal
49 Bajorai–Ateities g.–Didlaukio g.–Žalgirio g.–Lazdynai–Bukčiai	Bus	teal
5 Fabijoniškės–Žalgirio g.–Tuskulėnų g.–Šiaurės miestelis	Bus	teal
50 Antakalnis–Didlaukio g.–Baltupio g.–Bajorai	Bus	teal
51 Žemieji Paneriai–Trakų Vokė–Pagiriai	Bus	teal
52 Tarandė–Ukmergės g.–Pašilaičiai	Bus	teal
53 Fabijoniškės–Kalvarijų–Pylimo g.–Stotis	Bus	teal
54 Pilaitė–Lazdynai–Stotis	Bus	teal
55 Šiltnamių g.–Laisvės pr.–Fabijoniškės–Santariškės	Bus	teal
56 Fabijoniškės–Šeškinė–Konstitucijos pr.–A.Goštauto g.–Vilkpėdė (Apylanka)	Bus	teal
57 Fabijoniškės–Ateities g.–Jeruzalė–Bajorai–Bukiškis	Bus	teal
58 Stotis–Dzūkų g.–Minsko pl.–Kalnėnai–Guriai–Grigaičiai	Bus	teal
59 Grigiškės–Lazdynai–Laisvės pr.–Žvėrynas	Bus	teal
61 Stotis–Nemėžis–Kuprioniškės	Bus	teal
62 Žemieji Paneriai–Mūrinė Vokė– Gureliai–Lazdynai	Bus	teal
63 Žvėrynas–Pilaitės pr.–Karveliškės	Bus	teal
65 Ožkiniai–Naujieji Verkiai–Balsių g.–Pagubė	Bus	teal
66 Žalgirio–Kalvarijų–Žaliųjų Ežerų g.–Skirgiškės	Bus	teal
67 Parko–Pramonės g.–Mickūnai	Bus	teal
68 Lazdynai–Mūrinė Vokė–Lentvaris–Grigiškės	Bus	teal
69 Šiaurės miestelis–Kernavės g.–Lazdynai–Lazdynėliai	Bus	teal
7 Šiaurės miestelis–Verkių g.–Viršuliškės–Lazdynai	Bus	teal
73 Justiniškės–Centras–Naugarduko g.–Vilkpėdė (Apylanka Rygos g.)	Bus	teal
74 Stotis–Subačiaus–Parko g.	Bus	teal
75 Santariškės–Visorių g.–Fabijoniškės–Šeškinė–Justiniškės–Pilaitė	Bus	teal
76 Ateities–Balsių g.–Sakališkės–Bireliai	Bus	teal
78 Stotis–Eišiškių pl.–Pagiriai	Bus	teal
8 Žemieji Paneriai–Aukštieji Paneriai–Vaidotai	Bus	teal
82 Stotis–Salininkai–Miškiniai–Juodšiliai	Bus	teal
87 Ateities g.–Molėtų pl.–Riešė–Bendorėliai–Šeškinė	Bus	teal
88 Oro uostas–Centras–Europos aikštė	Bus	teal
89 Nepriklausomybės aikštė–Senamiestis–Drujos g.–Stotis	Bus	teal
9 Zuikių–Agrastų g.–Baltoji Vokė–Vaidotai	Bus	teal
1G Stotis–Kalvarijų g.–Santariškės	Bus	green
2G Santariškės–Laisvės pr.–Stotis	Bus	green
3G Perkūnkiemis–Šeškinė–Centras–Oro uostas	Bus	green
3G-A Fabijoniškės–Žaliasis tiltas (Apylanka P. Žadeikos g.)	Bus	green
3GA Fabijoniškės–Žaliasis tiltas (Apylanka P. Žadeikos g.)	Bus	green
4G Pilaitė–Konstitucijos pr.–Saulėtekis	Bus	green
5G Perkūnkiemis–Ozo g.–Saulėtekis	Bus	green
6G Parko–Olandų g.–Žaliasis tiltas	Bus	green
L1 Žirmūnų paplūdimys–Žaliasis tiltas–Verslo trikampis	Ferry	teal
N1 Centras–Antakalnis–Saulėtekis	Bus	black
N2 Centras–Lazdynai–Karoliniškės–Pilaitė (Apylanka per st. MO muziejus)	Bus	black
N3 Centras–Žirmūnai–Baltupiai–Santariškės	Bus	black
N4 Centras–Kalvarijų–S. Stanevičiaus g.–Gabijos progimnazija	Bus	black
N5 Centras–Markučiai–Pavilnys–Naujoji Vilnia (Apylanka)	Bus	black
N6 Centras–Šeškinė–Pašilaičiai–Bajorų kalvos	Bus	black
N7 Centras–Žvėrynas–Justiniškės–Perkūnkiemis–Gabijos progimnazija	Bus	black
N8 Europos aikštė–Centras–Stotis–Naujininkai–Oro uostas	Bus	black
N9 Centras–Naujamiestis–Žemieji Paneriai–Grigiškės (Apylanka per st. MO muziejus)	Bus	black
1 Karoliniškės–Žvėrynas–Stotis	Trolleybus	red
10 Saulėtekis–Kalvarijų g.–Naujininkai	Trolleybus	red
12 Žirmūnai–Šeimyniškių–Tauro g.–Žemieji Paneriai (Apylanka be Reformatų st.)	Trolleybus	red
15 Stotis–Žemieji Paneriai–Titnago g.	Trolleybus	red
16 Pašilaičiai–Lazdynai–Stotis	Trolleybus	red
17 Žirmūnai–Naujininkai	Trolleybus	red
18 Perkūnkiemis–Justiniškės–Žemieji Paneriai–Titnago g.	Trolleybus	red
19 Pašilaičiai–Konstitucijos pr.–Antakalnis–Saulėtekis	Trolleybus	red
2 Saulėtekis–Žygimantų g.–Stotis	Trolleybus	red
20 Žirmūnai–Žygimantų–Pylimo g.–Stotis	Trolleybus	red
21 Antakalnis–Šilo tiltas–Žirmūnai	Trolleybus	red
3 Karoliniškės–Žvėrynas–Žirmūnai–Valakampiai	Trolleybus	red
4 Antakalnis–Centras–Žemieji Paneriai	Trolleybus	red
6 Žirmūnai–Kalvarijų–Tauro g.–Žemieji Paneriai (Apylanka be Reformatų st.)	Trolleybus	red
7 Perkūnkiemis–Justiniškės–Žvėrynas–Stotis	Trolleybus	red
9 Karoliniškės–Šeimyniškių g.–Žirmūnai	Trolleybus	red

List every stop

Televizijos bokštas
Titnago st.
Mažoji Riešė
Mažoji Riešė
Bendoriai
Bendoriai
Bendorėliai
Bendorėliai
Klevinė
Klevinė
Durpynas
Durpynas
Ežero st.
Ežero st.
Antakalnio žiedas
Vaikų ligoninė
Valai
Ungurių st.
Turniškės
Sidaronių st.
Sidaronių st.
Skirgiškės
Klonio st.
Klonio st.
Mikalojaus Katkaus st.
Tverečiaus st.
Vikingų slėnis
Gynėjų st.
Ukmergės st.
Ukmergės st.
Žilvičių st.
Žilvičių st.
Ramunių st.
Juodvarnių st.
Juodvarnių st.
Stanislovo Kerbedžio st.
Stanislovo Kerbedžio st.
Stepono Kairio st.
Stepono Kairio st.
Moliakalnio st.
Moliakalnio st.
Krakiškių sodai
Krakiškių sodai
Žaliojo Visalaukio st.
Žaliojo Visalaukio st.
Vilniaus Pergalė
Pylimėliai
Pylimėliai
Duburio st.
Tautų st.
Vaikų darželis
Vaikų kaimas
Vaivorykštės st.
Valkininkų st.
Vieversių st.
Vieversių st.
Visoriai
Vytauto st.
Zarasų st.
Naujoji Vilnia
Ožkinių žiedas
Fabijoniškių žiedas
Žolyno st.
Duburio st.
Autobusų parkas
Laimos st.
Laimos st.
Povilo Lukšio st.
Kalinas
Didieji Gulbinai
Kalinas
Liepų st.
Justiniškės
Atžalyno st.
Bajorai
Šaulio st.
Šaulio st.
Aušros st.
Mėtų st.
Mėtų st.
Aušros vartai
Perkūnkiemis
Perkūnkiemis
Pavilionys
Gureliai
Gureliai
Jono Švažo st.
Jono Švažo st.
Kaimynų st.
Kovo 11-osios st.
1-asis paplūdimys
Lizdeikos st.
Rato st.
Vaidilutės st.
2-asis paplūdimys
Bruknių st.
Svajonių st.
Grybautojų st.
Rytų st.
Gerovės st.
Karklėnų st.
Karklėnų st.
Žvirblių st.
Žvirblių st.
Gerovės st.
9-asis kilometras
9-asis kilometras
Slėnis
Slėnis
Naujosios Vilnios sankryža
2-asis Didžiasalis
Grigaičių žiedas
2-asis Didžiasalis
Naujosios Vilnios sankryža
1-asis Didžiasalis
1-asis Didžiasalis
Šumsko kryptis
Šumsko kryptis
Grigiškių poliklinika
Vokės sodai
Vokės sodai
Kauno Vokės st.
Kauno Vokės st.
Geležinio Vilko st.
Geležinio Vilko st.
Kairėnai
Kairėnai
Kairėnai
Mykolo Lietuvio st.
Viršilų st.
Vismaliukai
Miškadvaris
Inovacijų pramonės parkas
Meškonių st.
Meškonių st.
Nepriklausomybės aikštė
Stotis
Lazdynėliai
Petro Baublio st.
Petro Baublio st.
Santariškių žiedas
Degučių st.
Degučių st.
Jaunystės st.
Jaunystės st.
Daniliškės
Ąžuolyno st.
Ąžuolyno st.
Paukščių takas
Airių st.
Airių st.
Savičiūnų st.
Savičiūnų st.
Vytauto Andriaus Graičiūno st.
Medkirčių st.
Medkirčių st.
Vaidotų piliakalnis
Vaidotų piliakalnis
Vinco Pietario st.
Verslo trikampis
Verslo trikampis
Titnago st.
Žynių st.
Lentvario kryžkelė
Dobūklė
Dobūklė
Žynių st.
Mačiuliškių st.
Mačiuliškių st.
Garbės st.
Garbės st.
Lentvaris
Tautų st.
Vytauto Pociūno st.
Vytauto Pociūno st.
Žirnių st.
Žirnių st.
Liepynės kapinės
Gerviškių st.
Gerviškių st.
Gulbinėlių st.
Gulbinėlių st.
Raudonės st.
Raudonės st.
Mažieji Gulbinai
Mažieji Gulbinai
Pijų st.
Pijų st.
Imanuelio Kanto st.
Imanuelio Kanto st.
Paplūdimio st.
Paplūdimio st.
Pakrantės st.
Žvorūnos st.
Užpalių st.
Bubilo st.
Kryžiokų sodų st.
Padvarės st.
Padvarės st.
Didieji Gulbinai
Taurupės st.
Taurupės st.
Pakrantės st.
Trakėnų st.
Trakėnų st.
Gelūžės st.
Gelūžės st.
Obeliškių st.
Obeliškių st.
Vienkiemių st.
Vėluvos st.
Katiliškės
Vėluvos st.
Varnės st.
Varnės st.
Pergalės st.
Pergalės st.
Šilo tiltas
Vinco Grybo st.
Vinco Grybo st.
Saulės slėnis
Saulės slėnis
Mažieji Pupojai
Mažieji Pupojai
Šiaurės Sodai
Šiaurės Sodai
Centrinė st.
Centrinė st.
Šv.Jono Bosko gimnazija
Egliškės
Egliškės
Kernavės st.
Kernavės st.
Krokuvos st.
Oršos st.
Lentvaris
Krokuvos st.
Gileikių st.
Rotušė
Šnipiškės
Skapiškio st.
Panerių kalvyno st.
Panerių kalvyno st.
Skapiškio st.
Rudamina
Rudamina
Europos aikštė
Smalinės st.
Aitvarų st.
Smėlio st.
and 1285 more (see the full list on the map or in the GeoJSON)

Over time

Overall score across the last 2 checks — up 0.1 since 2026-07-31.

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-07-31	70.0	first check
2026-08-01	70.1	up 0.1

What changed since your last check

Correctness no change
Freshness no change
Rider experience up 0.2

What changed in this feed

Overall score rose 0.1 points since 2026-07-31.

The feed file was re-published since 2026-07-31 (+211 KB).

What changed inside the export

Service now runs through 2027-08-01 (was 2027-07-01).

Read from the feed file itself, compared with the previous export. A service change is normal; this is a heads-up so nothing disappears silently.

Changed counts

down Some service calendars in the feed have already ended. (13 → 12) (expired_calendar)
up Some rider-facing names are in ALL CAPS or all lowercase. (9 → 10) (mixed_case_recommended_field)
up Some trip headsigns name a stop along the way, not the final destination. (5246 → 5323) (trip_headsign_matches_intermediate_stop)

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

Everything we checked

12 findings, ordered by severity.

Show every finding

Warning3308 instances
3308 of 21479 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.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Warning1535 instances
1535 of 1535 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)
Warning16 instances
Unexpected enum value (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unexpected_enum_value' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: unexpected_enum_value · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning12 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning10 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)
Info5323 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.)
Finding code: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info6 instances
Platform without parent station (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'platform_without_parent_station' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: platform_without_parent_station · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info2 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 85% of trips; the mark needs 90% of each.

Valid Met: Passes validation with no errors.
Current Met: Service data covers the next 365 days.
Accessible Not yet: States wheelchair access on 0% of stops and 85% 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 365 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 76 / 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 50 / 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.

[![Vilnius public transport (JUDU) GTFS data quality grade: C](https://gtfsscorecard.org/data/artifacts/vilnius-public-transport-judu/badge.svg)](https://gtfsscorecard.org/agency/vilnius-public-transport-judu/)

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/vilnius-public-transport-judu/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). Vilnius public transport (JUDU) GTFS feed-quality record, dated 2026-08-01 (grade C (70.1/100), rubric v1.3, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 4bf2be646b7e…). https://gtfsscorecard.org/data/artifacts/vilnius-public-transport-judu/2026-08-01.json

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

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