Paste a raw GPS tracker packet as hexadecimal, ASCII, JSON, NMEA, Base64, or a byte array. The inspector evaluates the complete Open VTS reference decoder catalogue, verifies protocol-specific framing, ranks matching protocols, and translates device identity, location, status, network, sensor, checksum, and packet fields into readable values. Packet contents are processed in memory and are not retained.
Tool Guide
This protocol inspection utility helps GPS software developers, device integrators, and support engineers understand unknown tracker traffic. It runs protocol-specific frame splitters and production decoders across the Open VTS catalogue, explains why a protocol matched, and presents the complete decoded result in plain language while preserving the original packet for comparison.
No automatic detector can guarantee a protocol from every isolated packet because many tracker families share framing patterns. The tool ranks likely matches and shows evidence so you can verify the result against device documentation and live acknowledgement behavior.
The packet is sent to the Open VTS website decoder, processed in memory, and not stored by this tool. Avoid pasting secrets or production credentials, and redact sensitive data before sharing diagnostic results.
You can paste hexadecimal bytes with or without spaces, raw ASCII tracker messages, JSON location payloads, common NMEA sentences, explicitly prefixed Base64, JSON or comma-separated byte arrays, and Node.js Buffer JSON. The tool automatically selects the representation.
