Fleet tracking · Edinburgh

Fleet tracking for taxi fleets in Edinburgh

Live driver pins, geofences, and replay — accurate to 200ms. Configured for City of Edinburgh Council Licensing.

Fleet tracking in Edinburgh is the live driver pins, geofences, and replay — accurate to 200ms, configured against City of Edinburgh Council Licensing and the operating reality of a 2.4k-vehicle market. TaxiCloud Fleet Tracking ships live driver-pin tracking, geofenced coverage zones, route replay for incident review, and aggregate fleet-utilisation analytics. Driver GPS pings stream over WebSocket at 200ms latency. For Edinburgh specifically, the feature reads from regulator-aware booking, dispatch, and reporting surfaces — no bolt-on integration, no separate console.

Fleet tracking in Edinburgh — the operating reality

Fleet tracking ships against the Lothian operating geography as a structural object. Fleet tracking is the foundation that makes live dispatch, customer-app live tracking, and dispute resolution all work. TaxiCloud's tracking layer is engineered around 200ms ping latency — driver GPS streams to the WebSocket gateway, fans out to dispatch board, customer app, and supervisor view, and updates pins in lockstep. The result is a tracking experience that matches Uber and Bolt on responsiveness rather than the polling-refresh feel that legacy dispatch platforms ship with. In Edinburgh, the feature posts cleanly against City of Edinburgh Council Licensing quarterly returns, vehicle inspection cycles, and the 2,400-vehicle scale that defines the market. EDI airport flows integrate natively where applicable.

How TaxiCloud delivers fleet tracking in Edinburgh

Operators in Edinburgh typically run fleet tracking on TaxiCloud after a 6-10 day migration off iCabbi, Autocab, Cordic, or TaxiCaller. Geofences are first-class objects. Coverage zones (your operating area), airports (terminal pickup zones), restricted areas (Old Town in Edinburgh, congestion zones in London), and corporate-account boundaries all configure as geofences with entry / exit events. The dispatch board flags geofence events in real time; AI Copilot uses geofence state to rank reassignment suggestions; the customer app surfaces geofence-triggered information (e.g. "Your driver has entered the airport pickup zone"). The dispatcher impact is highest in the Edinburgh operating tempo because City of Edinburgh Council Licensing compliance overlays the standard PHV regulatory posture, and fleet tracking surfaces the resulting reports through the same dispatch flow rather than as a separate finance task.

FAQ

Fleet tracking in Edinburgh — questions answered.

How does Fleet tracking work in Edinburgh?: Fleet tracking in Edinburgh reads from the live dispatch board, the customer-facing booking widget, and the City of Edinburgh Council Licensing compliance reporting layer in a single tenant. Driver app streams GPS pings over WebSocket at 200ms intervals. The Edinburgh configuration is preset for the city's 2,400-vehicle market and the Lothian operating geography.
Is Fleet tracking compliant with City of Edinburgh Council Licensing?: Yes. Fleet tracking is calibrated for City of Edinburgh Council Licensing reporting, audit, and renewal cycles. Vehicle inspection deadlines, driver-licence audits, and the local quarterly return format ship pre-configured. Format updates land in-sprint when the regulator changes requirements.
What does Fleet tracking cost for a Edinburgh fleet?: Fleet tracking ships on every TaxiCloud plan — Starter through Pro Ultra. Transparent £49-£349/month pricing. Most Edinburgh fleets run Pro (£149/€55/$59/A$89 month) or Pro Max (£349/€395/$449/A$629 month). No setup fee on Starter or Pro; month-to-month contracts; fleet tracking configuration in Edinburgh is included.

Ready when you are

Dispatch on autopilot.

14-day free trial. No card. Cancel anytime.

47 fleets joined this month · Talk to sales