Integration guides for the manufacturers we are asked about most, written for installers rather than for a brochure — protocols, sensors, configuration and what to check before you buy in volume.
Six manufacturers cover most of what actually gets installed in this region. Each guide covers the protocol, the sensors, the configuration path and the honest caveats.
Platforms implement protocols, not model numbers. This is the coverage that produces the device count.
| Protocol family | Typical manufacturers | Notes |
|---|---|---|
| Codec 8 / 8 Extended | Teltonika | Typed IO elements; the richest sensor data of the common protocols |
| GT06 family | Concox, and many rebranded clones | Compact and cheap; IO mapping varies between clones |
| @Track | Queclink | ASCII and binary; correct ACK handling prevents duplicate reports |
| Ruptela binary | Ruptela | Native CAN and tachograph depth for heavy vehicles |
| MEITRACK | Meitrack | One command set across vehicle, asset and personal units |
| JT/T 808 derivatives | Jimi IoT, Howen, several Chinese OEMs | Common on dashcam and video telematics hardware |
A guide page does not exist for every brand, but support does. If yours is here, or even if it is not, ask.
We do not sell trackers. We are not a reseller for any manufacturer on this page, we take no margin on hardware, and we have no incentive to route you toward a more expensive unit. That is worth stating plainly, because most device advice in this industry comes from somebody with a box to move.
The practical consequence is that the guides above will tell you when a cheaper model does the same job, and when a brand that looks like a bargain will cost you more in support than it saves in purchase price. Both are genuinely true more often than the market admits.
What do you need to report on? Position and trips need almost nothing. Fuel loss needs a probe or CAN. Plant billing needs engine hours. Incident defence needs video. Start from the report and work backwards to the unit, rather than buying a tracker and discovering later what it cannot tell you.
What network will it live on? 2G shutdowns have already happened in several markets and will happen in more. A 2G-only tracker is cheap today and stranded within the asset’s working life. Check the network roadmap in every country you will deploy in, not just the one you are standing in.
Who installs it, and can they reach it again? A tracker that needs a physical visit to reconfigure is a tracker that will never be reconfigured. Every manufacturer on this page supports remote server and parameter changes; make sure whatever you buy actually does, because it determines what a future migration costs you.
Send us your device list, or just the models you are considering. Request a compatibility check or message us on WhatsApp — we will test against a live server and tell you what works, what does not, and where you could spend less.
Over 1,000 models across more than 50 manufacturers. That number comes from protocol coverage rather than individual model testing — the platform implements the major tracker protocols, and any device speaking one of them reports in. If your manufacturer is not listed here, ask anyway; the long tail is much longer than the six hubs above.
No. The six hubs above are the manufacturers we are asked about most, not the limit of what is supported. Many smaller brands ship firmware derived from GT06 or JT/T 808, which is already implemented. Send us the model and we will tell you within a day.
We write the protocol integration. What you should ask for is a concrete answer on who does the work, how long it takes and what it costs — and you should be sceptical of any vendor whose answer is "we will look into it", because that is how a signed deal becomes an apology six weeks later.
No. We do not require hardware purchases and we are not a reseller for any manufacturer, which is why the pages above are willing to say when a cheaper unit would do the same job. Buy your trackers wherever you get the best price and support.
Yes, and most fleets above a few hundred vehicles end up doing exactly that. Each protocol has its own listener and all of them normalise into a shared position and event model, so reports, geofences and driver scoring behave identically regardless of which brand produced the record.
Send the model and firmware version. We test it against a live server and give you a straight answer, usually within a day.
Check My Device →