API – vehicles

This is the documentation for version 2 of the API. Documentation for the deprecated version 1.

Information on the current locations of public transport vehicles. See also: GTFS.

  • Endpoint: GET https://rozklad.renegades.at/api/v2/vehicles?format=json|cbor
  • Data type: application/json (default) or application/cbor (when format=cbor)
  • Update frequency: approx. every 10 seconds

Data structure

{
  "data": [
    {
      "line": {
        "id": 14,
        "number": "53",
        "type": "DAY",
        "subtype": "NORMAL"
      },
      "vehicle": {
        "id": 3,
        "type": "BUS",
        "number": "1050",
        "model": "Solaris Urbino 18",
        "low_floor": true,
        "ticket_machine": {
          "cards": true,
          "coins": false
        },
        "passenger_counter": true,
        "operator": "SPA Klonowica"
      },
      "trip": {
        "service": "053-01",
        "gtfs_id": "502693_POWS",
        "start_date": "2026-06-22",
        "scheduled_start_time": "2026-06-22T11:09:00.000000Z",
        "headsign": "Stocznia Szczecińska",
        "direction_id": 1,
        "route_variant_number": 12,
        "current_stop_sequence": 30
      },
      "previous_stop": {
        "number": "14121",
        "name": "Sczanieckiej"
      },
      "next_stop": {
        "number": "17012",
        "name": "Plac Matki Teresy"
      },
      "position": {
        "latitude": 53.43933868408203,
        "longitude": 14.565779685974121,
        "bearing": 90,
        "velocity": 0
      },
      "delay": {
        "seconds": 568,
        "minutes": 9
      },
      "occupancy_status": "MANY_SEATS_AVAILABLE",
      "stuck": false,
      "updated_at": "2026-06-22T12:03:28.000000Z"
    },

    ...

  ]
}
  • object line – object containing information about the line
    • int id – line identifier (immutable)
    • string number – line designation (number) (may change)
    • string type – line type:
      • DAY – day service
      • NIGHT – night service
    • string subtype – line subtype:
      • NORMAL – regular service
      • SEMI_FAST – semi-fast service
      • FAST – fast service
      • REPLACEMENT – replacement service
      • ADDITIONAL – additional service
      • SPECIAL – special service
      • TOURIST – tourist service
  • object vehicle – object containing information about the vehicle
    • int id – vehicle identifier
    • string type – vehicle type:
      • SKM – SKM train
      • TRAM – tram
      • BUS – bus
    • string number – fleet number of the vehicle
    • string|null model – vehicle model name
    • bool|null low_floortrue if the vehicle is low-floor
    • object|null ticket_machine – object containing information about the ticket machine installed in the vehicle (null if no ticket machine is installed in the vehicle)
      • bool cards – accepts payment by card
      • bool coins – accepts payment by coins
    • bool passenger_countertrue if the vehicle is equipped with passenger counting sensors
    • string|null operator – name of the operator owning the vehicle
  • object trip – object containing information about the trip currently being operated by the vehicle
    • string service – duty code (shift) operated by the vehicle
    • string|null gtfs_id – identifier of the trip currently being operated by the vehicle in the static GTFS timetable (null if the vehicle cannot be matched to a trip)
    • string start_date – start date serving as the reference point for the trip currently being operated by the vehicle
    • string scheduled_start_time – scheduled start time of the trip currently being operated by the vehicle
    • string headsign – direction name for the trip currently being operated by the vehicle
    • int direction_id – direction identifier (0 denotes the outbound direction, and 1 denotes the return direction)
    • int route_variant_number – route variant number of the line on which the vehicle is currently operating
    • int|null current_stop_sequence – sequence number of the current stop within the trip currently being operated by the vehicle (null if the vehicle cannot be matched to a trip)
  • object|null previous_stop – object containing information about the previous stop (null if there is no data about the previous stop)
    • string number – number of the previous stop
    • string name – name of the previous stop
  • object|null next_stop – object containing information about the next stop (null if there is no data about the next stop)
    • string number – number of the next stop
    • string name – name of the next stop
  • object position – object containing information about the vehicle’s location
    • float latitude – geographic coordinates of the vehicle (latitude)
    • float longitude – geographic coordinates of the vehicle (longitude)
    • int|null bearing – value in the range from 0 to 360 indicating the vehicle’s geographic direction of travel (bearing), where 0 or 360 means north, 90 means east, etc., in 45° increments
    • int velocity – current speed of the vehicle in km/h
  • object delay – object containing information about the vehicle’s delay
    • int seconds – vehicle delay in seconds (0 = on time, a value greater than 0 = delayed, and a value less than 0 = early)
    • int minutes – vehicle delay rounded to full minutes (0 = on time, a value greater than 0 = delayed, and a value less than 0 = early)
  • string occupancy_status – current occupancy level of the vehicle:
    • MANY_SEATS_AVAILABLE – very low occupancy
    • FEW_SEATS_AVAILABLE – low occupancy
    • STANDING_ROOM_ONLY – medium occupancy
    • CRUSHED_STANDING_ROOM_ONLY – high occupancy
    • NO_DATA_AVAILABLE – no occupancy data available
  • bool stucktrue if the vehicle is not moving (stuck); possible reasons include, among others, traffic congestion or a vehicle breakdown
  • string updated_at – timestamp of the last data update

General information

  1. The data are provided free of charge under the CC0 1.0 licence, for use in any context, with no prior notification required.
  2. Zarząd Dróg i Transportu Miejskiego w Szczecinie (Roads and Public Transport Authority in Szczecin) does not guarantee the accuracy or completeness of the data and accepts no liability for any loss or decisions made on the basis of this information.
  3. In any product using the data (application, website, publication, etc.), please cite the data source as Zarząd Dróg i Transportu Miejskiego w Szczecinie, or in abbreviated form, ZDiTM Szczecin; although not legally required, this is appreciated.
  4. Where possible, please include a link to this page or to the ZDiTM Szczecin homepage in any product using the data; this is also not a legal obligation.
  5. Clients should recognise and honour the HTTP headers Cache-Control and ETag.
  6. API requests are rate‑limited: 100 requests per minute per IP address across all endpoints. The X-RateLimit-Remaining header shows the number of remaining requests. Once the limit is reached, an HTTP 429 response is returned. The X-RateLimit-Reset header then contains a Unix timestamp for when the limit resets, and the Retry-After header shows the number of seconds until reset.
  7. If possible, please include in your User-Agent header information identifying the entity using the data (e.g. the name of your application, website, or its URL).
  8. In the event of excessive server load, ZDiTM Szczecin reserves the right to partially or fully block access to the API.

Migration from version 1

  1. Endpoint changed to: GET https://rozklad.renegades.at/api/v2/vehicles.
  2. The response structure has been reorganised with the introduction of the line, vehicle, trip, position and delay objects.
  3. Added fields: vehicle.passenger_counter, trip.gtfs_id, trip.start_date, trip.scheduled_start_time, trip.direction_id, trip.current_stop_sequence, previous_stop.number, next_stop.number, delay.seconds and occupancy_status.
  4. The previous_stop and next_stop fields have been converted into objects.
  5. The punctuality field has been replaced by the delay object (the sign convention has also changed).
  6. Values returned by line.type, line.subtype and vehicle.type use the UPPER_SNAKE_CASE convention.
  7. CBOR format (application/cbor) is additionally supported via the format=cbor parameter.