Ruptela Protocol · port, CAN bus, switch from TrustTrack
11 devices 1 brands Port 5046 (Traxelio) · vendor-configurable TCP (canonical) · UDP variant available

Ruptela Protocol

TCP protocol published by Ruptela (Vilnius, Lithuania) for its Trace5, FM-Eco4, and Plug-and-Track families · the format Ruptela hardware uses to push positions, CAN bus data, and sensors to a fleet server.

Talk to integration team Browse 11 supported devices Read the spec

2 min read · ~364 words

Quick answers

Is the Ruptela protocol open or proprietary?

Documented to integrators. Ruptela publishes the spec via its developer documentation portal (doc.ruptela.lt). Any server with access to the spec can decode the same stream Ruptela's TrustTrack platform decodes. That is why Traxelio, Flespi, and Traccar all support it.

What port does the Ruptela protocol use?

Configurable on the device side. Traxelio's ingest port is 5046 (TCP, matches the Traccar default). Other operators use 27200, 5009, or vendor-assigned ports. The configurator sets whichever the server expects.

Can I switch from TrustTrack without replacing my Ruptela devices?

Yes. Open the Ruptela Configurator, set the server IP and port, save to device. The same Trace5 (HCV5/LCV5/Pro5) or FM-Eco4 device that reports to TrustTrack will report to Traxelio. CAN-bus calibration stays on the device, IMEI stays the same.

Does Traxelio decode the full Ruptela CAN bus profile?

Yes. Ruptela's 256-channel CAN decoder streams FMS standard fields (fuel level, total fuel used, odometer, engine hours, axle weight, gear position) to Traxelio. RS232 and RS485 fuel and temperature sensors are also accepted.

Is Ruptela the same as Teltonika?

No. Both are Vilnius-based Lithuanian manufacturers but separate companies with different protocols. Ruptela leans into heavy CAN and FMS; Teltonika leans into broader I/O and Codec 8 / Codec 8 Extended. Both supported by Traxelio.

The Ruptela protocol (sometimes called Ruptela FMTPv1 · "FM Telematics Protocol v1") is the device-to-server binary format Ruptela GPS trackers use to report data. Ruptela publishes the spec to integrators, which is why third-party servers (Traccar, Flespi, Traxelio) can decode it without needing Ruptela's own TrustTrack platform.

Protocol-at-a-glance

  • Transport · TCP (UDP variant exists but TCP is canonical for online fleets)
  • Default port · 5046 (Traxelio's ingest port; configurable on the device side)
  • Encoding · binary AVL records, length-prefixed packets, big-endian
  • Auth · IMEI handshake in the first packet; server acknowledges with 0x01
  • Compression · supports buffered "extended" records when GPRS reconnects after offline gaps

Why Ruptela hardware ships this protocol

Ruptela's value proposition is deep CAN-bus decoding. The protocol carries:

  • Standard FMS fields (fuel level, total fuel used, odometer, engine hours, axle weight, gear position)
  • OBD-II PIDs (RPM, throttle, MAF, coolant temp)
  • RS232 and RS485 sensor channels (third-party fuel sensors, temperature probes, driver-ID iButton readers)
  • Accelerometer + gyroscope events (hard braking, harsh cornering, idle detection)
  • Custom digital and analog I/O channels (panic button, ignition cut relay, door open/close)

The 256-channel CAN decoder is the headline feature · most fleet protocols carry 10-20 standard channels and call it a day.

Switching from TrustTrack to Traxelio (no hardware swap)

If your fleet is on TrustTrack (Ruptela's own platform) and you want to move to Traxelio:

  1. Open Ruptela Configurator (Windows desktop tool, free from Ruptela's documentation portal)
  2. Connect the device via USB or read over-the-air
  3. Set the server endpoint: Traxelio's IP + port 5046
  4. Save and reboot
  5. Confirm the first decoded position in your Traxelio dashboard
  6. Cancel TrustTrack at next renewal (do one truck first to validate, then batch the rest)

No re-install, no re-wiring, no IMEI change. The CAN-bus calibration you already did on TrustTrack stays on the device.

Supported Ruptela hardware

Common models speaking this protocol:

  • Trace5 series · HCV5 (heavy commercial), LCV5 (light commercial), Smart5 (entry fleet), Pro5 (advanced I/O), Plug5 (OBD-II plug-and-track)
  • FM-Eco4 legacy series · FM-Eco4, FM-Pro4, FM-Tco4 (2G/3G workhorses being phased out behind 2G sunsets)
  • FM3001 and other current-gen Trace family

Any Ruptela device that lists "FMTPv1" or "Ruptela protocol" in its datasheet speaks this format.

Setup walkthrough

  1. 1

    Download Ruptela Configurator

    Free Windows desktop tool from doc.ruptela.lt. Works with any Ruptela-compatible server, not just TrustTrack. Trace5 + later firmware also accepts over-the-air configuration.

  2. 2

    Connect the device via USB or read OTA

    USB connection for initial setup. For deployed fleets already reporting to a server, the configurator can read the device over GPRS.

  3. 3

    Set the server endpoint

    In the configurator's Server tab, set your platform's IP and port. Ruptela's default port is 5046 but the device side is configurable · match your server's listener. Transport: TCP.

  4. 4

    Save and reboot

    Click Save · the device reboots and reconnects. Confirm the first decoded position in Traxelio. CAN-bus calibration stays on the device through any server change.

  5. 5

    Validate before cancelling the old server

    Run one truck on the new server for a week to confirm positions + CAN data match what the previous platform showed. Then batch the rest of the fleet.

  6. 6

    Don't have a Ruptela-compatible server yet?

    Traxelio decodes the Ruptela protocol natively on port 5046. Point the configurator at Traxelio's endpoint and the first decoded position can be verified in Traxelio · CAN bus, RS232/485 sensors, the full Trace5 channel set. Or self-host Traccar / Flespi · they decode it too.

Reference

Configuration reference

Parameter Value
Transport TCP (canonical) · UDP variant available
Default port 5046 (Traxelio) · vendor-configurable
Encoding binary AVL, length-prefixed, big-endian
Authentication IMEI handshake in first packet, server acks 0x01
Extended records supported · buffered offline writes drain on reconnect
Configurator Ruptela Configurator (Windows, free from doc.ruptela.lt)
Spec portal doc.ruptela.lt/
Alternative reference flespi.com/protocols/ruptela

Or skip the integration

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

Traxelio processes all telemetry data sent by Ruptela 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 Ruptela Devices

Featured

HCV5

Ruptela
Featured

Smart5

Ruptela

All Models

Representative Ruptela Devices (11)

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

FM-ECO 4

Ruptela

FM-Eco3

Ruptela

FM-Pro3

Ruptela

FM-Pro3-R

Ruptela

FM-Tco3

Ruptela

LCV5

Ruptela

Plug5

Ruptela

Pro5

Ruptela

Trailer Tracker

Ruptela

Compatible Brands

Brands Using Ruptela Protocol

Ruptela

11 devices

Common troubleshooting

Device reports to TrustTrack but stays silent after configurator change

Verify the configurator wrote the new server IP back to the device (Read configuration after Save to confirm). Power-cycle the tracker. If still silent, check the device's raw GPRS log for outbound TCP attempts · no attempts means SIM data session isn't active (APN, airtime, roaming block).

Positions arrive but CAN bus channels are empty

CAN decoding is profile-driven · the device needs the right CAN profile loaded for the vehicle make/model (Mercedes Actros vs Volvo FH vs DAF XF use different FMS profiles). Use Ruptela Configurator's CAN profile selector or contact Ruptela support for the model code.

Plug5 OBD-II tracker shows engine on/off correctly but no fuel level

OBD-II fuel level PID (0x2F) is optional · many European light vehicles do not expose it via the OBD-II port. For accurate fuel level on those vehicles, install an external capacitive or ultrasonic fuel sensor on RS232/RS485 rather than relying on OBD-II.

Explore More

Other Protocols

GT06

99 devices

H02

96 devices

Teltonika

84 devices

Meiligao

59 devices

GL200

36 devices

Huabao

32 devices
View All Trackers

FAQ

Frequently Asked Questions

What's the difference between Ruptela's protocol and TrustTrack?

Ruptela protocol = the wire format devices speak. TrustTrack = Ruptela's own fleet platform (the dashboard, mobile app, reports, alerts). Devices speak the protocol; servers (TrustTrack, Traxelio, Flespi, Traccar) decode it. Same device, multiple possible servers.

Is Ruptela FMTPv2 supported by Traxelio?

FMTPv1 (the current production protocol) is fully supported. FMTPv2 is a Ruptela-internal evolution not yet widely deployed in customer hardware as of 2026. When v2 ships to production fleets, Traxelio's ingest will be extended to decode it. Existing v1 devices keep working untouched.

Does Ruptela have a Lithuanian-only restriction?

No. Ruptela hardware is sold worldwide (150 countries per Ruptela's own marketing). The protocol itself is country-agnostic. In Senegal and West Africa, Ruptela devices route through European resellers · Traxelio sources authentic units and installs in Dakar (Ouest Foire).

Can Ruptela devices use a dual-server setup (TrustTrack + Traxelio simultaneously)?

Yes, on most current Ruptela firmware. The configurator allows two server endpoints; the device pushes the same record to both. Useful when migrating · run dual-stream for a week to validate Traxelio's decoding matches TrustTrack's, then cancel TrustTrack.

Why is Ruptela hardware more expensive than Concox or Coban?

Different segments. Ruptela targets professional fleet operators where CAN bus depth, install quality, and 24-month warranty matter more than per-unit cost. Concox and Coban target the budget end (consumer self-install, small fleets, light data needs). Both are valid · pick by what your fleet actually needs.

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