Proof
Every entry below is a real deployment. Every customer name is pending publication sign-off. We would rather show you the structure of the proof than borrow credibility we have not confirmed in writing.
01 · The deployments
Situation. A fleet financier and operator running a large electric bus fleet, with strict asset-protection requirements.
Deployed. ZAPPP across ~1,000 buses; ~3,000 vehicles across the relationship. Contactless, warranty-safe install was the deciding factor.
What changed. Zenobē runs legacy telematics and ZAPPP in parallel, because the data requirements are fundamentally different. The old system still tracks vehicles. ZAPPP reads the batteries.
Situation. A 300-vehicle electric deployment with a hard timeline.
Deployed. 300 vehicles in 90 days, phased rollout.
What changed. Fleet-wide telemetry at 1Hz inside one quarter: proof of deployment speed, not just platform capability.
Situation. One of Denmark’s largest electric bus fleets, managing readiness through manual depot checks and driver phone calls. Danish temperatures run -10°C to 30°C.
Deployed. Design partner for ZAPPP Ops Pack. BYD fleet, BYD Fleet Link telemetry, hourly schedule exports.
What changed. Schedule-vs-reality comparison and 8–10 hour SOC forecasting in live operations; temperature-aware consumption modelling validated against a real Scandinavian winter.
Situation. Industrial and heavy EV platforms with no third-party telemetry depth.
Deployed. Existing customers; validated CAN channel maps.
What changed. OEM coverage that competitors list as a roadmap item is validated and in service here.
02 · Where
Validated across BYD · Yutong · SANY · JAC · Alexander Dennis · Volvo · Wrightbus · Ebusco · Solaris and others.