Home Apps
Platform
Tracking panel Zones and alerts Reports Mobile app Compatible devices Device catalogue Connects to other systems Developer access Our own maps Every client, separate Backups Service status Where your data lives
Your brand
Your domain and logo Your app in the stores Your website Security padlock and email What you need to start How long it takes Brands already running Your reseller panel
What improvement you offer your client
Road safety Anti-theft and recovery Fuel control Regulatory compliance Preventive maintenance Delivery reliability Working-hours control Cold chain School routes Asset control Onboard video Guard patrols Field work Tracking with no device Satellite coverage Automatic alerts Silent devices Connect to their system
Who to sell it to
Freight transport Passenger transport School transport Delivery and last mile Construction and machinery Agriculture Field services Food and refrigerated Vehicle rental Security and guarding
Pricing
How billing works Volume plans What's included Your margin Payment methods Annual prepayment
Resources
Your first 30 days Technical support Training Sales material Frequently asked How to start a tracking business What it costs to start Which devices to buy How to bill your client Which protocol your GPS uses What the PESV is The GPS is not reporting Look up an IMEI Is my device supported? Your carrier's APN Look up a list of IMEIs Compare devices How much data the SIM uses When 2G shuts down When do I break even? Quote with your brand
Contact Request Demo

The Teltonika (Codec 8) protocol

The protocol of Teltonika devices, made in Lithuania. It is what you use when you need real vehicle data: fuel use, engine revs, temperature, wired sensors.

It is binary and runs over mobile data. These devices are not configured by SMS but with the manufacturer's tool or remotely, which makes installation tidier but less improvised.

Which port it comes in onOur server listens for the Teltonika (Codec 8) protocol on port 6027. That is the port you set on the device, together with the server address. Point it somewhere else and the data still leaves, but the server cannot read it. In the platform this protocol is listed as teltonika.
Careful with what other sites tell youTeltonika publishes the TAC codes of every model on its wiki. Cross-checking them reveals what nobody mentions: some TACs are shared by seven different models, so the IMEI alone cannot tell you which one you are holding.

Build the configuration command

Type the APN of the SIM you will use and we build the commands exactly as they must be sent to the device by SMS.

Poner APN y servidor de una vez

Los parámetros son 2001 APN, 2004 servidor, 2005 puerto y 2006 protocolo (0 = TCP). OJO: el comando empieza con DOS ESPACIOS. Es el hueco del usuario y la contraseña de SMS, que de fábrica vienen vacíos; si usted les puso valor, van ahí en vez de los espacios.

Comprobar que quedó bien

El equipo responde con lo que tiene guardado en esos tres parámetros.

The server address is deliberately left blank. We give it to you when you sign up, along with the port that corresponds to you.

Verified against: Wiki oficial de Teltonika: FMB SMS/GPRS Commands y lista de parámetros FMC130

Devices that use it

TeltonikaSee this brand's devices

Receive this protocol on your own platform

No server to set up and nothing to program: the platform already reads this protocol. You add the brand and the domain.

See how becoming a distributor works

Back to the lookup

IMEI lookupDevice identification tool. We do not perform unlocking, carrier release or mobile blacklist checks, and we are not affiliated with the GSMA.

Where the data comes fromPublic mobile TAC database (MIT licence, Copyright (c) 2026 Moaz Ebrahem), TAC codes published by Teltonika on its official wiki, and the protocol observed on devices connected to the Appogio platform. We publish no full IMEI and no customer data.

Frequently asked questions

What is Teltonika's Codec 8?

It is the way Teltonika devices package what they send. It is used when you need real vehicle data, not just position, which is why it is the protocol you find in professional fleets.

Can it read the vehicle's computer?

That is exactly its ground. That is the difference from the budget-range protocols: it does not just send where the vehicle is, but what the vehicle itself is reporting.

I have several different Teltonika models — do they all speak the same?

In essence yes, which is why they are registered the same way. What changes between part numbers is the network generation — 2G, 4G and NB-IoT live side by side — and which inputs each one carries, so confirm the exact part number before promising a customer sensors.