GT06 Protocol · packet format, port, server commands
99 devices 4 brands Port 5023 (Traxelio) · 21100 commonly elsewhere TCP

GT06 Protocol (Concox / Jimi family)

Binary TCP protocol designed by Concox for the GT06 family · the most widely-deployed budget GPS tracker protocol worldwide. Used by Concox, Jimi, Aksh, and dozens of OEM-rebrand devices.

Talk to integration team Browse 99 supported devices Read the spec

3 min read · ~447 words

Quick answers

Is GT06 the same as Concox?

GT06 is the protocol; Concox is the original device maker that designed it. Today "Concox" usually refers to the company (now Jimi IoT after the 2018 rebrand), and "GT06" refers to the protocol all their devices · and dozens of OEM clones · speak. So a Jimi tracker speaks GT06, and so does a no-name AliExpress unit that copied the design.

What's the GT06 packet header?

0x78 0x78 for small packets (under 256 bytes). 0x79 0x79 for extended packets (larger payloads like image uploads). Every packet ends with 0x0D 0x0A (CRLF). The header is the fastest way to identify GT06 traffic in a TCP dump.

What port does GT06 use?

Configurable on the device side. Traxelio's ingest port is 5023 (TCP, matches the Traccar default). Some operators use 21100 or 7777. The device's SMS or configurator command sets whichever port the server expects.

Can I send commands back to a GT06 device?

Yes. The protocol supports server-to-device commands via protocol number 0x80 (general command) and protocol-specific codes (engine cut, alarm arm/disarm, location request, server change). Commands ride over the same TCP channel as positions · no SMS round-trip needed.

Does GT06 support CAN bus or fuel sensors?

Not in the base spec. GT06 was designed for the budget tier (consumer cars, motorcycles, basic fleet tracking) where CAN integration isn't expected. For CAN-bus depth, look at Teltonika Codec 8 or Ruptela. Some Jimi extended firmware adds RS485 fuel sensor channels on top of GT06 · check the device datasheet.

The GT06 protocol is the binary TCP wire format used by hundreds of low-cost GPS tracker models, originally designed by Concox for the GT06N tracker and adopted across the entire Concox / Jimi / iTrack family plus their many OEM rebrands. If your tracker cost under $30 wholesale and ships from Shenzhen, there is a very good chance it speaks GT06.

Protocol-at-a-glance

  • Transport · TCP
  • Default port · 5023 (Traxelio's ingest port; Concox's reference is configurable)
  • Encoding · binary, big-endian, packet header 0x78 0x78 (small packets) or 0x79 0x79 (extended)
  • Auth · Login packet (protocol number 0x01) carries IMEI; server returns ACK with same serial
  • Heartbeat · device sends 0x13 keep-alive; server replies 0x13
  • Spec · Concox publishes the GT06 protocol specification PDF (v1.8.1 is the canonical reference)

Packet structure (essentials)

Every packet has the same envelope:

0x78 0x78 [LEN] [PROTO] [BODY...] [SERIAL_HIGH] [SERIAL_LOW] [CRC_HIGH] [CRC_LOW] 0x0D 0x0A
  • LEN = body length
  • PROTO = protocol number (0x01 login, 0x10 GPS data, 0x13 heartbeat, 0x16 alarm, 0x80 server-to-device command, etc.)
  • BODY = protocol-specific payload (IMEI on login, GPS+speed+course+status on data)
  • CRC = ITU-T CRC-16 of the entire packet minus header and stop bytes

The simplicity is the point · ~30 bytes per position record, perfect for cheap 2G/3G modules that pay per byte on roaming SIMs.

Why GT06 is everywhere

  • Cheap silicon · Concox's reference design uses an ARM Cortex-M0 + Quectel modem · BOM under $8
  • Open enough · the spec leaks across the integrator community; every Chinese OEM cloning the design speaks the same protocol
  • Server-friendly · ~30-byte position records, fixed packet shape, fast to decode in any language
  • Bidirectional · server can push SMS-like commands (engine cut, alarm arm/disarm, server change) over the same TCP channel

The combination means thousands of OEM-rebrand devices ship under different names but all speak GT06: Concox GT06N, Jimi JM-VL01, Aksh GT01, Coban GT06 clones, and many AliExpress no-name trackers.

Configuring a GT06 device for Traxelio

Two paths · SMS commands or web configurator:

SMS path (most universal):

SERVER,1,traxelio.com,5023,0#
APN,internet#                          (or your carrier's APN)
RESET#                                 (reboot to apply)

(Some clones use different command syntax · check your model's SMS command sheet.)

Configurator path: most modern Concox / Jimi devices ship with a Windows configurator (GT06 Tool or vendor-branded). Connect via USB-to-serial, set the server IP + port, click Save, power-cycle.

Confirm the first decoded position in Traxelio. If it doesn't, the most common cause is wrong APN (data session never opens).

Supported devices in our catalog

99+ devices in the Traxelio tracker catalog declare protocol: "gt06" · the headline models: Concox GT06N, Concox AT4, Jimi JM-VL01, Jimi VL103D, Aksh GT01, plus the long tail of OEM rebrands.

Setup walkthrough

  1. 1

    Insert SIM with data plan + airtime

    Verify the SIM has an active data session in a phone first · GT06 devices have no UI to surface APN / signal failures, so a dead SIM looks identical to a working one.

  2. 2

    Send SMS configuration

    Send these commands to the device's SIM phone number (most clones accept them in any order, but APN before SERVER is safer). Replace your-server.com:5023 with your platform's endpoint.

    APN,internet#
SERVER,1,your-server.com,5023,0#
GPRS,1#
TIMER,30,60#
RESET#
  3. 3

    Power-cycle the device

    Disconnect and reconnect the main power (or wait for the RESET# to fire). The device opens a fresh TCP session on boot.

  4. 4

    Confirm first position arrives

    After GPS lock, confirm the first decoded position in Traxelio. If nothing arrives in 5 min, the most common cause is wrong APN (data session never opens) · re-send APN,...# with the correct value from your carrier's portal.

  5. 5

    Don't have a GT06 server yet?

    Traxelio decodes GT06 natively on port 5023. Send SERVER,1,traxelio.com,5023,0# to the device and the first decoded position can be verified in Traxelio · including engine-cut command support if your hardware has the relay wired. Or self-host Traccar · same decoder, same port.

Reference

Configuration reference

Parameter Value
Transport TCP
Default port 5023 (Traxelio) · 21100 commonly elsewhere
Packet header 0x78 0x78 (small) · 0x79 0x79 (extended)
Packet footer 0x0D 0x0A
Authentication Login packet protocol number 0x01, body = IMEI
Heartbeat Protocol number 0x13, server echoes
Checksum ITU-T CRC-16 over packet minus header + stop bytes
Configurator GT06 Tool (Windows, vendor-branded variants exist)
Spec PDF www.traccar.org/protocol/5023-gt06/GT06_GPS_Tracker_Communication_Prot...

SMS commands

SERVER,1,traxelio.com,5023,0#

Set Traxelio as the device server (mode 1 = TCP, port 5023, DNS lookup enabled).

APN,internet#

Set the SIM's APN (replace `internet` with your carrier's APN if different).

GPRS,1#

Enable GPRS data session (some clones need this explicitly after APN change).

TIMER,30,60#

Report every 30 s when moving, 60 s when stationary.

RESET#

Reboot the device to apply server + APN changes.

STATUS#

Query the device's current GPS / GSM / server-connected status. Returns SMS reply with diagnostics.

RELAY,1#

Engage the engine-cut relay (only on hardware with the relay wired · `RELAY,0#` releases).

Or skip the integration

Traxelio decodes GT06 natively

Point your device at our endpoint, then verify the first decoded position in Traxelio. We handle the protocol, ack the packets, and serve the dashboards.

Plan a protocol cutover Talk to integrators

Protocol Capabilities

Data Points from GT06 Devices

Traxelio processes all telemetry data sent by GT06 trackers for comprehensive fleet insights.

Core Tracking

  • GPS Location
  • Speed
  • Altitude
  • Heading / Direction
  • Street Address
  • GPS Accuracy

Engine & Driving

  • Ignition Status
  • Odometer / Mileage
  • Engine Hours

Sensors

  • Battery Level

Event Coverage

Alerts you'll get from devices on this protocol

Device online

The device is back online and transmitting data.

Device offline

The device has stopped reporting. It may have lost connection or power.

Device Moving

The vehicle is currently in motion.

Device Stopped

The vehicle is stationary.

Device overspeed

The vehicle is exceeding the set speed limit.

Geofence enter

The vehicle has entered a defined zone.

Geofence exit

The vehicle has exited a defined zone.

Alarm

Tow

Possible towing activity detected, check vehicle status.

Ignition On

The ignition is ON. The engine has started.

Ignition Off

The ignition is OFF. The engine has been stopped.

Long Idle

The vehicle has been idling for a long period.

Hard Braking

Hard braking detected, driver safety alert.

Hard Acceleration

Rapid acceleration detected, driving behavior alert.

Hard Turning

Sharp turning detected, driving behavior alert.

Impact Detected

Potential impact detected based on sudden deceleration and course change pattern.

Recommended

Featured GT06 Devices

Featured
Verified

JM-VL02

Concox
Featured

GT06N

Concox · $25 - $40

All Models

Representative GT06 Devices (99)

Start with the strongest matches, then use pagination or brand pages for the full compatibility list.

Verified

Concox GT800

Concox

Benway ET300

Benway

BW02

Concox

BW08

Concox

BW09

Concox

C32

Concox

Chentian OBD

Concox

Concox CRX3

Concox

Concox GK301

Concox

Concox GK503

Concox

Concox GT02D

Concox

Concox GT03

Concox

Buy + activate today

GT06 devices in our store

Ships from inventory · pre-configured for the Traxelio endpoint · arrives ready to install.

In store

Concox JM-VL02

$89.00
In store

Concox GT06N

$79.00

Compatible Brands

Brands Using GT06 Protocol

Concox

78 devices

SecumorePlus

19 devices

Benway

1 device

Seeworld

1 device

Note: many manufacturers (Coban TK103, Sinocastel, Goome, and others) implement GT06-compatible variants under their own protocol names. Check the relevant brand page to confirm compatibility before ordering.

Common troubleshooting

Device shows GPS lock but server never receives data

The SIM data session likely isn't opening. Check APN configuration (SMS: APN,internet#) and verify the SIM has data quota. A GT06 device with GPS lock but no GPRS will sit in that state indefinitely · the device has no way to surface the network failure.

Engine-cut relay command sent from server, but nothing happens

Three things to check: (1) relay is physically wired to the device's output pin (varies by model · check datasheet); (2) device firmware version supports the command (some clones omit the relay opcode); (3) device is currently online (commands queue but expire if the device is offline > 5 min).

Positions look correct but speed reads 0 even when moving

Speed is GPS-derived in GT06 (Doppler shift). If the device has weak GPS lock (urban canyon, garage, indoor), speed reads zero or jumps erratically while position interpolates. Check satellite count in the raw packet · under 4 satellites = unreliable speed.

Explore More

Other Protocols

H02

96 devices

Teltonika

84 devices

Meiligao

59 devices

GL200

36 devices

Huabao

32 devices

GPS103

31 devices
View All Trackers

FAQ

Frequently Asked Questions

Is the GT06 protocol officially published?

Concox publishes a protocol spec for integrators (v1.8.1 is the most cited revision). The PDF leaked widely across the integrator community years ago · search for 'GT06 GPS Tracker Communication Protocol' to find it. Traccar's open-source decoder is the most authoritative reference implementation.

Does GT06 work over 4G LTE?

Yes, on devices with 4G modems. The protocol is transport-agnostic at the application layer · 2G/3G/4G all work the same way to GT06. Newer Jimi and Concox devices ship with LTE Cat-1 modems and speak GT06 over LTE. The 2G sunset (already happened in some markets, coming in others) is forcing the catalog upward.

Why are there so many GT06 device models?

GT06 is a protocol, not a product. Hundreds of OEMs source the same Concox reference design (or near-clones) and rebrand. The protocol stays identical; the housing, the relay, the antenna, the firmware extras differ. From a server's perspective, it's all the same packet shape.

What's the difference between GT06 and Coban's GPS103 / TK103?

Different family. GT06 (Concox) is binary, packet-oriented, fixed envelope. GPS103/TK103 (Coban) is ASCII text, comma-separated, looks like a CSV row. Coban devices speak ASCII; Concox devices speak binary. Different decoders, different OEM ecosystems.

How does GT06 handle offline buffering?

Older firmware: limited (some devices buffer a few hours of positions in flash and dump them on reconnect, prefixed with an offline-flag byte). Newer Jimi firmware: better buffering, up to days of positions stored. Behavior varies by model · check the datasheet's offline storage field.

Talk to integration team
T
Trax
Online
Say hello to Trax!