Feed status · checked 2026-09-05
Ужгородська міська рада (Uzhhorod city transport)
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Zakarpatska oblast, Ukraine.
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.
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
Review the rule documentation for 'missing_required_field' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Missing required field (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 points in its category
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
217 of 217 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
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
- Missing required field (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'missing_required_field' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- 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
- 217 of 217 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
- 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.
Review the rule documentation for 'missing_required_field' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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_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.
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. 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 1060 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 17.8% 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 7 kinds of issue across 33 instances (3 error, 25 warning, 5 informational).
Service data covers the next 1060 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.
2 accessibility depth signals
18 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (11Б, 156, 24, 18, 22, and more).
Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.
2 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("в/м 555 (175)", "в/м 555 (174)").
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 217 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.
- 11Б (blue)
- 156 (white)
- 24 (brown)
- 18 (brown)
- 22 (brown)
- 20 (white)
- 38 (brown)
- 58 (brown)
- 26 (brown)
- 2 (brown)
- 14 (brown)
- 10 (brown)
- 7 (brown)
- 7Д (brown)
- 8 (brown)
- 09 (brown)
- 17 (brown)
| Route | Type | Line color |
|---|---|---|
| 11Б вул. Василя Гаджеги - площа Корятовича | Bus | blue |
| 156 вул. В. Чорновола - цвинтар Барвінок | Bus | white |
| 24 Університет - Дравці | Bus | brown |
| 18 Університет - ТЦ Епіцентр | Bus | brown |
| 22 вул. В. Чорновола - пл. Корятовича | Bus | brown |
| 20 вул. Технічна - Речовий ринок | Bus | white |
| 38 Університет - В. Чорновола | Bus | brown |
| 58 Залізничний вокзал - УжНУ | Bus | brown |
| 26 в/м 555 - мкр-н Горяни - УжНУ | Bus | brown |
| 2 пл. Шандора Петефі - мкр-н Горяни - в/м 555 | Bus | brown |
| 11А вул. Володимирська - пл. Корятовича ч/з вул. Загорську | Bus | brown (no shape in feed) |
| 14 пл. Корятовича - вул. В'ячелава Чорновола | Bus | brown |
| 10 мкр-н Горяни - Епіцентр ч/з речовий ринок | Bus | brown |
| 7 вул. Михайла Грушевського - вул. Івана Котляревського | Bus | brown |
| 7Д вул. Михайла Грушевського - Дачний масив | Bus | brown |
| 8 вул. В'ячеслава Чорновола - УжНУ | Bus | brown |
| 09 вул. Івана Котляревського - Речовий ринок ч/з залізничний вокзал | Bus | brown |
| 17 УжНУ - вул. Івана Котляревського | Bus | brown |
List every stop
- Барвінок (128)
- Технічна (96)
- Школа №9 (85)
- Закарпатська (77)
- Грушевського (42)
- Туристичний факультет (59)
- Туристичний факультет (60)
- Дравці (76)
- Парк ПІдзамковий (90)
- Прогрес (87)
- Стадіон Авангард (107
- Гуртожиток №1 (108)
- проспект Свободи (122)
- Рубін (110)
- Залізнична лікарня (111)
- Ігоря Сікорського (112)
- Дік (113)
- Велмарт (114)
- Чорновола (115)
- Чорновола (116)
- Велмарт (117)
- Дарина (118)
- Богомольця (119)
- Ігоря Сікорського (120)
- Залізнична лікарня (121)
- Електрон (123)
- Гуртожиток №1 (124)
- Яна Гуса (125)
- площа Князя Лаборця (126)
- Ліцей (127)
- Лісна (130)
- Барвінок (131)
- Беркут (134)
- Беркут (135)
- Автоуправління (136)
- АТП (137)
- Радіоцентр (138)
- Зіна (139)
- Білочка (140)
- Білочка (141)
- Площа Захисників України (142)
- Поштова (143)
- Залізничний вокзал (143)
- Залізничний вокзал (144)
- Автовокзал (145)
- Автовокзал (146)
- Площа Кирила і Мефодія (147)
- Площа Кирила і Мефодія (148)
- Прогрес (149)
- Електрон (150)
- готель "Ужгород" (151)
- Івана Франка (155)
- Антоніна Дворжака (163)
- Гранітна (164)
- Данила Галицького (165)
- Дендеші 1 (166)
- Дендеші (167)
- Дендеші 2 (168)
- Дендеші 2 (169)
- Горянська ЗОШ (170)
- Горяни центр (171)
- Радгосп (172)
- Радгосп (173)
- в/м 555 (174)
- в/м 555 (175)
- Школа №4 (176)
- Корятовича (177)
- ФМК (178)
- Володимирська (179)
- Володимирська (180)
- Епіцентр 2 (181)
- Епіцентр 2 (182)
- Гербера (183)
- Універмаг "Україна" (184)
- ТЦ "Токіо" (185)
- ТЦ "Токіо" (186)
- Пролісок (187)
- Торгово-промислова палата (188)
- Готель "Закарпаття" (189)
- Площа Кирила і Мефодія (190)
- Кінцева Епіцентр (191)
- Кінцева Епіцентр (192)
- Блеста (193)
- Горяни центр (194)
- Блеста (195)
- Тубдиспансер (196)
- Тубдиспансер (197)
- Онкодиспансер (198)
- Кардіодиспансер (199)
- Шахтарів (200)
- Шахтарів (201)
- Сергія Параджанова (202)
- Сергія Параджанова (203)
- Івана Котляревського (203)
- Івана Котляревського (204)
- Площа Корятовича (205)
- Дитяча поліклініка (206)
- Марії Занковецької (207)
- ЖК "Park Land" (208)
- Ужанська долина (209)
- Коледж Культури (210)
- Райенерго (211)
- Коньячний завод (212)
- Коньячний завод (213)
- Дачний масив "Шахта" (214)
- Дачний масив "Шахта" (215)
- Карпати (216)
- Боздош -1 (217)
- Боздоський парк (218)
- Боздош - 2 (219)
- Василя Гаджеги (220)
- Академіка Шпеника (221)
- Волонтерів (222)
- Андрія Палая (223)
- Академіка Шпеника (224)
- Корятовича (93)
- Капітанський мостик (80)
- Митна (98)
- Івана Чендея (83)
- площа Шандора Петефі (24)
- Анкудінова (55)
- Будителів (57)
- Переїзд (61)
- Військова частина (63)
- Механічний завод (65)
- Електродвигун (67)
- Браво (81)
- Речовий ринок (32)
- Речовий ринок (33)
- Браво (82)
- Електродвигун (65)
- Механічний завод (66)
- Військова частина (64)
- Переїзд (62)
- Ужанська (58)
- Руська (100)
- Дастор (78)
- Івана Чендея (84)
- Водоканал (79)
- Корятовича (45)
- Університет (1)
- Гуртожиток №4 (3)
- Міська лікарня (7)
- Міська поліклініка (9)
- Ера (11)
- Джин (13)
- Санепідемстанція (15)
- Жупанацька (91)
- Завод (055)
- Анкудінова (56)
- Автостанція №2 (88)
- Готель Ужгород (86)
- площа Кирила І Мефодія (52)
- Стоматологічна поліклініка (48)
- Коледж Культури (46)
- Героїв 128-ї Бригади (44)
- Каплиця (40)
- Школа №19 (38)
- Легоцького (36)
- ТЦ Епіцентр (34)
- ТЦ Епіцентр (33)
- Легоцького (35)
- Школа №19 (37)
- Грушевського (41)
- Героїв 128-ї Бригади (43)
- Коледж Культури (45)
- Стоматологічна поліклініка (47)
- Орхідея (50)
- Швабська (75)
- Каплиця (39)
- Корятовича (77)
- Жупанацька (92)
- Санепідемстанція (16)
- Джин (14)
- Ера (12)
- Міська поліклініка (10)
- Міська лікарня (8)
- Гуртожиток №4 (4)
- Університет (2)
- Парк Підзамковий (89)
- Технічна (97)
- Школа №17 (101)
- Тичини (105)
- Другетів (103)
- Школа №20 (95)
- Другетів (104)
- Тичини (106)
- Школа №17 (102)
- Школа №20 (94)
- Пенсійний фонд (17)
- Суд (21)
- Вишнева (23)
- Фруктова (25)
- Озерна (27)
- Нова лінія (29)
- ВАТ Модуль (31)
- Орхідея (49)
- Автовокзал (51)
- Карпатської України (73)
- Корчма Деца у Нотаря (69)
- Дравці-центр (71)
- Дравці, кінцева (144)
- Карпатської України (74)
- Дравці-центр (72)
- Корчма Деца у Нотаря (70)
- Автовокзал (53)
- Ринок (19)
- ВАТ Модуль (32)
- Нова лінія (30)
- Загорська (28)
- Фруктова (26)
- Вишнева (24)
- Суд (22)
- Ринок (20)
- Пенсійний фонд (18)
- Червениця (5)
- Червениця (6)
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
- Error3 instances
Missing required field (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_required_field' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: missing_required_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1954 instances
1954 of 2376 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)
- Warning217 instances
217 of 217 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)
- Warning18 instances
Some route colors don't contrast with their text color.
Route badges get hard to read, most of all for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Finding code: route_color_contrast · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 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)
- Warning2 instances
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.)
Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
On some trips the stops fall along the route line in a different order than the schedule lists.
Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.
Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)
Finding code: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · 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)
- Info5 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)
- 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
Two requirements remain for this feed to earn the conformance mark. 1 validator error to resolve. States wheelchair access on 0% of stops and 18% of trips; the mark needs 90% of each.
- Valid Not yet
- 1 validator error to resolve.
- Current Met
- Service data covers the next 1060 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 18% 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.
- 2 of 217 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 1060 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 3 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
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 66 / 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 100 / 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 40 / 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/uzhhorod-city-transport/2026-09-05.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-05. 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.