← All agencies

Feed status · checked 2026-09-05

Јавни градски превоз Ниш

Based on the official feed source on file

Service mode Bus

56.6 / 100

First scorecard for this agency

Catalogued in Nišavski okrug, Serbia.

Covers 117 daysAccessibility gapsRealtime not yet published

The Niš city network, published by the City of Niš and run under contract by Niš-ekspres, Lasta a.d. Beograd and Strela-Obrenovac. Counted as one feed record for the city network, not as three 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.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

Fix 01

Review the rule documentation for 'stop_time_timepoint_without_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

Stop time timepoint without times (flagged by the MobilityData validator). See the linked rule for what this affects.

⏱ Varies.worth about +24 points in its category

Fix 02

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

337 of 337 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 03

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

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

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
Stop time timepoint without times (flagged by the MobilityData validator).
Next action
Review the rule documentation for 'stop_time_timepoint_without_times' 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
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.

  1. Review the rule documentation for 'stop_time_timepoint_without_times' 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.

  2. 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.

  3. 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.

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 117 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
Fare information is published using GTFS Fares v1.
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

Correctness30.0 / 100

The MobilityData validator flagged 12 kinds of issue across 17900 instances (2070 error, 15663 warning, 167 informational).

Freshness100.0 / 100

Service data covers the next 117 days.

Rider experience59.0 / 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 published.

Accessibility0 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

FaresLegacy fares

Fares are applied to trips.

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 337 stops.

Skip to route and stop data

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 (green)
  • 10 (green)
  • 11 (green)
  • 11A (green)
  • 12 (green)
  • 13 (green)
  • 2 (green)
  • 3 (green)
  • 34A (green)
  • 34B (green)
  • 36 (green)
  • 4 (green)
  • 5 (green)
  • 6 (green)
  • 7 (green)
  • 8 (green)
  • 9 (green)
Routes in Јавни градски превоз Ниш's feed
RouteTypeLine color
1 Minovo naselje I - Niška BanjaBusgreen
10 Naselje "9. maj" - Ćele kulaBusgreen
11 Medoševac - DuvaništeBusgreen
11A Trg Pavla Stojkovića - MedoševacBusgreen
12 Njegoševa - Donji komrenBusgreen
13 Trg Kralja Aleksandra - Bulevar Nemanjića - Delijski VisBusgreen
2 Bubanj - Donja VrežinaBusgreen
3 Brzi Brod - Naselje "Ratko Jović"Busgreen
34A Aerodrom-Autobuska stanica-Železnička stanica-AerodromBusgreen
34B Aerodrom-Železnička stanica-Autobuska stanica-AerodromBusgreen
36 Trg Kralja Aleksandra - MramorBusgreen
4 Čalije - BubanjBusgreen
5 Železnička stanica - SomborskaBusgreen
6 Železnička stanica - Duvanište - SkopskaBusgreen
7 Sarajevska - Kalač brdoBusgreen
8 Novo groblje - Gabrovačka rekaBusgreen
9 Mokranjčeva - Branko BjegovićBusgreen
List every stop
  • Trg kralja Aleksandra
  • Trg kralja Milana
  • Gabrovačka reka
  • Lozni kalem
  • Lozni kalem - ka centru
  • Niš-ekspres
  • Niš-ekspres
  • Krive livade
  • Krive livade
  • Zona I
  • Trg Svetog Save
  • Zona II
  • Zona II
  • OŠ Ćele Kula
  • OŠ Ćele Kula
  • Trošarina
  • Trošarina
  • Stonoteniski dom
  • Stonoteniski dom
  • Đerdapska
  • Đerdapska
  • Branka Miljkovića
  • Branka Miljkovića
  • TC Roda
  • Branka Krsmanovića
  • Romanijska
  • Pijaca Duvanište
  • Pijaca Duvanište
  • Magdon
  • Magdon
  • Tržni centri
  • Tržni centri
  • Most Medijana
  • Most Medijana
  • DUVANIŠTE
  • DUVANIŠTE
  • OŠ Dušan Radović
  • OŠ Dušan Radović
  • Ekonomska škola
  • Ekonomska škola
  • Agrogradnja
  • Elektronska industrija
  • Elektronska industrija
  • Brzi Brod I
  • Marger
  • Brzi Brod I
  • Brzi Brod II
  • Brzi Brod II
  • Naselje Nikola Tesla
  • Naselje Nikola Tesla
  • 6 borova
  • 6 borova
  • Banjska rampa
  • Banjska rampa
  • NIŠKA BANJA
  • Marger
  • NIŠKA BANJA
  • BRZI BROD
  • Mokranjčeva
  • Mokranjčeva
  • Žitopek
  • Žitopek
  • Ledena Stena
  • Ledena Stena
  • Ledena Stena brdo
  • Ledena Stena brdo
  • Obilićev venac-rampa
  • Veterinarski zavod
  • Veterinarski zavod
  • Metro
  • Metro
  • Naselje Milka Protić
  • Naselje Milka Protić
  • KP Dom
  • KP Dom
  • KP Dom - kružni tok
  • KP Dom - kružni tok
  • Feroks
  • Naselje "9. maj" podvožnjak
  • Naselje "9. maj" podvožnjak
  • Naselje "9. maj" MK
  • Naselje "9. maj" pošta
  • NASELJE "9. MAJ" okretnica
  • Naselje "9. maj" OŠ
  • Naselje "9. maj" OŠ
  • Vulkan
  • Vulkan
  • MRAMOR
  • Pirotska rampa
  • Papir servis - ka centru
  • Papir servis - od centra
  • Medoševac okretnica
  • Spomenik Bubanj
  • Spomenik Bubanj
  • Jurija Gagarina
  • Jurija Gagarina
  • MK Pasi Poljana
  • Šumadijska - od centra
  • MK Pasi Poljana
  • Lužičkih srba
  • Lužičkih srba
  • Gligorija Đaka
  • Gligorija Đaka
  • NOVO GROBLJE
  • Pasi Poljana raskrsnica
  • Svetislava Trgojevića
  • Svetislava Trgojevića
  • Kalač brdo
  • Trg Pavla Stojkovića
  • Šumadijska - ka centru
  • Kragujevačka
  • Logor - od centra
  • Logor - ka centru
  • DIN - od centra
  • DIN - ka centru
  • Tempo - od centra
  • Tempo - ka centru
  • MIN Kopeks - od centra
  • MIN Kopeks - ka centru
  • Ratka Jovića - od centra
  • Autobuska stanica
  • Ratka Jovića - ka centru
  • NASELJE Ratko Jović - od centra
  • NASELJE Ratko Jović - ka centru
  • Vazduhoplovaca - od centra
  • Vazduhoplovaca - ka centru
  • Salon nameštaja
  • VELPRO (raskrsnica)
  • AERODROM
  • Strugara
  • Strugara
  • Autobuska stanica
  • Prijepoljska
  • Prijepoljska
  • MK Branko Bjegović
  • MK Branko Bjegović
  • 22. decembra
  • 22. decembra
  • Dobrovoljačka
  • Tehnički fakulteti
  • Tehnički fakulteti
  • Restoran Indeks
  • Učiteljski dom
  • Restoran Indeks
  • Naselje Stevan Sinđelić
  • Naselje Stevan Sinđelić
  • DIN I
  • DIN I
  • Mariborska I
  • Mariborska I
  • Mariborska II
  • Mariborska II
  • Ul. Mladosti
  • Ul Mladosti
  • MK Donji Komren
  • MK Donji Komren
  • Hram Svetog Ilije
  • Hram Svetog Ilije
  • DONJI KOMREN
  • Nišauto
  • Kasarna Knez Mihajlo
  • Jagodin Mala
  • Jagodin Mala
  • Dom Vojske Srbije
  • Niteks
  • Niteks
  • OŠ Njegoš
  • OŠ Njegoš
  • Radoja Domanovića
  • Bojnička
  • RK Sinđelić
  • RK Sinđelić
  • Dom D. Radović
  • Dom D. Radović
  • Crveni soliter
  • Pijaca Durlan
  • Pijaca Durlan
  • Durlan
  • Durlan
  • Benzinska stanica
  • Benzinska stanica
  • Radomira Antića
  • Radomira Antića
  • DONJA VREŽINA
  • DONJA VREŽINA
  • Most Mladosti
  • Naselje Beverli Hils
  • Zorana R. Čupe
  • OŠ Miroslav Antić
  • Matejevački put
  • Matejevački put
  • Ul. Borova
  • Ul. Borova
  • ČALIJE
  • Proleterska
  • Proleterska
  • Vojvode Mišića
  • MK B. Mišić Kamenko
  • MK B. Mišić Kamenko
  • Sveti Pantelejmon
  • Sveti Pantelejmon
  • Vase Pelagića
  • Vase Pelagića
  • Studenička
  • Studenička
  • Čedomira Krstića
  • Čedomira Krstića
  • Vojvode Mišića
  • G. Bolnica - Zetska
  • Agrogradnja
  • Ledena Stena - trafo
  • Ledena Stena - trafo
  • Jura
  • Jura
  • Bubanjskih heroja
  • Jermenska
  • Dimitrija Leka
  • MINOVO NASELJE I
  • Trg Pavla Stojkovića
  • Crveni pevac
  • Stojana Andrića
  • Dobrovoljačka
  • PODVINIK II
  • SOMBORSKA - Despota Đurđa
  • SOMBORSKA - Despota Đurđa
  • Lipovačka
  • Lipovačka
  • Sarajevska - ložionica
  • Sarajevska - ložionica
  • Vulkanizer
  • Trg Patrijarha Pavla
  • Vulkanizer
  • DONJA VREŽINA 1
  • Francuska
  • Francuska
  • Svrljiškog part. odreda
  • Svrljiškog part. odreda
  • DELISJKI VIS
  • DELISJKI VIS
  • ĆELE KULA 1
  • Episkopska
  • Ćele Kula 1
  • Heroja Pop Miće
  • Heroja Pop Miće
  • Vidovdanska
  • Vidovdanska
  • Salvadora Dalija
  • Salvadora Dalija
  • SKOPSKA
  • Vojvode Gojka
  • and 87 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

15 findings, ordered by severity.

Show every finding
  • Error2070 instances

    Stop time timepoint without times (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'stop_time_timepoint_without_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: stop_time_timepoint_without_times · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning15489 instances

    Some internal IDs use characters outside the basic text set.

    These IDs are valid UTF-8 data. This warning is only about support in older apps. It does not mean that names in other languages are wrong.

    Fix: Only change the flagged IDs if an app needs basic ASCII values. Update each place that uses the ID. Keep all names and headsigns in their original language. (A planned ID change, not a quick text cleanup.)

    Finding code: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning6055 instances

    6055 of 6055 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)

  • Warning337 instances

    337 of 337 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)

  • Warning131 instances

    Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'equal_shape_distance_diff_coordinates_distance_below_threshold' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning26 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)

  • Warning7 instances

    Some stops sit far from the route line they belong to.

    Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.

    Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)

    Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning4 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 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)

  • 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)

  • Warning2 instances

    The feed contains route shapes no trip uses.

    Harmless to riders, but it bloats the feed and suggests stale export data.

    Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)

    Finding code: unused_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Info163 instances

    Some trip headsigns name a stop along the way, not the final destination.

    The sign should tell riders where the bus ends up, so a midpoint name can send them the wrong way.

    Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)

    Finding code: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Info23 instances

    About 23 stop names are written in ALL CAPS.

    Mixed-case names are easier to read in apps and are read more naturally by screen readers.

    Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)

    Finding code: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)

  • Info3 instances

    The feed has a stretch of two weeks or more with no service running.

    A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.

    Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)

    Finding code: big_gap_in_service · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Info1 instance

    Feed valid beyond total service window (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'feed_valid_beyond_total_service_window' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: feed_valid_beyond_total_service_window · 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 0% of trips; the mark needs 90% of each.

Valid Not yet
1 validator error to resolve.
Current Met
Service data covers the next 117 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 117 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 2070 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 30 / 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 59 / 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.

Јавни градски превоз Ниш GTFS data quality grade: F

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/jgp-nis/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.