25 devices 15 brands

Eelink Protocol

Eelink old/new binary on Traccar TCP/UDP 5064 with BLE MAC tags, OBD decode path, and length-field framing.

Connect your tracker

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

Browse 25 supported devices

Quick answers

Stock port?

5064 (TCP and UDP in EelinkProtocol).

ASCII?

No — length-field binary with old/new package decoders.

OBD / BLE?

Open decoder includes OBD path and BLE MAC/tag helpers.

Eelink uses length-field binary framing (LengthFieldBasedFrameDecoder offset 3, length 2) on stock port 5064, with TCP and UDP servers. EelinkProtocolDecoder branches into decodeOld / decodeNew, plus OBD and result paths. BLE-related tag strings and illuminance/CO2-style attributes appear in the open decoder.

Old vs new packages

Firmware generation changes package layout. A hex sample that matched “old” may fail after a vendor upgrade — capture package type before blaming the host.

Sibling contrast

Aplicom on 5049 is another binary CAN/event stack, but Aplicom’s cold-unit/alarm hex vocabulary differs from Eelink’s BLE/OBD package types.

Catalogue stance

Traccar stock reference; Traxelio positions_only.

Setup walkthrough

  1. 1

    Confirm Eelink package generation

    Note old vs new firmware before comparing hex samples.

  2. 2

    Aim at TCP 5064

    Host + 5064; UDP only if the sheet requires it.

  3. 3

    Prove binary length-field frames

    Not line ASCII; keep a hex capture of the first packages.

  4. 4

    Optional OBD/BLE check

    If fitted, confirm those attributes after a fix.

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.

Eelink SERVER hash commands

Guided setup available

gps.traxelio.com:5064 1 example model
Eelink TK319

Set server

SERVER,0,gps.traxelio.com,5064#

Set reporting interval

TIMER,60#

Check parameters

PARAM#

APN commands depend on the carrier SIM in your tracker, so they are not shown here.

Eelink V1

Guided setup available

gps.traxelio.com:5064 4 example models
ET301 Eelink GOT08 Eelink GOT10 Eelink GPT06

Set server

SERVER,"tcp://gps.traxelio.com:5064"#

Set reporting interval

COLLECT,60#

APN commands depend on the carrier SIM in your tracker, so they are not shown here.

Reference

Configuration reference

Parameter Value
Port 5064

Telemetry fields

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

All Models

All Eelink Devices (25)

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

Eelink GOT08

Eelink

Eelink GOT10

Eelink

Eelink GPT06

Eelink

Eelink GPT06-3G

Eelink

Eelink K6

Eelink

Eelink K9+

Eelink

Eelink TK115

Eelink

Eelink TK319

Eelink

ET301

ET301

Goome GM06NW

Goome

GPT06-3G

GPT06 model family

GPT09

GPT09

GPT12-L

GPT12

GPT15

GPT15

GPT18

GPT18

GPT19

GPT19

GPT26

GPT26

GPT46

GPT46

K30

K30

TK119

TK119

TK119-3G

TK119

TK119-T

TK119

TK319-H

TK319

TK319-L

TK319

WTR1-T

WTR1

Compatible Brands

Brands Using Eelink Protocol

Eelink

8 devices

TK119

3 devices

TK319

2 devices

ET301

1 device

Goome

1 device

GPT06 model family

1 device

GPT09

1 device

GPT12

1 device

GPT15

1 device

GPT18

1 device

GPT19

1 device

WTR1

1 device

Common troubleshooting

Aimed at Aplicom 5049

Retarget to 5064; Aplicom cold-unit frames will not satisfy Eelink packages.

Breaks after firmware upgrade

Old/new decode branches diverge; re-capture package headers.

BLE tags empty

Tag scanning may be off; decoder only emits present tags.

Explore More

Other Protocols

Aplicom

8 devices

Obddongle

0 devices

Bce

10 devices
View All Trackers

FAQ

Frequently Asked Questions

Same as ObdDongle row?

No. Eelink is its own 5064 binary family with optional OBD package types.

Command coverage claimed?

Not asserted — positions_only.

Connect Eelink tracker
T
Trax
Online
Say hello to Trax!