Skip to main content
Home Studio Cart

Attribution

Transit data sources

DotClock Cloud combines public transport feeds, map services and user-selected stops to show local departure information on the clock. Coverage depends on the feeds available in each city, region and transport network.

Live transit coverage

Current totals from the catalog used by DotClock Cloud.

Live database
293healthy data feeds
111.3kstops indexed
31.1mscheduled calls
17regional catalogs

Companies covered

Recognised operators present in the live stop catalog.

285 recognised

Cotral SpA

13,743 stops

Schedule valid 2026-07-27 to 2026-09-20

GTFS

TPLFVG

8,734 stops

Schedule valid 2026-05-03 to 2026-08-31

NeTEx

SETA-MOREPC

8,343 stops

Schedule valid 2026-07-27 to 2026-08-30

NeTEx

CCA-CN

8,334 stops

Schedule valid 2026-08-10 to 2026-09-13

NeTEx

Roma Mobilità

8,300 stops

GTFS

CCA-GTT

7,073 stops

Schedule valid 2026-08-25 to 2027-01-31

NeTEx

GTT Torino

7,073 stops

Schedule valid 2026-08-28 to 2027-01-31

GTFS

TPER-BO

6,398 stops

Schedule valid 2026-07-09 to 2027-01-02

NeTEx

AMTEXT

6,237 stops

Schedule valid 2025-10-06 to 2026-01-28

NeTEx

BUSITALIA

5,970 stops

Schedule valid 2026-08-24 to 2026-09-20

NeTEx

AIR

5,942 stops

Schedule valid 2026-08-01 to 2026-09-14

NeTEx

ATM (Azienda Trasporti Milanesi)

4,856 stops

Schedule valid 2026-01-01 to 2026-12-31

NeTEx

CCA-EXTRATO

4,646 stops

Schedule valid 2026-08-18 to 2026-12-31

NeTEx

Autoguidovie

4,227 stops

Schedule valid 2025-12-11 to 2026-12-11

NeTEx

CCA-VCO

3,965 stops

Schedule valid 2026-08-28 to 2026-09-27

NeTEx

ATMA

3,919 stops

NeTEx

TEP Parma

3,877 stops

GTFS

TEP-PR

3,877 stops

Schedule valid 2026-07-02 to 2026-09-14

NeTEx

EAV GOMMA

3,737 stops

Schedule valid 2026-08-27 to 2026-08-31

NeTEx

ARST

3,554 stops

Schedule valid 2026-01-01 to 2026-12-31

NeTEx

TRENITALIA

3,542 stops

Schedule valid 2024-12-15 to 2026-12-13

NeTEx

ATV

3,489 stops

Schedule valid 2026-08-24 to 2026-09-09

NeTEx

COSAT

3,135 stops

Schedule valid 2026-07-01 to 2026-09-15

NeTEx

26

3,111 stops

Schedule valid 2026-07-27 to 2026-12-31

NeTEx

21

3,056 stops

Schedule valid 2026-07-27 to 2026-12-31

NeTEx

28

3,043 stops

Schedule valid 2026-07-27 to 2026-12-31

NeTEx

29

2,985 stops

Schedule valid 2026-07-27 to 2026-12-31

NeTEx

START-RN

2,971 stops

Schedule valid 2026-08-24 to 2026-09-20

NeTEx

TPER-FE

2,953 stops

Schedule valid 2026-05-22 to 2026-12-25

NeTEx

AMT

2,923 stops

Schedule valid 2025-04-10 to 2025-06-15

NeTEx

ATC

2,910 stops

Schedule valid 2025-06-15 to 2025-09-13

NeTEx

TPLLINEA

2,904 stops

Schedule valid 2025-09-15 to 2025-12-31

NeTEx

221

2,816 stops

Schedule valid 2026-06-04 to 2026-06-10

NeTEx

ADRIABUS

2,772 stops

NeTEx

30

2,719 stops

Schedule valid 2026-07-27 to 2026-12-31

NeTEx

RT

2,685 stops

Schedule valid 2025-01-01 to 2025-06-08

NeTEx

Showing the 36 largest operators by indexed stops. Another 249 operator records are available in the live catalog.

Updated from the live catalog at 30 Aug 2026, 21:31 CET.

Main services

These are the concrete transit data sources used by the DotClock Cloud backend for current departure features.

Roma Mobilita publishes the static GTFS catalog used for Rome stops and routes, plus a GTFS Realtime trip-updates feed for live departures.

Data used: Stops, routes, trip headsigns, scheduled service and realtime trip updates for supported Rome stops.

Licence: Publisher terms for Roma Mobilita transit data

Comune di Milano GTFS

Milan, Italy

The City of Milan open-data portal publishes a GTFS timetable feed used for scheduled Milan departures.

Data used: Stops, routes, trips, calendars and stop-time schedules for supported Milan stops.

Licence: Comune di Milano open-data terms

Agenzia TPL GTFS feeds

Milan, Monza Brianza, Lodi and Pavia basin

Agenzia TPL publishes GTFS operator feeds for regional services around Milan. DotClock currently ingests the Air Pullman, Movibus, STAR, STAV and NET feeds.

Data used: Scheduled stops, routes, calendars and stop-time departures for supported regional bus services.

Licence: Agenzia TPL open-data terms

Trenord

Lombardy rail

Trenord departure information is used for configured rail stations in supported areas.

Data used: Train number, category, destination, departure time, delay, cancellation status, platform and station name lookup.

Licence: Trenord service terms

Italy's National Access Point operated through CCISS publishes Lombardia NeTEx operator assets. DotClock parses these schedule-only feeds for supported regional stops.

Data used: Scheduled stop points, line names, journey patterns, day types and timetabled passing times from Lombardia NeTEx assets.

Licence: NAP / publisher terms for each NeTEx asset

Standards and context

DotClock also depends on shared transit formats and a small amount of date context to interpret the feeds correctly.

GTFS and GTFS Realtime

Open transit data standard

GTFS and GTFS Realtime are the interchange formats used by the Rome, Milan and regional GTFS feeds DotClock ingests.

Data used: Static schedules and realtime trip updates. The specifications are maintained separately from the transport data publishers.

Licence: Specification maintained by MobilityData; feed data remains licensed by each publisher

NeTEx

European transit data standard

NeTEx is the XML format used by the Lombardia assets DotClock reads from Italy's National Access Point.

Data used: Stops, lines, service journeys, day types and timetabled passing times.

Licence: Specification terms separate from publisher data terms

Nager.Date

Italy holiday context

Nager.Date helps DotClock decide whether Lombardia NeTEx schedules marked for holidays or non-holidays apply today.

Data used: Italian public holiday dates used only for schedule filtering.

Licence: MIT License

Coverage

Transit coverage is intentionally local. The backend currently supports Rome GTFS Realtime departures, static GTFS schedules for Milan and selected Agenzia TPL operators, Trenord train boards for configured stations, and Lombardia NeTEx regional schedules for configured stops.

1

Find nearby GTFS stops from the loaded static stop catalog when the device has location data and no explicit stop list.

2

Use configured stations and stops for trains and NeTEx regional services, which do not use automatic nearest-stop fallback.

3

Group departures by destination and send compact summaries with route labels, minutes, arrival time, platform and delay where available.

A note on attribution

DotClock is not affiliated with these transport agencies, operators, standards bodies or data publishers unless explicitly stated. Transit data is transformed by DotClock Cloud before it appears on the device, and the final display may combine static schedules, realtime updates and holiday context. Licence names above reflect each provider's terms at the time of writing; check the linked source or local feed publisher for the current terms before reuse.

← Back to home