JT/T 808 Protocol · Chinese national standard, port, packets
0 devices 0 brands Port 5015 (Traxelio / Traccar huabao) · 6207 (MOT compliance reference) TCP (UDP variant on some firmware)

JT/T 808 Protocol (Chinese National Standard)

Binary TCP protocol mandated by the Chinese Ministry of Transport (交通运输部) for fleet-grade GNSS terminals · the wire format every Chinese-compliance GPS tracker speaks. Used by Howen, Streamax, Concox compliance variants, and hundreds of OEM dashcam manufacturers worldwide.

Talk to integration team Read the spec

4 min read · ~756 words

Quick answers

Is JT/T 808 the same as Huabao?

Same thing under two names. JT/T 808 is the official Chinese transport-ministry standard. Huabao is Traccar's slug for one specific JT/T 808 implementation that the open-source community decoded first · the slug stuck even as the decoder grew to handle the broader JT/T 808 ecosystem. Today both names refer to the same wire format.

What port does JT/T 808 use?

Traxelio's ingest port is 5015 (TCP, matches Traccar's huabao decoder default). The Chinese MOT compliance port is operator-assigned (often 6207). Configurable on the device side via the OEM's SMS or AT-command interface.

Why do my Chinese-export trackers speak JT/T 808 even though I don't need Chinese compliance?

Default firmware. Most Chinese OEMs ship JT/T 808 as the default protocol because that's what their domestic-market hardware uses · the export-market variants inherit it unless the buyer specifies otherwise. Operators discover this on device evaluation. Traxelio decodes JT/T 808 natively so the firmware default isn't a barrier.

What's the difference between JT/T 808-2011, -2013, and -2019?

Three revisions of the same standard. 2011 = original (legacy hardware still uses it). 2013 = mid-revision (most current Chinese-export hardware uses it). 2019 = current revision (newer dashcam DVR and AI-driving hardware uses it). Backward-compatible at the packet-envelope level · message-ID additions in newer revisions don't break older decoders.

Does Traxelio decode JT/T 1078 video streaming?

JT/T 1078 (the video / dashcam streaming layer that rides on top of JT/T 808) is supported on request for fleets running Howen / Streamax / similar Chinese-OEM dashcam hardware. The 1078 streaming endpoint is configured separately from the 808 telemetry endpoint · contact support for setup.

JT/T 808 is the Chinese transport-ministry standard for GNSS vehicle terminal communication. Every Chinese-compliant fleet GPS tracker · whether sold inside China or exported · speaks JT/T 808 in some revision (the 2011, 2013, or 2019 spec versions). The standard is the dominant fleet protocol by sheer device count globally · more devices ship JT/T 808 than any single other fleet protocol, even though Western fleet operators rarely encounter it.

The standard is published in full by the Chinese Standardization Administration. Implementations exist as open-source decoders (Traccar's huabao decoder is a JT/T 808 implementation; EMQX's open-source IoT gateway has a JT/T 808 plugin) and commercial servers. Traxelio decodes JT/T 808 natively for fleets operating cross-border or running Chinese-OEM hardware in Western deployments.

Protocol-at-a-glance

  • Transport · TCP (UDP variant for some firmware)
  • Default port · 5015 (Traxelio's ingest port; matches Traccar's huabao decoder default; configurable on the device side)
  • Encoding · binary, escape-sequence framed (0x7E start/end markers · escape 0x7D + 0x01/0x02 for literal 0x7D/0x7E inside payload)
  • Auth · device authentication packet (0x0102) carries the unique terminal ID + auth code · server replies general response (0x8001)
  • Spec versions · JT/T 808-2011 (legacy, still common), JT/T 808-2013 (revision), JT/T 808-2019 (current)
  • Related standards · JT/T 1078 (video / dashcam streaming, layered on top), JT/T 809 (server-to-server forwarding, the Chinese equivalent of Wialon Retranslator)

Packet structure

Every JT/T 808 packet has the same envelope:

0x7E [MSG_ID (2B)] [BODY_PROPS (2B)] [TERMINAL_PHONE (6B BCD)] [SERIAL (2B)] [BODY...] [CHECKSUM (1B)] 0x7E
  • MSG_ID = message type (0x0100 register, 0x0102 auth, 0x0200 position, 0x8001 general response, 0x9101 video stream control, etc.)
  • BODY_PROPS = length + encryption flag + multi-packet flag
  • TERMINAL_PHONE = 6-byte BCD-encoded terminal phone number (used as the device identifier · NOT the IMEI)
  • BODY = message-specific payload (position record, sensor data, command response)
  • CHECKSUM = single-byte XOR of all bytes between (and excluding) the 0x7E markers

The 0x7E framing means any 0x7E or 0x7D byte in the payload is escaped (0x7E → 0x7D 0x02, 0x7D → 0x7D 0x01). Decoders un-escape before parsing.

Why JT/T 808 dominates by device count

  • State mandate inside China · the 2013 transport ministry circular requires all fleet vehicles (taxi, freight, hazardous-materials) to install JT/T 808-compliant GNSS terminals · estimated 50+ million devices in active use in China alone
  • Default for Chinese OEMs · Howen, Streamax, Concox compliance variants, JIMI compliance variants, and hundreds of dashcam / DVR manufacturers ship JT/T 808 as the default protocol · western OEM rebrands inherit it
  • Compliance ecosystem · JT/T 808 plugs into the Chinese government's MOT (Ministry of Transport) monitoring platform via JT/T 809 server-to-server forwarding · once a fleet is on JT/T 808 hardware, compliance reporting is automatic
  • Cross-border bleed · Chinese-export hardware (motorcycle trackers, asset tags, low-end fleet) often ships with JT/T 808 firmware whether or not the export market requires it · operators discover the protocol on their first device-evaluation

Configuring a JT/T 808 device for Traxelio

JT/T 808 device configuration varies by manufacturer · there isn't a single universal configurator the way Teltonika ships Configurator or Queclink ships Manage Tool. Common patterns:

  • SMS commands (most Chinese OEMs):

    *SERVER#TYPE,1,traxelio.com,5015,0#
*APN#internet,,,#
*RESET#

    (Exact syntax varies · check the model's SMS command sheet.)

  • AT-command serial console: connect via USB-to-serial and send AT-style commands documented in the model's developer guide

  • Cloud OEM platform: many Chinese OEMs ship a cloud configurator (varies by vendor) · navigate to the device's settings and set the server endpoint

Supported devices in our catalog

30+ devices declare protocol: "huabao" (Traccar's slug for JT/T 808 · the catalog will canonicalise to jt808 in a future cleanup cycle). The headline models: Howen Hero ME31, Howen Hero MD41, Streamax X3 / X5 / X7 dashcam DVR units, plus dozens of Concox and Jimi compliance variants and a long tail of Chinese-export trackers.

JT/T 808 vs Huabao vs the "Chinese protocol" naming

The same protocol has three names in common use:

  • JT/T 808 · the official Chinese standard name · JT/T = Jiao Tong Tielu (transport-rail), 808 = standard number · always written with the slash
  • Huabao · Traccar's slug for one specific JT/T 808 implementation (Huabao is a Chinese GPS tracker manufacturer whose hardware Traccar reverse-engineered first) · the slug stuck even as the decoder grew to handle the broader JT/T 808 ecosystem
  • "Chinese protocol" · informal shorthand operators use when they don't know the standard name

All three refer to the same family. Traxelio's catalog currently uses huabao as the protocol slug for legacy reasons · a cleanup commit will canonicalise to jt808 to match the spec's actual name.

Setup walkthrough

  1. 1

    Check the device's OEM configurator path

    JT/T 808 hardware varies by manufacturer (Howen, Streamax, Concox compliance variants, JIMI compliance variants). Check the model's manual for the canonical config method · SMS, AT-command serial console, or vendor cloud configurator.

  2. 2

    Set the server endpoint via SMS or AT

    Most Chinese-OEM JT/T 808 devices accept SMS commands like *SERVER#TYPE,1,your-server.com,5015,0# · check the model's exact command sheet. Vendor portals usually expose the same settings via web UI.

  3. 3

    Set the APN

    *APN#your_carrier_apn,,,# (Sinotrack-derived JT/T 808 firmware) or vendor-specific equivalent. APN must be correct before any data session opens.

  4. 4

    Reboot the device

    *RESET# or hard power-cycle. The device authenticates via Registration (0x0100) + Authentication (0x0102) packets · server replies with general response (0x8001) on accept.

  5. 5

    Validate the 0x7E framing arrives intact

    If positions don't arrive, capture a TCP dump on the server · packets should start and end with 0x7E. If you see garbage bytes inside the body, the firmware likely mis-implements the escape rule · contact the OEM for a firmware update.

  6. 6

    Don't have a JT/T 808 server yet?

    Traxelio decodes JT/T 808 natively on port 5015 (Traccar huabao decoder · same protocol, historical name). Point the device at the Traxelio endpoint and the first decoded position can be verified in Traxelio. JT/T 1078 video streaming and JT/T 809 server-to-server forwarding available on request.

Reference

Configuration reference

Parameter Value
Transport TCP (UDP variant on some firmware)
Default port 5015 (Traxelio / Traccar huabao) · 6207 (MOT compliance reference)
Packet envelope 0x7E [body with escape sequences] 0x7E
Escape rule 0x7E → 0x7D 0x02 · 0x7D → 0x7D 0x01 (inside payload)
Authentication Registration (0x0100) + Authentication (0x0102) packets · server replies general response (0x8001)
Checksum XOR of all bytes between 0x7E markers
Spec versions JT/T 808-2011, JT/T 808-2013, JT/T 808-2019
Spec PDF www.scribd.com/document/837914037/JTT-808-2019
Open-source decoder Traccar (`huabao` decoder) · EMQX IoT gateway
Related standards JT/T 1078 (video / dashcam), JT/T 809 (server-to-server forwarding)

Or skip the integration

Traxelio decodes JT808 natively

Point your device at our endpoint, then verify the first decoded position in Traxelio. We handle the protocol, ack the packets, and serve the dashboards.

Plan a protocol cutover Talk to integrators

Protocol Capabilities

Data Points from JT808 Devices

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

Common troubleshooting

Device authenticates successfully but no position records arrive

Some JT/T 808 firmware variants require an explicit position-reporting configuration command (0x8103 set terminal parameters) after authentication · without it, the device sits idle. Traxelio's ingestor sends the standard configuration command on auth-success · if positions still don't arrive, check the model's parameter list for the position-frequency setting (parameter ID 0x0029 is the common one).

Position checksum errors flagged on a fraction of packets

Common cause: device firmware mis-implements the escape rule (forgetting to un-escape the body before computing the checksum). Two paths: (1) firmware update from the OEM (often fixes); (2) Traxelio's decoder has a tolerant mode that accepts checksums computed either pre- or post-escape · check the model's known-quirks list.

Streamax dashcam DVR uploads positions but video stream fails to start

Video streaming is JT/T 1078 (separate protocol on a separate port), not JT/T 808. The 808 telemetry endpoint and the 1078 streaming endpoint are configured independently · check the device's video-streaming settings and confirm the 1078 endpoint points at Traxelio's streaming ingest (separate from the 5015 telemetry port).

Explore More

Other Protocols

GT06

99 devices

H02

96 devices

Teltonika

84 devices

Meiligao

59 devices

GL200

36 devices

Huabao

32 devices
View All Trackers

FAQ

Frequently Asked Questions

Is JT/T 808 an open standard?

Yes · published by the Chinese Standardization Administration. The spec PDF (in Chinese, with English-language community translations) circulates widely. Traccar's huabao decoder and EMQX's IoT gateway both implement it open-source. No licensing barrier to decoding it.

Why is the protocol called JT/T 808 and not just JT 808?

JT/T is the Chinese transport-ministry standards series · the slash is part of the official name. JT = Jiao Tong (transport), T = Tielu (rail-related industries). The 808 is the standard number. Operators casually drop the slash when writing in English · both JT/T 808 and JT808 are common in the wild and refer to the same standard.

What's JT/T 809?

The server-to-server forwarding standard that pairs with JT/T 808 · it specifies how a JT/T 808-compliant server forwards processed records to the Chinese MOT monitoring platform (the equivalent of Wialon Retranslator in the Chinese ecosystem). Traxelio doesn't currently forward to MOT but the JT/T 809 protocol can be enabled on request for fleets that need to maintain Chinese compliance reporting from a non-Chinese server.

Can I use JT/T 808 hardware outside of China?

Yes · the protocol itself is country-agnostic. Many Western fleets unknowingly run JT/T 808-compliant hardware (especially in motorcycle, asset-tag, and budget-fleet deployments) because the Chinese OEMs default to it. Traxelio decodes the protocol regardless of where the device is deployed.

Does JT/T 808 support CAN bus?

Through the JT/T 808-2013 and -2019 extensions, yes · the standard reserves message-ID ranges for additional sensor / CAN data, and individual OEMs (Howen, Streamax) extend with vendor-specific CAN profiles. Coverage varies by manufacturer · for guaranteed CAN bus depth on a non-Chinese-compliance fleet, the comparison is Teltonika Codec 8 or Ruptela.

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