Device support: 4,800 types over 269 protocols.
How a unit gets connected.
Four steps from a unit in its box to positions on the map. The portal's documentation pages carry the details for each brand.
- Before fitting
Set server and port
Program the unit with your server's host name and the port for its protocol, using an SMS command or the manufacturer's configuration software. The Tracker ports page lists both by brand.
- In the portal
Add the IMEI
Create the device in the portal with its IMEI or ID and give it to a client account. A unit that reports before it is added appears in the server's list of unregistered devices.
- First report
Watch it arrive
The connection log, filtered by IMEI, shows raw data and decoded positions as the unit reports, so a wrong port or protocol is obvious straight away.
- Day to day
Send commands
Engine cut, reporting interval and other commands go out from the portal. A command for a unit that is offline waits in a queue until it reconnects.
Native listeners and the bridge.
The 11 protocols in the table run in native listeners. They cover the hardware most fleets use, and all of the video.
The protocol bridge adds 258 more, among them Queclink's GL200 family, Ruptela, Meitrack, Suntech, CalAmp, ATrack, Galileosky, Cellocator, Wialon IPS and OsmAnd, which phone tracking apps use. Each bridged protocol also has a port of its own.
| Protocol | Typical devices |
|---|---|
| Teltonika | FMB, FMC and FMU trackers, including CAN-ready installs |
| Teltonika DualCam | Road and cabin camera paired with a Teltonika tracker |
| GT06 | Concox units and the many trackers built on the same protocol |
| H02 | SinoTrack, TKSTAR and other H02 trackers |
| Cantrack H02 | Cantrack units that need a listener able to send commands |
| JT/T 808 | Trackers and mobile DVRs that use the Chinese transport standard |
| JT/T 1078 | Live video from dashcams that use the 1078 standard |
| Watch | SeTracker and Wonlex wearables |
| EV07 | Eview EV07 vehicle trackers |
| DMT | Digital Matter devices |
| Reachfar | Reachfar personal trackers |
Search the supported list.
This search contains a selection of common models. Click a maker's name for its models, or start typing a model code.
Largest makers in this search (click a name to list its models):
Several makers on one server
Units from different makers report side by side. One client might run Teltonika units on its trucks, GT06 trackers on its cars and a JT/T 1078 camera on a bus, and all of it shows up together on one map and in one set of reports.
Moving from another platform
From supported platforms the move is scripted: accounts and devices are copied across, stored positions are imported, and the units are then repointed to your server a batch at a time. Units on other platforms are repointed the same way.
Device questions
How do I find out whether my tracker model works?
Search the list on this page. It shows popular models only, and the supported set is larger. If yours is missing, send the make, model and firmware and we will check the protocol.
Can a phone act as a tracker?
Yes, with a tracking app that reports over the OsmAnd protocol. A phone is less dependable than a fitted unit, so it suits staff tracking and trials better than vehicles.
What happens to positions if the server cannot be reached?
Most trackers keep records in memory and send them when the link is back. The server acknowledges a record only after saving it, so anything not stored is sent again.
Related technical pages
Put it on your own server and try it.
Order online and your server is normally live the next day, with your domain and logo in place and the tracker ports open.