Queclink @track Protocol · GL200, GV-series, port, configurator
0 devices 0 brands Port 5004 (Traxelio / Traccar gl200) · configurable TCP (UDP variant on asset-tag models)

Queclink @track Protocol

ASCII TCP protocol published by Queclink (Shanghai, listed on Shanghai Stock Exchange) for the GL200, GL300, GV-series, GMT100, and GB100 device families · the format Queclink hardware uses to push positions, sensor channels, and events to a fleet server.

Start Tracking

3 min read · ~530 words

Quick answers

Is @track the same as Queclink protocol?

Yes · same thing under two names. @track is Queclink's canonical spec name (always written with the at-sign prefix). 'Queclink protocol' is the informal name operators use. Traccar's slug for the same protocol is gl200. All three refer to the ASCII TCP wire format Queclink GL / GV / GMT / GB devices speak.

What port does the Queclink @track protocol use?

Traxelio's ingest port is 5004 (TCP, matches Traccar's gl200 decoder default). Queclink's reference is operator-configurable via the GL200 Manage Tool or SMS commands · the AT+GTSRI command sets whichever port the server expects.

What does a Queclink @track position record look like?

Plain ASCII, bracketed by +RESP: and $: +RESP:GTFRI,310601,860861054295928,GL300VC,...,2.292889,48.858889,20260531180000,...,30A3$. The packet type after +RESP: (GTFRI for position, GTPNA for power-on, GTBAA for SOS button, etc.) tells the decoder what to extract. Human-readable in a raw TCP dump.

What's the GL200 Manage Tool?

Windows desktop configurator Queclink ships free with the GL200 hardware (and re-used across the GV / GMT / GB families · it predates them all). It connects via USB to read / write device configuration: server endpoint, GPRS reporting rules, geofence definitions, I/O mappings. Most integrators use it for initial setup, then SMS for ongoing changes.

Does Queclink hardware support CAN bus?

Yes on the GV-series (GV600M, GV300W, GB100 heavy-vehicle). CAN data rides as additional fields in the @track packet. The CAN profile must be loaded per vehicle make/model via the Manage Tool's CAN section. For pure CAN-bus depth the comparison is Teltonika Codec 8 or Ruptela; Queclink's CAN coverage is competitive for the GV-series tier.

The Queclink @track protocol (officially called "@track" with the at-sign · the documentation calls it "@track communication protocol") is the ASCII wire format Queclink GPS trackers use to report data. Queclink ships hundreds of device models worldwide under the GL / GV / GMT / GB prefixes and they all speak @track. The spec is published in full to Queclink's integrator community and Traccar's open-source decoder is the most-cited reference implementation.

Protocol-at-a-glance

  • Transport · TCP (UDP variant for asset-tag low-power models)
  • Default port · 5004 (Traxelio's ingest port; matches Traccar's gl200 decoder default)
  • Encoding · ASCII text, comma-separated fields, message bracketed by +RESP: (device reply) or +BUFF: (offline buffer drain) or +ACK: (server-acknowledged events)
  • Auth · IMEI handshake in first packet, no separate login round-trip
  • Spec name · @track (with the at-sign · always written with the prefix in Queclink docs)

Packet structure

A typical position record from a GL300 device:

+RESP:GTFRI,310601,860861054295928,GL300VC,gv55lite,11,1,1,0.0,0,153.6,2.292889,48.858889,20260531180000,0208,0001,4ec8,9b9c,00,11.4,,,,100,210100,,,,20260531180000,30A3$

Fields (in order): packet type (+RESP:GTFRI = friendly position record) · protocol version · IMEI · device model · device name · counter · counter · GPS-fix-quality · speed · course · altitude · longitude · latitude · UTC time · MCC · MNC · LAC · CellID · reserved · battery voltage · ... · checksum.

The trailing $ is the end-of-message marker · everything between the + prefix and $ is one record.

Why Queclink @track is widely adopted

  • Public-listed company · Queclink is on the Shanghai Stock Exchange · gives integrators long-term supplier stability
  • OBD / asset-tag / fleet breadth · the GV-series covers professional fleet (GV600M / GV300W with CAN), the GL-series covers entry fleet (GL200 / GL300), the GMT-series covers asset tags, the GB-series covers heavy-vehicle CAN
  • Software ecosystem · Queclink ships the GL200 Manage Tool (Windows configurator), TrackPro (web platform), and an OEM API · integrators don't have to start from scratch
  • Tier-2 pricing · between budget Concox/Coban and pro Teltonika/Ruptela · ~$40-$80 for mid-range fleet units

Configuring a Queclink device for Traxelio

Two paths · GL200 Manage Tool (Windows desktop) or SMS commands:

GL200 Manage Tool path (most common):

  1. Download the latest GL200 Manage Tool from Queclink's integrator portal
  2. Connect the device via USB
  3. Open the GPRS section · set Server Address to Traxelio's ingest endpoint
  4. Set Port to 5004, Transport to TCP
  5. Save to device
  6. First position usually arrives within a minute

SMS path (no physical access):

AT+GTSRI=PASSWORD,1,,,traxelio.com,5004,0.0.0.0,0,,,,,,FFFF$
AT+GTRTO=PASSWORD,1,,,,,,FFFF$

(PASSWORD is the device-configured password · default varies by model, often empty or gV55ABCD-style.)

Supported devices in our catalog

36+ devices declare protocol: "gl200" (Traccar's slug for the @track family) · the headline models: Queclink GL200, GL300, GV200, GV300, GV500, GV58LAU, GV58CEU, GMT100 (asset tag), GB100 (heavy-vehicle CAN), GL320MG, CV200.

"GL200" vs "Queclink" vs "@track"

The same protocol has three names in common use:

  • @track · Queclink's own canonical name in their spec PDFs
  • Queclink · the vendor name · informal shorthand for "the protocol Queclink uses"
  • GL200 · Traccar's slug · derives from the GL200 being the first Queclink model the open-source community decoded · now used as the umbrella protocol name across all Queclink hardware

All three refer to the same wire format. Traxelio's TrackerDevice catalog uses gl200 as the protocol slug. Search-engine traffic arrives split across all three names · this page is the canonical landing surface for the protocol family.

Setup walkthrough

  1. 1

    Download the GL200 Manage Tool

    Free Windows tool from Queclink's integrator portal. Universal across the GL / GV / GMT / GB families · the same tool configures every Queclink model, regardless of destination server.

  2. 2

    Connect via USB

    Install the right USB-to-serial driver (CH340 on most older models, FTDI on newer GV-series). Make sure no other application is holding the COM port.

  3. 3

    Set the GPRS section

    Server Address: your platform's host · Port: your platform's listener (Traccar default for Queclink @track is 5004) · Transport: TCP. Save to Device.

  4. 4

    Optional · SMS path for already-deployed fleets

    If you can't get the device on USB: send AT+GTSRI=PASSWORD,1,,,your-server.com,5004,0.0.0.0,0,,,,,,FFFF\$ to the device's SIM phone number. PASSWORD is the device-configured value (often empty on factory units).

  5. 5

    Validate before cancelling the old server

    First position arrives within a minute. If running dual-server (legacy + new), validate that both feeds agree before cutting over.

  6. 6

    Don't have a Queclink @track server yet?

    Traxelio decodes @track natively on port 5004 · point the Manage Tool at the Traxelio endpoint and the first position lands within a minute. Or self-host Traccar · the open-source gl200 decoder handles the full Queclink hardware family.

Reference

Configuration reference

Parameter Value
Transport TCP (UDP variant on asset-tag models)
Default port 5004 (Traxelio / Traccar gl200) · configurable
Encoding ASCII, comma-separated, checksum suffix
Packet envelope +RESP: … $ (response) · +BUFF: … $ (offline buffer drain) · +ACK: … $ (acknowledgement)
Authentication IMEI handshake in first packet, no separate login round-trip
Configurator GL200 Manage Tool (Windows, from Queclink integrator portal)
Vendor platform TrackPro (Queclink's web platform) or any @track-compatible server
Spec name @track communication protocol

Or skip the integration

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

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

All Models

All Queclink Devices (0)

Common troubleshooting

Device positions arrive but +BUFF: drain records are out of order

Expected behavior · the +BUFF: prefix marks records replayed from the device's internal flash after a connectivity gap. Traxelio sorts these by timestamp on ingest, so the dashboard view stays correct even though the wire order is unordered.

GL200 Manage Tool fails to connect via USB

Three things to check: (1) the right USB-to-serial driver is installed (Queclink ships CH340 / FTDI drivers depending on hardware revision); (2) no other application is holding the COM port; (3) the device is powered (some Queclink models need external power even during USB configuration, not just USB power). Restart the Manage Tool after fixing.

GV600M reports CAN data correctly to TrackPro but channels go empty after switching to Traxelio

The CAN profile lives on the device, not on the server · switching servers preserves the CAN profile. If channels go empty, the actual cause is usually a Manage Tool configuration drift during the server-change (some integrators accidentally clear the I/O mappings while editing GPRS settings). Re-load the saved configuration backup.

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

Is the Queclink @track protocol open?

Documented to integrators with NDA-soft access · Queclink publishes the spec PDFs to its integrator portal, and the PDFs circulate freely across the integrator community. Traccar's open-source gl200 decoder is the most-cited reference implementation. Practical effect: third-party servers (Traxelio, Flespi, in-house fleet platforms) decode the protocol as reliably as TrackPro.

Why does Traccar call it `gl200` when the canonical name is @track?

Historical · the GL200 was the first Queclink model the open-source community decoded, so the Traccar slug stuck even as Queclink's hardware expanded across GV / GMT / GB families. Today the slug gl200 covers all Queclink devices speaking the same @track wire format. The slug-to-name disconnect is one of the open-source community's persistent naming quirks.

Can I run dual-server (Queclink TrackPro + Traxelio)?

Most current Queclink firmware supports a primary and a backup server endpoint. Useful during migration · push the same record to both for a week to validate Traxelio's decoding matches TrackPro's, then cancel TrackPro. Configure via the Manage Tool's GPRS section.

Does Queclink hardware speak any protocol other than @track?

Some Queclink models support LWM2M and TR-50 protocols for OEM integrations into telematics service providers. The @track protocol is the default and the only one in widespread fleet use. If you receive a Queclink device speaking something other than @track, it's almost certainly a custom OEM build, not the standard catalog.

What's the difference between GL-series and GV-series Queclink hardware?

GL-series = legacy entry tier (GL200, GL300, GL320 · 2G/3G focus, basic I/O). GV-series = current pro tier (GV300W, GV600M, GV58LAU · LTE Cat-M1/Cat-1, deep CAN bus, more I/O channels). Same @track protocol on both. Pick GV for any new fleet deployment unless you specifically need cheap 2G coverage.

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