Data Panda pulls your Wialon units, positions, trips and sensor events and lines them up with the rest of your fleet stack. From one place, we turn them into dashboards, automations, AI workflows and custom apps your fleet manager, finance and operations teams use every day.
Wialon is the flagship product of Gurtam, founded in 2002 in Minsk and now headquartered in Vilnius after the team relocated out of Belarus in 2022. The platform is hardware-agnostic by design: more than two thousand tracker models from over four hundred manufacturers feed into the same backend, which is why it ended up as the white-label engine under thousands of regional fleet brands rather than as a direct sale to one logistics operator. Gurtam's own numbers put the network at 2,700-plus service providers covering 150-plus countries and roughly five million commercial units; Berg Insight and the Wikipedia-cited 2024 figure put the connected-asset count just under four million. Either way, this is a platform-scale system, not a country-local tracker.
Most companies in Belgium and the Netherlands meet Wialon through a regional service provider rather than through Gurtam directly. The provider sells the hardware, installs it, brands the portal and handles support, and Wialon does the heavy lifting on positions, trip detection, geofences, fuel sensors, driver-ID, ECO-driving scores and the report engine. The Remote API and SDK are open enough that fleets pull their own slice into a warehouse, where Wialon stops being a reseller portal you log into once a week and starts being a feed your finance, planning and maintenance systems read every day.
Units, trips and sensor events joined to the accounting, CRM and maintenance data the rest of the business already trusts.
Turn Wialon trips and events into the nudges finance, dispatch and maintenance would otherwise chase by hand.
Use the trip and sensor history to predict where the fleet will be stretched and where a driver, route or device is drifting.
Small fleet, finance and dispatch tools that sit on Wialon data instead of another reseller-portal export.
A list of concrete reports, automations and AI features we have built on Wialon data. Pick the one that matches your situation.
Where is the gap between fuel-card litres and what the Wialon sensor recorded?
Wialon fuel-sensor readings per unit per week joined to the fuel-card transactions booked on the same plate. Finance sees which units are systematically over on the card, and fleet sees whether the gap traces to a single tracker model whose calibration has drifted, instead of arguing about it on receipts. The device-model column matters here: the same litres-per-hundred number means different things on a capacitive sensor versus a CAN-bus reading.
Across the resold accounts on our platform, who is generating the event volume?
Position pings and event count per Wialon resource and per unit type, rolled up against the partner that owns each resource. The hosting cost story stops being a flat per-unit fee and becomes a real picture of which end customers, route patterns or hardware models are driving server load, which is the conversation a reseller has to have before the next contract round.
Did the field engineer really visit the three sites on the route this morning?
Geofence-entry events per unit matched to customer addresses in the CRM, with arrival and departure time per stop. A service manager sees where the engineer was, how long they stayed and whether the visit lines up with the work order they closed, instead of taking the daily report at face value.
Cost per kilometre and litre per unit next to the leasing, insurance and fuel-card numbers from accounting, instead of three separate exports. Sensor drift on a particular tracker model becomes a quarterly conversation with numbers behind it, not a gut feeling at the budget round.
Field-service visits verified against the CRM on actual geofence-entry time per customer site. Engineers keep their autonomy and the service manager stops phoning around to reconstruct what happened this week from memory and timesheets.
Engine hours, fuel use and route adherence on one dashboard per fleet manager, with the device model on the same row. Dispatch and maintenance read the same picture, so the Monday call is about which unit goes where next and which one needs a workshop slot, not about whose Wialon report is the right one.
The route Solvice planned per vehicle joins the trip and position track Wialon recorded on that same unit. Planning sees per route where the driver took a detour, where idle time ate the slack and where the original plan was simply too tight, instead of a post-mortem from a tracker export. Optimisation gets a feedback loop the planner can act on next round.
Wialon kilometres and engine hours per unit flow into the fixed-asset records in Business Central on the right plate, so depreciation, residual value and finance lease coverage reflect what each truck has really done. The finance team runs the quarterly fleet review on live telematics data instead of on a meter reading the driver wrote down at the last service.
Wialon fuel-sensor consumption per unit per week is matched to the fuel-card supplier invoices booked in Exact Online on that same plate, with the gap per unit and per device model pulled out. Finance closes the week with each unit either in tolerance or flagged with the exact delta, and fleet sees whether a recurring drift sits on a particular tracker model rather than on a single driver.
Geofence-entry events on customer addresses in Wialon flow into HubSpot as logged activity on the matching company record, with arrival and departure time per visit. The service manager sees which planned interventions really happened and how long each stop lasted, instead of relying on a daily engineer report typed from memory at the end of the shift.
You keep the reporting tool you already have. We connect it to the warehouse where your Wialon data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.
Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.
We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.
We set up the foundation. Your team builds on top.
Best fit Teams that already have a BI analyst or data engineer and want to own the build.
We build the whole thing, end to end.
Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.
You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.
Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.
No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.
Through the Wialon Remote API, the connector brings the core operational tables into the warehouse: units (every vehicle, machine or asset registered on the account, with the device model and identifier), positions (the time-series location track per unit), trips (start, end, distance and duration per trip) and events (geofence entries, sensor triggers and notifications). That covers kilometres, fuel use, geofence dwell and route reporting. Raw video-telematics frames and the report-template engine are not part of the pull; the underlying numbers behind those reports are.
Yes. Wialon's resource model lets a hosting partner expose units across multiple end-customer accounts under a single API session, and the connector keeps the resource and account identifiers on every row. That is what makes per-tenant rollups possible: position-event volume per end customer, kilometres per resource, billing-relevant unit counts per partner. The same pull also serves a single-fleet customer who only sees their own resource.
Yes, and you want it to. Wialon stores the hardware type on the unit, and the connector keeps that column in the warehouse. Reports on fuel-sensor accuracy, position-frequency cost and even harsh-event scores really only become trustworthy when you can group by device model. A litres-per-hundred number that looks high across the whole fleet often turns out to sit on one tracker model whose calibration has drifted.
We review your Wialon setup and the systems around it. Together we pick the first thing worth building.