All posts
TraccarDevicesProtocolsTroubleshooting

How to find the right protocol and port for any GPS tracker in Traccar

Nov 23, 20263 min read

The most common question from new Traccar users is simple: "Which port do I use for my tracker?" Traccar listens on a different port for each protocol, and a tracker sent to the wrong port just won't show up.

Here are three ways to find the answer, from quickest to most thorough.

Way 1: look it up

Search your brand and model on our supported GPS devices list. It lists more than 2,000 trackers with their protocol and port, based on Traccar's official list.

A few common ones:

Tracker Protocol Port
Concox GT06N and many GT06 clones gt06 5023
Teltonika FMB and FMC series teltonika 5027
H02-based trackers h02 5013
JT808-based trackers jt808 5015
iTriangle devices aquila 5089
AIS-140 standard devices its 5179

If your exact model is listed, use that port and you're done.

Way 2: the model isn't listed

Cheap trackers often have their own brand name but copy another protocol. The listing may show them as "clones". Try this:

  1. Check the manual or seller page for words like "GT06", "H02", "TK103" or "JT808". Those are protocol names.
  2. Look at the SMS commands in the manual. Commands like SERVER,1,domain,port,0# usually mean GT06. Commands starting with adminip often point to TK103-style protocols.
  3. Try the most likely port and watch the Traccar log (below).

Way 3: identify it from the raw data

Traccar writes every incoming message to its log in hex. That makes it possible to recognise a protocol even when you don't know it.

Point the tracker at your server on any Traccar port, for example 5023, and watch:

tail -f /opt/traccar/logs/tracker-server.log

Each line shows the protocol name of the port it arrived on, and the data. Now look at how the data starts:

Data starts with Likely protocol
78 78 or 79 79 gt06
2a 48 51 (text *HQ) h02
00 0f followed by digits (an IMEI) teltonika
7e jt808 or a related protocol
24 (text $) one of many text protocols, read the rest

If the data arrives on the wrong port, Traccar can't decode it, but you can still read it in the log. Once you know the protocol, change the tracker to that protocol's port.

You can also capture data directly on the server with tcpdump if the log is busy:

sudo tcpdump -i any -A port 5023

Once data arrives on the right port

If the log shows Unknown device with a number, the protocol is right and only the identifier is missing. Add a device in Traccar with exactly that number as its identifier.

Don't forget the firewall

Each port you use must be open on the server and in any cloud firewall:

sudo ufw allow 5023/tcp
sudo ufw allow 5023/udp

Some protocols use UDP, some TCP, some both. Open what your tracker uses.

Still stuck?

If the protocol truly isn't supported, Traccar is open source, and new protocol decoders can be added. That's something we do as part of custom Traccar development.

Or skip the guesswork: send us your tracker's brand and model on WhatsApp from the supported devices page, and we'll tell you the protocol and port.

Keep reading

Need help with your Traccar server?

I offer Traccar setup and maintenance, GPS tracking apps and Flutter development.