Wialon IPS Protocol · port, packets, supported devices
4 devices 3 brands Port 20332 TCP (UDP variant exists but TCP is canonical)

Wialon IPS Protocol

TCP/UDP wire protocol published by Gurtam · the format most GPS trackers use to push positions, sensors, and events to a Wialon-compatible server (Wialon Hosting, Wialon Local, or Traxelio).

Start Tracking Browse 4 supported devices Read the spec

3 min read · ~420 words

Quick answers

Is Wialon the same as Wialon IPS?

No. Wialon is Gurtam's fleet-tracking SaaS platform (Wialon Hosting / Wialon Local). Wialon IPS is the device-to-server wire protocol Wialon uses. A device speaks Wialon IPS; the platform decodes it. Any other server that implements the spec (including Traxelio) can decode the same stream.

What port does Wialon IPS use?

Wialon IPS is port-flexible by design. Gurtam's reference port is 20332 (TCP). The tracker configurator lets the operator set any port; the server just has to listen on it.

Can I switch from Wialon Hosting to Traxelio without replacing my trackers?

Yes. If your trackers speak Wialon IPS (most modern Teltonika, Concox, Queclink, Galileosky and many others do), point them at Traxelio's Wialon-IPS ingestor via the configurator. The IMEI, SIM, and hardware stay the same · only the destination IP changes.

Is the Wialon IPS spec open?

Yes. Gurtam publishes the spec publicly under GNU FDL. The PDF is at extapi.wialon.com/hw/cfg/. That is why so many third-party servers (Traccar, Flespi, Traxelio) can decode the same stream.

What's the difference between Wialon IPS and Wialon Retranslator?

Wialon IPS is the device-to-server protocol (a tracker speaks it). Wialon Retranslator is a server-to-server forwarding format (a Wialon server speaks it to a downstream server). Different layers · IPS sits between hardware and platform; Retranslator sits between platforms.

Wialon IPS is the device-to-server protocol Gurtam published for the Wialon fleet-tracking platform. It is supported by hundreds of GPS tracker models out of the box and remains one of the most-used open wire protocols in fleet telematics. The spec is freely available and licensed under GNU FDL, so any server (not just Wialon) can decode it · Traxelio implements Wialon IPS as a first-class ingest path.

The three Wialons (disambiguation)

People typing "Wialon" into search are usually looking for one of three different things:

Name What it is Where it lives
Wialon Hosting / Wialon Local The SaaS fleet-tracking platform built by Gurtam (Vilnius, Lithuania). The competing product to Traxelio. See our Traxelio vs Wialon comparison
Wialon IPS The device-to-server wire protocol. Open spec. Devices speak it; servers decode it. This page
Wialon Retranslator A server-to-server forwarding protocol. Wialon (or another server speaking the format) re-broadcasts position records to a downstream server. Section below

Message types

Wialon IPS is a simple text-based TCP protocol. Each message begins with a hashtag-wrapped identifier:

  • #L# · Login (authentication, IMEI handshake)
  • #P# · Ping (keep-alive)
  • #SD# · Shortened position data
  • #D# · Full position data with sensor channels
  • #B# · Black-box (batched offline positions when GPRS reconnects)
  • #M# · Free-form message (driver text, alerts)
  • #I# · Image upload (photo, dashcam frame)
  • #AD# · Server acknowledgement
  • #ANS# · Server response with payload

The protocol supports any TCP port; Gurtam's reference port is 20332. Devices configure the destination via SMS or USB configurator commands.

Wialon Retranslator

The Retranslator is a separate, server-side format Wialon uses to forward already-decoded position records from one server to another. It is not what a tracker speaks · it is what a Wialon-compatible server speaks to a downstream system (insurance dashboards, government compliance servers, third-party analytics).

If your fleet currently reports to Wialon Hosting and you want a parallel Traxelio account without re-pointing the devices, the Retranslator path lets Wialon push a copy of your data to Traxelio. Devices keep their existing config; the dual-stream happens server-side.

Using Wialon IPS with Traxelio

If your tracker speaks Wialon IPS:

  1. Open your device configurator (Wialon's universal tool or your vendor's SMS command set)
  2. Set the server IP to Traxelio's Wialon-IPS ingest endpoint
  3. Set the port (we accept the spec's flexible port range; default 20332)
  4. Save and reboot the device
  5. First position usually arrives within a minute · confirm in your Traxelio dashboard

The IMEI stays the same. The SIM card stays the same. Only the destination server changes. No hardware swap, no re-install.

Setup walkthrough

  1. 1

    Identify your device's current server

    Open your tracker's existing configurator (or check the SMS-command sheet for the model). Note the current server IP + port so you can roll back if anything goes wrong.

  2. 2

    Point the device at your Wialon-IPS server

    Set the destination to your platform's IP and port. Gurtam's reference port is 20332 but Wialon IPS is port-flexible · use whatever your server listens on. Transport: TCP. The IMEI and SIM stay the same.

  3. 3

    Save and reboot the device

    Most Wialon-IPS-compatible firmware applies the new server on the next boot. Some devices accept a remote #REBOOT# command if you can't physically access the unit.

  4. 4

    Confirm first position arrives

    First position usually arrives within a minute of GPS lock. If nothing arrives in 5 min, check the device's raw log for outbound TCP attempts on the port · no attempts means the SIM's data session isn't open (APN, airtime, roaming block).

  5. 5

    Don't have a Wialon-IPS server yet?

    Traxelio decodes Wialon IPS natively on port 20332 · point your device at the Traxelio endpoint and the first position lands within a minute. Or self-host any Wialon-IPS-compatible server (Traccar, Flespi) · the protocol's the same.

Reference

Configuration reference

Parameter Value
Transport TCP (UDP variant exists but TCP is canonical)
Default port 20332
Encoding ASCII text, hash-wrapped message identifiers (#L#, #P#, #SD#, #D#, #B#, #M#, #I#)
Authentication Login packet (#L#) carries IMEI; server returns #AL#1 on accept
Spec PDF extapi.wialon.com/hw/cfg/Wialon%20IPS_en_v_2_0.pdf
License GNU FDL (open spec)

Or skip the integration

Traxelio decodes Wialon natively

Point your device at our endpoint, first position lands in under a minute. We handle the protocol, ack the packets, and serve the dashboards.

Start free Talk to integrators

Protocol Capabilities

Data Points from Wialon Devices

Traxelio processes all telemetry data sent by Wialon trackers for comprehensive fleet insights.

Core Tracking

  • GPS Location
  • Speed
  • Altitude
  • Heading / Direction
  • Street Address
  • GPS Accuracy

Engine & Driving

  • Ignition Status
  • Odometer / Mileage

Sensors

  • Battery Level

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.

All Models

All Wialon Devices (4)

Eskort TD-Online

Eskort

MasterKit

MasterKit

MasterKit BM8009

MasterKit

NeoTech TR_1000

NeoTech

Compatible Brands

Brands Using Wialon Protocol

MasterKit

2 devices

Eskort

1 devices

NeoTech

1 devices

Common troubleshooting

Device reports to Wialon Hosting but not to Traxelio after configurator change

Verify the server IP and port were actually written back to the device (some configurators silently keep a draft). Power-cycle the tracker, then check its raw log for an outbound TCP attempt on the new IP. If the attempt never leaves the device, the SIM probably has no data session · check airtime + APN before assuming a protocol issue.

Wialon IPS device shows positions but no fuel/temperature sensor data

Sensor channels ride in the #D# (full data) packets, not #SD# (shortened). Some devices default to #SD# to save GPRS bytes. Re-enable full data in the configurator (Teltonika: Codec settings; Concox: extended mode; Queclink: AT+GTCFG sensor opcodes).

Retranslator delivers stale data (~minutes behind real-time)

Expected. Retranslator is a server-to-server feed · it ships after the source platform has decoded, persisted, and queued the record. For real-time, point the device directly at Traxelio over Wialon IPS (cuts out the source platform's queue).

Explore More

Other Protocols

GT06

99 devices

H02

91 devices

Teltonika

84 devices

Meiligao

59 devices

GL200

36 devices

GPS103

31 devices
View All Trackers

FAQ

Frequently Asked Questions

What trackers speak Wialon IPS out of the box?

Hundreds of models. The biggest families: Teltonika (FMB/FMC/FMM series via Codec 8 or native Wialon IPS firmware), Concox / Jimi (with the right firmware build), Queclink (selected GV models), Galileosky (most models), Navtelecom, BCE. Any device whose datasheet lists "Wialon IPS" or "Wialon Hosting compatible" speaks the protocol.

Does Traxelio support Wialon Retranslator inbound?

Yes for new deployments by request. If your fleet is currently on Wialon Hosting and you want Traxelio as a parallel view without re-pointing devices, contact us · we add the Retranslator ingest endpoint and Wialon pushes a mirror stream. The Retranslator config lives on the source server (Wialon), not on each device.

What's the difference between Wialon IPS and Teltonika's Codec 8?

Different protocols, both well-known. Codec 8 is Teltonika's proprietary binary protocol. Wialon IPS is Gurtam's text-based open protocol. Many Teltonika devices can be configured to send EITHER (or both in dual-server mode). If your operator-of-record is Wialon Hosting, the device likely speaks Wialon IPS; if it is FOTA Web (Teltonika's platform), it likely speaks Codec 8.

Is the Wialon IPS port the same as the Wialon platform login port?

No. 20332 (Wialon IPS device port) is unrelated to the HTTPS / web port (443) that operators use to log in to Wialon Hosting. The 20332 connection is hardware-to-server only; the 443 connection is human-to-server.

How do I know if my device is actually speaking Wialon IPS vs another protocol?

Check the configurator's protocol selector (most devices expose this explicitly). If the option isn't visible, capture a raw TCP dump on the server side · Wialon IPS packets start with # (hash) and end with \r\n. If you see 0x78 0x78 headers, it's GT06. If you see *HQ, prefixes, it's H02. If you see binary AVL records, it's likely Codec 8.

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