Teltonika Codec 8 Protocol · port, AVL packets, CAN bus
84 devices 3 brands Port 5027 (Traxelio) · 8500 (FOTA Web) TCP

Teltonika Codec 8 Protocol

Binary TCP protocol published by Teltonika (Vilnius, Lithuania) for its FMB / FMC / FMM hardware families · Codec 8 and Codec 8 Extended are the wire formats most professional fleets use to push positions, CAN bus, and sensor channels to a fleet server.

Talk to integration team Browse 84 supported devices Read the spec

4 min read · ~615 words

Quick answers

Is Codec 8 the same as Teltonika protocol?

Yes · they're the same thing under different names. Teltonika publishes the spec as 'Codec 8' (legacy) and 'Codec 8 Extended' (current). Operators casually say 'Teltonika protocol' meaning the codec. Both refer to the binary AVL TCP wire format Teltonika FMxxxx devices use.

What port does Codec 8 use?

Configurable on the device side. Traxelio's ingest port is 5027 (TCP, matches Traccar's default). Teltonika FOTA Web defaults to 8500. The configurator's GPRS section sets whichever port the server expects.

What's the difference between Codec 8 and Codec 8 Extended?

Codec 8 supports I/O element IDs 0-255 (one byte). Codec 8 Extended raises the ceiling to 0-65535 (two bytes), which matters for newer Teltonika models with rich CAN profiles (FMC230 heavy-vehicle, FMM250). Both share the same packet envelope; Extended is opt-in via the configurator. Traxelio decodes both.

Can I send commands to a Teltonika device over the protocol?

Yes · Codec 12 carries server-to-device commands on the same TCP channel as positions. The command set includes engine cut (digital output toggle), server change, configuration push, immediate position request, and arbitrary GPRS commands. No SMS round-trip needed.

Does Codec 8 support CAN bus?

Yes · CAN data rides as I/O elements within the standard packet. Teltonika maintains a master list of CAN-derived I/O IDs at wiki.teltonika-gps.com/view/AVL_Data (fuel level, total fuel used, engine hours, RPM, vehicle speed, axle weight, etc.). The right CAN profile must be loaded for the vehicle make/model · Teltonika's CAN Adapter Tool catalogs the profiles per Mercedes/Volvo/MAN/DAF/Scania/etc.

The Teltonika protocol (canonically called Codec 8 and Codec 8 Extended) is the binary AVL wire format Teltonika GPS trackers use to report data. It is the industry reference for the mid-to-pro fleet tier · designed for high-throughput telemetry (50+ I/O channels per packet), efficient binary encoding (well under 100 bytes per record), and reliable offline buffering (tens of thousands of records held when GPRS is down).

The spec is published in full at wiki.teltonika-gps.com · this openness is why third-party servers (Traccar, Flespi, Traxelio, and Teltonika's own FOTA Web) can all decode the same stream.

Protocol-at-a-glance

  • Transport · TCP
  • Default port · 5027 (Traxelio's ingest port; configurable on the device side via configurator)
  • Encoding · binary AVL records, length-prefixed, big-endian
  • Auth · IMEI handshake in first packet (length-prefixed UTF-8 string); server replies 0x01 (accept) or 0x00 (reject)
  • Codec versions · Codec 8 (legacy, fully supported), Codec 8 Extended (current, supports >255 I/O element IDs)
  • Other codecs · Codec 12 (commands), Codec 13 (NMEA), Codec 14 (configuration) ride alongside on the same connection

Packet structure (Codec 8 Extended)

[PREAMBLE = 0x00000000] [DATA_LENGTH] [CODEC_ID = 0x8E] [N_RECORDS]
  [RECORD 1] [RECORD 2] ... [RECORD N]
[N_RECORDS] [CRC-16/IBM]

Each record:

[TIMESTAMP (8B, ms since epoch)] [PRIORITY (1B)]
  [GPS: lon (4B) | lat (4B) | alt (2B) | angle (2B) | sats (1B) | speed (2B)]
  [IO_EVENT_ID (2B)] [N_TOTAL_IO (2B)]
  [N_1B_IO] [1B IO_ID + 1B value] × N
  [N_2B_IO] [2B IO_ID + 2B value] × N
  [N_4B_IO] [2B IO_ID + 4B value] × N
  [N_8B_IO] [2B IO_ID + 8B value] × N
  [N_XB_IO] [2B IO_ID + variable] × N    # Extended codec only

The I/O element IDs are documented per device model · Teltonika maintains a master list at wiki.teltonika-gps.com/view/AVL_Data. Some examples: ID 16 = Total Odometer, ID 17 = Accelerometer X, ID 21 = GSM Signal, ID 66 = External Voltage, ID 67 = Battery Voltage, ID 200 = Sleep Mode.

Why Teltonika hardware ships this protocol

  • Deep I/O · 50-200+ I/O elements per packet (vs ~10 in GT06, ~15 in H02) · fits CAN, OBD, sensor, and event channels in one record
  • Codec 8 Extended · raised the I/O ID ceiling from 255 to 65535 · matters for FMC230 / FMM250 with rich CAN profiles
  • Offline buffering · device holds 10,000+ records in flash · drains them on reconnect prefixed with a priority=0 flag
  • Bidirectional · Codec 12 commands flow server-to-device on the same TCP channel (no SMS round-trip needed for engine cut, server change, configuration push)

The trade-off vs the budget tier (GT06, H02, GPS103): Teltonika hardware costs 5-10x more per unit. For fleets where CAN bus depth, install quality, and 24-month warranty matter, that's the right trade.

Configuring a Teltonika device for Traxelio

Two paths · Teltonika Configurator (Windows desktop) or FOTA Web (over-the-air):

Configurator path (initial setup):

  1. Download Teltonika Configurator from wiki.teltonika-gps.com
  2. Connect via USB cable
  3. Open the GPRS section · set Domain to traxelio.com, Port to 5027, Protocol to TCP
  4. Set Codec to Codec 8 Extended (or Codec 8 for older FMB1xx models)
  5. Save to device · device reboots
  6. Confirm the first decoded position in Traxelio

FOTA Web path (already in your fleet):

  1. Log into fm.teltonika.lt (Teltonika's free OTA platform)
  2. Select your device by IMEI
  3. Configuration > Edit > GPRS section · set the new server endpoint
  4. Push configuration · device picks it up on next connection

The IMEI stays the same. The SIM stays the same. Only the destination server changes. No re-install.

Supported devices in our catalog

83+ devices declare protocol: "teltonika" · the headline models: FMB001 (OBD plug), FMB125 / FMB140 (wired pro fleet), FMC125 / FMC150 (4G LTE pro), FMC230 (heavy-vehicle CAN), FMM130 / FMM250 (compact 4G), FMT100 (asset tracker). The full Teltonika catalog is supported · any FMxxxx model with Codec 8 or Codec 8 Extended in its datasheet works.

Setup walkthrough

  1. 1

    Choose your config path

    Teltonika Configurator (Windows USB-attached) for initial setup. FOTA Web (free cloud platform at fm.teltonika.lt) for fleets already deployed · no physical access needed.

  2. 2

    Set the server endpoint

    In the GPRS section: Domain = your platform's host, Port = your platform's listener (Traccar default for Codec 8 is 5027), Protocol = TCP. Codec: Codec 8 Extended for FMB1xx-and-newer; Codec 8 for legacy FMB1xx pre-2018.

  3. 3

    Optional · enable dual-server

    Modern firmware supports a primary + secondary endpoint. Useful for validation · push the same record to both your previous platform and the new one for a week before cutting over.

  4. 4

    Save and reboot

    Click Save to Device · reboots automatically. Confirm the first decoded position in Traxelio.

  5. 5

    Confirm I/O elements decode correctly

    Spot-check 2-3 devices on the new server · CAN bus / fuel / engine-hours channels should match what FOTA Web showed. If a channel is missing, the CAN profile likely needs loading via Teltonika's CAN Adapter Tool.

  6. 6

    Don't have a Codec-8 server yet?

    Traxelio decodes Codec 8 and Codec 8 Extended natively on port 5027 · point your Configurator at the Traxelio endpoint and the first I/O-rich record lands after the device opens a data session. Or self-host Traccar / Flespi · same Teltonika decoder, same port convention.

Reference

Configuration reference

Parameter Value
Transport TCP
Default port 5027 (Traxelio) · 8500 (FOTA Web)
Encoding binary AVL, length-prefixed, big-endian
Authentication Length-prefixed IMEI in first packet · server replies 0x01 (accept) or 0x00 (reject)
Checksum CRC-16/IBM over packet body
Codec versions Codec 8 (legacy), Codec 8 Extended (current), Codec 12 (commands), Codec 13 (NMEA), Codec 14 (configuration)
Offline buffering 10,000+ records in flash · drain on reconnect with priority=0
Configurator Teltonika Configurator (Windows) · FOTA Web (cloud)
Spec wiki wiki.teltonika-gps.com/view/Codec
AVL data ID list wiki.teltonika-gps.com/view/AVL_Data

Or skip the integration

Traxelio decodes Teltonika 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 Teltonika Devices

Traxelio processes all telemetry data sent by Teltonika 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
  • Fuel Level

Network

  • Network / Cell Info

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.

Fuel Refill

A fuel refill was detected.

Recommended

Featured Teltonika Devices

Featured
Verified

FMB920

Teltonika · $28 - $40
Featured
Verified

FMC003

Teltonika
Featured

FMB130

Teltonika · $32 - $45
Featured

FMB140

Teltonika · $60 - $80

All Models

Representative Teltonika Devices (84)

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

Verified

FMB001

Teltonika
Verified

FMC150

Teltonika
Verified

FMC920

Teltonika
Verified

FMT100

Teltonika

Bitrek Series

Bitrek

Damoov Telematics SDK

Damoov

CT2000E

Teltonika

FCM650

Teltonika

FM1010

Teltonika

FM1100

Teltonika

FM1110

Teltonika

FM1120

Teltonika

Buy + activate today

Teltonika devices in our store

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

In store

Teltonika FMB125

F CFA 50,000
In store

Teltonika FMC125

£85.14

Compatible Brands

Brands Using Teltonika Protocol

Teltonika

82 devices

Bitrek

1 device

Damoov

1 device

Common troubleshooting

Device shows GPS lock but no I/O elements (CAN, fuel, sensors)

CAN profile not loaded · the device needs the right vehicle-specific CAN profile installed via CAN Adapter Tool (Mercedes Actros uses a different profile than Volvo FH or DAF XF). Without a matching profile, the device reports basic GPS only · the CAN side stays empty.

Position records arrive but timestamps are off by hours

Teltonika timestamps are Unix milliseconds UTC. If your dashboard shows local-time-shifted values, the issue is on the display layer (timezone conversion), not the protocol. If timestamps are off-epoch nonsense (year 1980, year 2106), the device's RTC drifted · power-cycle the device and wait for the GPS module to resync the clock.

Device reports correctly via FOTA Web but goes silent after a server change to Traxelio

Two things to check: (1) APN configuration matches the SIM (FOTA Web defaults often work because Teltonika has APN auto-detect for common European SIMs; on African / Asian SIMs you need to set APN manually). (2) The IMEI is correctly registered in Traxelio · check the device's IMEI matches a TrackerDevice record before assuming a wire-protocol issue.

Explore More

Other Protocols

GT06

99 devices

H02

96 devices

Meiligao

59 devices

GL200

36 devices

Huabao

32 devices

GPS103

31 devices
View All Trackers

FAQ

Frequently Asked Questions

Is the Teltonika protocol open?

Yes, fully documented. Teltonika publishes the Codec 8 and Codec 8 Extended specs on its public wiki (wiki.teltonika-gps.com/view/Codec). Any server with access to the wiki can decode the same stream Teltonika FOTA Web decodes. That is why Traccar, Flespi, Traxelio, and many in-house fleet platforms all support it.

Can I run a Teltonika device dual-server (FOTA Web + Traxelio)?

Yes, on most current firmware. The GPRS section of the configurator supports a primary and a secondary server. The device pushes the same record to both. Useful during migration · run dual-stream for a week to validate Traxelio's decoding matches FOTA Web's, then cancel the primary.

What's the difference between Codec 8 and the older Codec 6?

Codec 6 is the deprecated predecessor · removed from current Teltonika firmware. Codec 8 added the I/O element framework that makes the rich CAN/sensor reporting possible. If you encounter Codec 6 in the wild it's on very old hardware (pre-2014). Traxelio decodes Codec 8 and Codec 8 Extended; Codec 6 is not supported.

Does Teltonika hardware work over 2G?

Older FMB1xx models, yes (with 2G/3G modems). Current production (FMC1xx, FMM1xx, FMC2xx) is LTE Cat-1 / Cat-M1 with 2G fallback only. The protocol itself is transport-agnostic · whatever radio layer the modem uses, Codec 8 rides on top transparently.

Why is Teltonika hardware more expensive than Concox or Coban?

Different segments. Teltonika targets professional fleet operators where CAN bus depth, FOTA over-the-air management, 24-month warranty, and EU-made silicon matter more than per-unit cost. Concox / Jimi / Coban target the budget end. The price-per-feature curve is roughly: Teltonika 3-5x Concox, but with 5-10x more I/O channels and a real OTA management story.

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