Meitrack support
Meitrack trackers on Nexara.
Meitrack devices decode into the same position and event shape as the rest of the fleet, with no per-manufacturer branching in your application.
meitrackProtocol-level support
Meitrack is supported at the protocol level rather than as a fixed model list. Rather than publish a model grid we cannot stand behind, we confirm your exact hardware against a packet capture before you commit to it.
Check my Meitrack devicesWhat you get once Meitrack telemetry lands
Decoded Meitrack data is normalized into the same event model as every other manufacturer — so the REST API you write against does not branch per vendor, and the white-label tracker renders it without per-device work.
Other supported manufacturers
Queclink
In productionThe most heavily exercised family on the platform. Two decoders — a general Queclink parser and a dedicated GV50CNA implementation — cover position, ignition, movement, power and event reporting.
Queclink device support →Teltonika
SupportedTeltonika telemetry is decoded into the same normalized event model as every other manufacturer, so an application written against Nexara does not change when the hardware does.
Teltonika device support →Concox
SupportedConcox GT06-family devices are decoded natively, covering the low-cost end of the market that distributors most often start with.
Concox device support →AsiaTelco
SupportedAsiaTelco (ATEL) devices are decoded on a dedicated ingestion port, carried over from an earlier deployment so existing hardware kept reporting through the migration.
AsiaTelco device support →Hardware that isn’t on this list
Nexara carries a configuration-driven decoder alongside the per-manufacturer ones. A protocol is described as data — framing, login handshake, field offsets — rather than written as code, so adding a device family does not require a platform release. Send us a packet capture and we can tell you whether your hardware decodes.
Evaluate my devices