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 Flespi protocol

Flespi is neither a device nor a manufacturer: it is a <strong>bridge</strong> that receives devices speaking many different protocols and forwards them to whatever platform you choose. It is used when very disparate brands have to be brought together.

The device reports to Flespi and Flespi forwards. In practice, for the installer it is just another server address.

Which port it comes in onOur server listens for the Flespi protocol on port 6149. 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 youPutting a bridge between device and platform <strong>adds a point of failure and somebody else to pay</strong>. If the device's protocol is already handled directly, the bridge is unnecessary: connect it straight.

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

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

Is Flespi a device?

No, it is a bridge: it receives devices speaking many protocols and forwards them to whatever platform you pick.

Should I use it?

Only if you need to bring very disparate brands together. If the device's protocol is already handled directly, the bridge is unnecessary: it adds a point of failure and somebody else to pay.

Does it change anything for the installer?

No. In practice it is just another server address.