Astra Telematics Protocol · AT-series port, configurator
15 devices 1 brands Port 5103 (Traxelio / Traccar default) TCP (UDP variant for legacy AT100)

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.

Start Tracking Browse 15 supported devices

2 min read · ~339 words

Quick answers

Is Astra Telematics a Lithuanian company like Teltonika?

No · Astra is UK-based (Hampshire), founded 1999. Both companies serve the European fleet market but they're separate manufacturers with separate protocols. Astra is smaller and more vertical-focused (insurance telematics, lone-worker safety, valuable-asset tracking) than the broader fleet generalist Teltonika.

What port does the Astra protocol use?

Traxelio's ingest port is 5103 (TCP, matches Traccar's default). Astra's reference is operator-configurable · the configurator sets whichever port the server expects.

Is the Astra protocol open?

It is documented to integrators under NDA · not publicly published like Teltonika Codec 8 or Wialon IPS. That said, Traccar's open-source Astra decoder is the most widely-used reference implementation and proves the protocol can be third-party-decoded. Traxelio uses the same decode path.

Which Astra models work with Traxelio?

The full AT series · AT100 (legacy entry), AT110 (compact vehicle), AT220 (motorcycle / lone-worker), AT240 (vehicle + sensor), AT500 (premium fleet). 15+ models in our catalog declare protocol: "astra". Other Astra OEM builds typically also work · check the device datasheet for 'Astra protocol' or 'AT-series protocol' compatibility.

Can Astra devices use a dual-server setup?

On current firmware, yes · the configurator supports a primary and secondary server endpoint. Useful during migration · run dual-stream for a week to validate Traxelio's decoding matches your previous platform, then cancel.

Astra Telematics has been designing GPS hardware in the UK since 1999. The Astra protocol (sometimes called the AT-series protocol or Astra binary protocol) is the wire format the AT100 / AT110 / AT220 / AT240 / AT500 families use. It is proprietary · documented to integrators under NDA · but third-party servers including Traxelio and Traccar decode it via well-established open-source implementations.

Protocol-at-a-glance

  • Transport · TCP (UDP variant exists for legacy AT100 deployments)
  • Default port · 5103 (Traxelio's ingest port; matches the Traccar default)
  • Encoding · binary, length-prefixed records, mixed ASCII for headers
  • Auth · IMEI handshake in first packet
  • Ports of origin · designed for European fleets · Tier-2 hardware between budget Concox/Coban and pro Teltonika/Ruptela

Why Astra Telematics is its own ecosystem

  • UK-designed, UK-supported · the company operates from Hampshire with direct integrator relationships, rather than the Shenzhen reseller model
  • AT-series consistency · the AT100 through AT500 progression keeps protocol backward-compatibility so a mixed fleet of old + new hardware speaks the same wire format
  • Insurance / lone-worker / asset-tag focus · much of the Astra catalog targets specific verticals (insurance telematics, lone-worker safety, valuable-asset tracking) rather than generic fleet
  • Smaller footprint · 15 catalog models on Traxelio (vs 99 GT06 and 91 H02) · but each model has a clearer use-case

Configuring an Astra device for Traxelio

Astra devices ship with the Astra Configurator (Windows desktop tool, distributed via Astra's support portal). The configurator path:

  1. Download Astra Configurator from astratelematics.com (integrator login required)
  2. Connect the device via USB
  3. Set Server Address to Traxelio's ingest endpoint
  4. Set Port to 5103
  5. Set Transport to TCP (UDP fallback only if your network has CGNAT issues)
  6. Save and reboot
  7. First position usually arrives within a minute

For deployed fleets where physical access to each device is impractical, Astra also supports SMS-based reconfiguration · the command syntax is documented in the model's deployment manual.

Supported devices in our catalog

15+ devices declare protocol: "astra" · the headline models: Astra AT100, AT110, AT220, AT240, AT500. The AT series is the headline product line · other Astra models (older AT2X, custom OEM builds) typically also speak the same protocol.

Setup walkthrough

  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. First position arrives within a minute.

  6. 6

    Don't have an Astra-compatible server yet?

    Traxelio decodes the Astra protocol natively on port 5103 · point the configurator at the Traxelio endpoint and the first position lands within a minute. Or self-host Traccar · same Astra decoder, same port.

Reference

Configuration reference

Parameter Value
Transport TCP (UDP variant for legacy AT100)
Default port 5103 (Traxelio / Traccar default)
Encoding binary, length-prefixed, mixed ASCII headers
Authentication IMEI handshake in first packet
Configurator Astra Configurator (Windows, integrator login required)
Vendor portal www.astratelematics.com/

Or skip the integration

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

Traxelio processes all telemetry data sent by Astra 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 Astra Devices (15)

Astra Telematics AT Series

Astra

AT-110

Astra

AT-111

Astra

AT-200

Astra

AT-202

Astra

AT-210

Astra

AT-211

Astra

AT-240

Astra

AT-241

Astra

AT-242

Astra

AT-300

Astra

AT-400

Astra
Show 3 more Astra devices

AT-402

Astra

AT-406

Astra

AT-500

Astra

Compatible Brands

Brands Using Astra Protocol

Astra

15 devices

Common troubleshooting

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.

Lone-worker AT220 button press sent but no event arrives at Traxelio

The lone-worker button is wired as a digital input in the device configuration · confirm the input is enabled and mapped to the correct event ID. Astra firmware sometimes ships with the input disabled by default. Use the Astra Configurator's input mapping section to enable and assign.

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.

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

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.

Does Astra hardware support CAN bus reporting?

Limited · the AT240 and AT500 expose RS232 / RS485 interfaces that can read external CAN-bus interpreters, but Astra hardware doesn't have native CAN decoding the way Teltonika or Ruptela does. For deep CAN integration, pick Teltonika Codec 8 or Ruptela; for the verticals Astra targets, CAN depth is rarely the requirement.

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.

Does Astra still ship 2G hardware?

Legacy AT100 and AT110 models had 2G/3G modems. Current production (AT220 / AT240 / AT500) is LTE Cat-M1 / Cat-1 with 2G fallback only. The 2G sunset in the UK is forcing the catalog upward · check the model's connectivity datasheet before specifying for a long-term deployment.

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