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 FMB/FMC protocol

Teltonika's second protocol family, covering the more recent series: FMB964, FMC003, FMC920. It coexists with the Codec 8 family, which has its own page.

Like its sibling, it is built to read <strong>real vehicle data</strong> rather than just position: this is professional fleet ground.

Which port it comes in onOur server listens for the Teltonika FMB/FMC protocol on port 7028. 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.
Careful with what other sites tell youTwo things that change between part numbers of the same brand and cost money if assumed: <strong>the network generation</strong> — 2G, 4G and NB-IoT live side by side — and <strong>which inputs each model carries</strong>. Confirm the exact part number before promising a customer sensors.

Build the configuration command

We do not have this protocol's commands yetWe would rather tell you than make them up. We only publish the ones we have checked against the manufacturer's manual or against a real device. If you have them confirmed, send them to us and we will add them.
Send us the commands

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

How does it differ from Teltonika's Codec 8?

They are two protocol families from the same brand. This one covers the more recent series — FMB964, FMC003, FMC920 — the other the earlier ones.

Are all Teltonikas registered the same way?

In essence yes, but confirm the exact part number: what changes between models is the network generation and which inputs each one carries.

Can it read the vehicle's computer?

That is its ground. It is why Teltonika turns up wherever real vehicle data is needed rather than just position.