15 devices 1 brand

Astra Telematics Protocol

Proprietary TCP protocol published by Astra Telematics (Hampshire, UK) for the AT100, AT110, AT220, AT240, AT500 vehicle and asset tracker families · the format Astra hardware uses to push positions, sensor channels, and events to a fleet server.

Positions go to this server

gps.traxelio.com:5103 TCP
I already have a tracker

Connect your tracker

Enter your tracker IMEI to see whether Traxelio recognizes the model before you start setup.

Hardware that speaks this protocol

Devices that speak Astra

Point this protocol at Traxelio

Point Astra at Traxelio

  1. 1

    Get integrator access to Astra Configurator

    Astra requires an integrator login to download the configurator from astratelematics.com. Contact Astra support (UK) or your reseller to request credentials.

  2. 2

    Connect the device via USB

    Astra AT-series devices use a standard USB serial connection. Driver typically auto-installs on Windows 10+; Linux may need a /dev/ttyUSB0 permissions fix.

  3. 3

    Set the server endpoint

    Server Address: your platform's host · Port: your platform's listener (Traccar default for Astra is 5103) · Transport: TCP (use UDP only if your carrier has CGNAT issues breaking long-lived TCP).

  4. 4

    Calibrate accelerometer + I/O mappings

    If using lone-worker (AT220) or driver-behavior features, run the configurator's accelerometer calibration wizard. Enable digital inputs in the I/O section if you're wiring panic buttons or ignition-cut relays.

  5. 5

    Save and reboot

    Save to Device, power-cycle. Confirm the first decoded position in Traxelio.

Still offline after GPS lock

Astra still not landing

Device behind CGNAT or symmetric NAT fails to maintain TCP

Some mobile carriers' CGNAT setups break long-lived TCP connections from low-throughput devices. Two paths: (1) switch the device to UDP variant via the configurator (if the model supports it · check datasheet); (2) reduce the keep-alive interval so connection refresh happens before the carrier expires the NAT entry.

Position records arrive but accelerometer / driver-behavior events don't

Accelerometer event thresholds (hard braking, harsh cornering, idle) need to be enabled and calibrated per-device-orientation · the Astra Configurator has a calibration wizard that asks you to point the device's X-axis forward. Without calibration the device sees noise as events or misses real events.

These symptoms are answered outside this section:

FAQ

Astra leftover questions

Why is Astra Telematics less well-known than Teltonika or Ruptela?

Smaller company, vertical focus. Astra has been profitable in specific niches (insurance telematics, lone-worker safety, asset tracking) for two decades without trying to be a fleet generalist. The result is less SEO presence and a smaller integrator community than Teltonika's, but the hardware quality and UK support model are respected in the verticals Astra targets.

Are there OEM rebrands of Astra hardware?

Less common than the Concox or Coban ecosystems. Astra typically sells under its own brand; the rebrand-as-a-service model isn't a major part of its business. If you see an unusual 'AT-XXX' branded device in the wild, it's most likely actual Astra hardware.

What's the AT500 used for?

Premium fleet · larger battery, more I/O, broader cellular band support, intended for long-life trailer-tag and high-value-asset deployments. Sits at the top of the AT-series progression. The protocol is the same as the AT100 family · the difference is hardware capacity, not wire format.

T
Trax
Online
Say hello to Trax!