25 devices 2 brands

TK103 Protocol

TK103 family dialect on Traccar TCP/UDP 5002 — distinct from Gps103 on port 5001 — with handshake and alarm codes.

Connect your tracker

Enter the tracker IMEI first, then verify your email and continue setup.

Browse 25 supported devices

Quick answers

Stock port?

5002 (TCP and UDP servers in Tk103Protocol).

Same as Gps103?

No. Gps103 stock port is 5001 with a different decoder.

Handshake?

Open decoder includes an explicit handshake path.

TK103 is its own Traccar protocol on stock port 5002 (TCP plus a UDP server in Tk103Protocol). Tk103FrameDecoder + Tk103ProtocolDecoder handle device-id/command patterns, handshakes, cell/Wi-Fi extensions, BMS snippets, and alarms (SOS, power-cut, tamper, vibration, geofence exit, and more).

Not Gps103

Gps103 stock port is 5001. Silkscreens saying “TK103/GPS103 compatible” still need the correct listener: 5002 for this decoder family, 5001 for Gps103’s regular/OBD/photo paths. Mixing ports yields silent units.

Frame clue

Expect TK103 command/id grammar from Tk103ProtocolDecoder, not Gps103’s alternate OBD sentence shapes.

Catalogue stance

Traccar stock reference; Traxelio positions_only.

Setup walkthrough

  1. 1

    Pick TK103 vs Gps103 deliberately

    Sheets citing port 5001 or Gps103 OBD lines belong on gps103.

  2. 2

    Configure host + 5002

    Write TCP 5002 (UDP only if the SKU sheet says UDP).

  3. 3

    Complete handshake then first fix

    No handshake/id exchange usually means wrong port or APN.

  4. 4

    Alarm spot-check

    SOS or power-cut proves event codes beyond bare coordinates.

Setup

Public setup commands

Use these rows only after confirming the tracker password and SIM settings. Command families can differ between brands even when they use the same protocol.

Reference

Configuration reference

Parameter Value
Port 5002

Telemetry fields

GPS Location Speed Altitude Heading / Direction Street Address GPS Accuracy Ignition Status Odometer / Mileage Engine Hours Battery Level

All Models

All TK103 Devices (25)

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

EC-546

Coban

KS168

Coban

P168

Coban

P169

Coban

T1024

Coban

T1080

Coban

T12

Coban

T15400

Coban

T16

Coban

T18

Coban

T2024

Coban

T2124

Coban

T4400

Coban

T8800

Coban

TK05

Coban

TK10

Coban

TK15

Coban

TK206

Coban

TK207

Coban

TT0024

Coban

Kingneed T15400

Kingneed

Kingneed T4400

Kingneed

Kingneed T8800

Kingneed

Kingneed TK05

Kingneed

Kingneed TK20

Kingneed

Compatible Brands

Brands Using TK103 Protocol

Coban

20 devices

Kingneed

5 devices

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

Common troubleshooting

Unit on 5001 stays silent

5001 is Gps103. Move TK103 family firmware to 5002.

Handshake loops

IMEI/id format mismatch; compare raw id to decoder patterns.

Alarms missing

Event reporting disabled in SMS sheet; positions may still decode.

Explore More

Other Protocols

GPS103

19 devices

Fifotrack

13 devices

H02

72 devices
View All Trackers

FAQ

Frequently Asked Questions

Why separate from Gps103?

Different stock ports (5002 vs 5001) and different Traccar decoders — swaps create silent BYOD tickets.

Command provisioning claimed?

Not claimed. Support level is positions_only.

UDP allowed?

Traccar registers TCP and UDP for Tk103; follow the SKU sheet.

Connect TK103 tracker
T
Trax
Online
Say hello to Trax!