Radshid Protocol

Binary Radshid dialect on Traccar TCP 5265 without an ASCII delimiter cheat-sheet in the open decoder.

Connect your tracker

Enter the tracker IMEI first, then verify your email and continue setup.

Quick answers

Port?

TCP 5265.

ASCII markers?

None relied upon in the open decoder.

Commands?

None on RadshidProtocol.

Like Sigfox HTTP?

No — Sigfox is HTTP JSON on 5154.

Twin binary?

ThinkPower 5228 is separate.

Radshid sits on a high Traccar TCP port — 5265 — as a binary dialect (RadshidProtocolDecoder). There is no friendly ) or BSTPL$ marker to grep in a text editor; identification is port + binary accept logs + vendor sheet.

ThinkPower is not a shortcut

ThinkPower binary on 5228 is a different decoder. Copy-pasting ThinkPower firewall rules onto 5265 still leaves the wrong grammar if the device is Radshid.

Setup walkthrough

  1. 1

    Match vendor string 'Radshid' + Traccar port 5265

    Reject vague 'binary GPS' labels.

  2. 2

    APN up

    Binary units still need PDP context.

  3. 3

    Host:5265

    Reboot into binary frames.

  4. 4

    Capture hex

    Text greps will lie.

  5. 5

    Compare against ThinkPower samples

    Different accept paths — keep evidence separate.

Reference

Configuration reference

Parameter Value
Port 5265

Telemetry fields

GPS Location Speed Altitude Heading / Direction Street Address GPS Accuracy Ignition Status Odometer / Mileage Battery Level

Common troubleshooting

Text console shows noise

Expected for binary — use hex.

Works on ThinkPower port only

Firmware actually ThinkPower — retarget intake.

Firewall open, still silent

APN or host still vendor-cloud.

FAQ

Frequently Asked Questions

Why so little public prose historically?

Long-tail binary with thin marketing docs — this page exists to pin port 5265.

UDP?

Stock Radshid is TCP.

T
Trax
Online
Say hello to Trax!