- Type
- not stated
- Format
- Multimodal — tabular/time-series trip and stop-event records, GTFS/GTFS-RT geospatial feeds, ticketing transaction records, CCTV video segments tied to events, plus API access (150+ integrations)
- Volume
- Dense and continuous: est. 10^7-10^8 stop-event records per operator per year (a 500-vehicle fleet x ~150 stops x 2 directions x ~300 service days ≈ 45M stop events/yr), each carrying arrival/departure timestamps, dwell and delay; passenger-loading records at tap-on/stop granularity on top; 1-5s telematics position pings during service (est. 10^8-10^9 pings/operator/yr); plus CCTV segments only around incident events, which keeps video volume bounded
- Users
- N/A to a B2B backend platform — Ridango serves operators, not riders directly. Reach instead: operator fleet base of the LIT/Ridango group across the Nordic and Baltic bus markets (group profile ~180 employees, ~$12M revenue, merger/acquisition history indicating multi-country roll-up), so est. tens of operators covering national and regional networks. Consumer-facing passenger accounts sit with LIT's ticketing deployments, not this product page, and are not published
- History
- 10 years
- Update frequency
- not stated
- Growth
- Active — current product page with an added AI chat assistant layer, rapid-pilot commercial motion (4-6 week pilots, often onboarded within 48 hours), hardware-agnostic AVL-light option to widen the addressable base, and an integration-led strategy (150+ APIs)
- Launched
- est. ~2004-2010 for the underlying LIT/InterGiro ticketing and operations lineage (dating from the group's merger/acquisition history and two decades of Nordic ticketing deployment), with this Data Intelligence analytics layer a much later addition, est. 2018-2022, matching the GTFS-RT/telematics-consolidation and time-band-analytics feature set
- Delivery
- not stated
- Entity mapping
- not stated
- Sample
- not stated
- Point-in-time
- not stated
- Licence
- not stated