Център за градска мобилност (Sofia Urban Mobility Center)

What changed since the last check

• Correctness no change
• Freshness no change
• Rider experience no change
• Realtime quality down 2.4

Top three things to fix

1. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

   4449 of 4449 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.

   Effort: A column in stops.txt; your scheduling software likely has it.

2. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.

   33138 of 33138 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.

   Effort: A default or per-trip field in your export.

3. Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').

   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.

   Effort: Often a bulk fix in your scheduling software.

Key facts

Feed URL

https://gtfs.sofiatraffic.bg/api/v1/static

Last checked

2026-07-19

Service window

365 days of service data remain. Last service date 2027-07-19.

Feed version

1.0

Location

Sofia (stolitsa), Bulgaria