Supported trackers and ports
The bridge decodes 200+ protocols; these are the ones with an open port today.
The bridge is a Traccar server run by LemursEye. It decodes more than 200 tracker protocols. Each protocol listens on its own TCP port; only the ports below are open on the public address today, and more are opened on request.
| Protocol | Port | Typical devices |
|---|---|---|
| GT06 / Concox | 5023 | Concox GT06N, GT06E, WeTrack, JM-VL01, most cheap Chinese OBD and wired trackers |
| Teltonika | 5027 | FMB120, FMB920, FMC130, FMB003 |
| H02 | 5013 | SinoTrack ST-901, ST-906, ST-915 and many rebadged units |
| OsmAnd | 5055 | Phone apps: Traccar Client, OsmAnd |
Server address: gps.lemurseye.com (it points at 109.199.113.161). Configure devices with the name, not the number: if the server ever moves, one DNS change re-points every tracker, instead of a visit or an SMS to each vehicle. A few firmwares only take an IP; their pages say so.
Choosing a tracker
For a first fleet in Egypt the practical choice is a wired 4G tracker with an ignition input: the ignition signal is what makes idle cost and engine-hours real. Concox GT06 family units are cheap and widely available; Teltonika FMB/FMC units cost more and report richer data (odometer, fuel level from CAN on some models, harsh driving). SinoTrack ST-901 is the cheapest common unit; it speaks H02.
Avoid OBD plug-in trackers for commercial fleets: drivers unplug them.
Not on the list?
Send us the model. If the bridge decodes it, the port is opened the same day.