← All sources
DailyLive-testedCommunity mirror

Mobility / Public-transport schedules and network reference

Tbilisi Transport Company processed GTFS schedule

Transitous republishes a processed GTFS Schedule snapshot for Tbilisi containing full-size bus, minibus, both metro lines and three gondola/ropeway services. It includes stops, route metadata, dated service calendars, trips, ordered stop times, and English/Georgian translations. This is schedule and network-reference data, not live movement. The processed feed deliberately omits shapes.txt because the source configuration sets drop-shapes=true.

01

Provenance and access

How the data is reached

Unauthenticated GTFS ZIP over HTTPS. The tested processed file contained seven UTF-8 CSV tables. Transitous requests visible source attribution and recommends direct GTFS downloads instead of repeated journey-API calls.

Reuse status

No license information is declared for the underlying TTC feed; Transitous processing does not create an open-data license

02

Field-level detail

What is actually returned

livereferencederivedhistoricalunknown

agency.txt

One feed publisher/operator record.

8 fields
Field / pathTypeNull?ExampleMeaningFreshness
agency_idstringNoTTCAgency identifierreference
agency_namestringNoTbilisi Transport CompanyAgency display namereference
agency_urlURL stringNohttps://ttc.com.geAgency websitereference
agency_timezoneIANA timezoneNoAsia/TbilisiTimezone used by schedule timesreference
agency_langlanguage codeNokaPrimary feed languagereference
agency_phonestringNo032 293 44 44Public agency telephonereference
agency_fare_urlURL stringNohttps://ttc.com.ge/en/tariffsFare-information pagereference
agency_emailstringNoinfo@metro.gePublic agency emailreference

stops.txt

Transit stops and stations across bus, minibus, metro and gondola modes.

5 fields
Field / pathTypeNull?ExampleMeaningFreshness
stop_namestringNo#102-ე საჯარო სკოლაStop or station display nameBase feed is primarily Georgianreference
stop_codestringYes3280Public-facing stop code29 blanks, corresponding to non-bus stopsreference
stop_idstringNo1:3280Feed-unique stop identifierreference
stop_latdecimal degreesNo41.733616WGS84 latitudereference
stop_londecimal degreesNo44.724983WGS84 longitudereference

routes.txt

Bus, minibus, metro and aerial-lift route records.

6 fields
Field / pathTypeNull?ExampleMeaningFreshness
route_long_namestringNo9 ძმის ქ. -ცაიშის ქ. - სადგურის მოედანიRoute endpoints or descriptionreference
route_short_namestringNo368Rider-facing route numberreference
agency_idstringNoTTCForeign key to agency.txtreference
route_typeinteger enumNo3GTFS transport modeObserved: 1 subway, 3 bus/minibus, 6 aerial liftreference
route_idstringNo1:minibusR2518Feed-unique route identifierID prefix distinguishes bus from minibusreference
route_colorRGB hex stringNo0033B4Suggested route display color without #reference

calendar.txt

Recurring weekday service patterns and the current short schedule horizon.

4 fields
Field / pathTypeNull?ExampleMeaningFreshness
monday…sundayseven 0/1 integer columnsNo1Whether the service runs on each weekdayreference
start_dateYYYYMMDD stringNo20260721First date the recurring service rule appliesreference
end_dateYYYYMMDD stringNo20260818Last date the recurring service rule appliesreference
service_idstringNoMONDAY-FRIDAYService-pattern key used by tripsreference

trips.txt

One directional scheduled trip on a route and service pattern.

5 fields
Field / pathTypeNull?ExampleMeaningFreshness
route_idstringNo1:Gondola_Gondola_1Route foreign keyreference
service_idstringNoMONDAY-SUNDAYCalendar foreign keyreference
trip_headsignstringNoნარიყალაTrip direction or destinationreference
direction_id0/1 integerNo1Direction within the routereference
trip_idstringNo1:Gondola_Gondola_1-1:01-0-0Scheduled-trip identifierreference

stop_times.txt

Scheduled times at each ordered stop of each trip.

5 fields
Field / pathTypeNull?ExampleMeaningFreshness
trip_idstringNo1:Metro_Metro_1-0:01-0-0Trip foreign keyreference
arrival_timeGTFS time stringNo06:00:00Scheduled arrival timeGTFS times can exceed 24:00reference
departure_timeGTFS time stringNo06:00:00Scheduled departure timereference
stop_idstringNo1:metro_1_1Stop foreign keyreference
stop_sequenceintegerNo0Stop order within tripStarts at zero in this feedreference

translations.txt

English and Georgian translations for routes, stops and trip headsigns.

6 fields
Field / pathTypeNull?ExampleMeaningFreshness
table_namestringNoroutesGTFS table being translatedreference
field_namestringNoroute_long_nameField being translatedreference
languagelanguage codeNoenTranslation languageObserved en and kareference
translationstringNoRike - NarikalaTranslated textreference
record_idstringYes1:Gondola_Gondola_1Record-ID selectorMay be blank under GTFS field-value selection rulesreference
field_valuestringYesAlternate field-value selectorreference
03

Representative evidence

Sample records

Three transport modes from routes.txt

Retrieved 2026-07-22 13:38 Asia/Tbilisi

CSV
route_long_name,route_short_name,agency_id,route_type,route_id,route_color
მ/ს ახმეტელი - მ/ს ვარკეთილი,1,TTC,1,1:Metro_Metro_1,FF505B
ავშნის III შეს. - მ/ს "ახმეტელის თეატრი",508,TTC,3,1:minibusR2518,0033B4
რიყე - ნარიყალა,1,TTC,6,1:Gondola_Gondola_1,F5861F
04

Boundaries

Reliability, caveats, and privacy

What held up

  • HTTP metadata and every CSV table were inspected on 2026-07-22
  • Counts and route-type distributions were calculated from the downloaded ZIP
  • Use calendar.txt and HTTP headers rather than relying only on catalog metadata

What can go wrong

  • Processed community mirror, not an official TTC open-data publication
  • No shapes.txt or calendar_dates.txt in the validated processed snapshot
  • Underlying TTC data license is unclear
  • Static times do not prove that a vehicle is operating or on time
  • The 28-day calendar horizon requires regular refresh

Privacy boundary

  • Contains public network and schedule data, not passenger or fare-validation records
05

Cross-source possibilities

Ideas using this source