Home Apps
Platform
Tracking panel Zones and alerts Reports Mobile app Compatible devices Device catalogue Connects to other systems Developer access Our own maps Every client, separate Backups Service status Where your data lives
Your brand
Your domain and logo Your app in the stores Your website Security padlock and email What you need to start How long it takes Brands already running Your reseller panel
What improvement you offer your client
Road safety Anti-theft and recovery Fuel control Regulatory compliance Preventive maintenance Delivery reliability Working-hours control Cold chain School routes Asset control Onboard video Guard patrols Field work Tracking with no device Satellite coverage Automatic alerts Silent devices Connect to their system
Who to sell it to
Freight transport Passenger transport School transport Delivery and last mile Construction and machinery Agriculture Field services Food and refrigerated Vehicle rental Security and guarding
Pricing
How billing works Volume plans What's included Your margin Payment methods Annual prepayment
Resources
Your first 30 days Technical support Training Sales material Frequently asked How to start a tracking business What it costs to start Which devices to buy How to bill your client Which protocol your GPS uses What the PESV is The GPS is not reporting Look up an IMEI Is my device supported? Your carrier's APN Look up a list of IMEIs Compare devices How much data the SIM uses When 2G shuts down When do I break even? Quote with your brand
Contact Request Demo

The Queclink (GV) protocol

The protocol of <strong>Queclink's GV family</strong> — GV75, GV300, GV500, GV350, GV55, GV20 — the Shanghai manufacturer's vehicle and fleet line.

It is a binary protocol, so it cannot be read by eye in a log. The device is configured with commands, using the SIM's APN and the server address.

Which port it comes in onOur server listens for the Queclink (GV) protocol on port 6004. That is the port you set on the device, together with the server address. Point it somewhere else and the data still leaves, but the server cannot read it. In the platform this protocol is listed as gl200.
Careful with what other sites tell youQueclink has <strong>several protocol families</strong>: the GV you see here, and the GL ones — GL200, GL100 — from another line. The part numbers look very much alike and the difference between two may be exactly the input you need: ask for the exact model in writing.

Build the configuration command

We do not have this protocol's commands yetWe would rather tell you than make them up. We only publish the ones we have checked against the manufacturer's manual or against a real device. If you have them confirmed, send them to us and we will add them.
Send us the commands

Devices that use it

QueclinkSee this brand's devices

Receive this protocol on your own platform

No server to set up and nothing to program: the platform already reads this protocol. You add the brand and the domain.

See how becoming a distributor works

Back to the lookup

IMEI lookupDevice identification tool. We do not perform unlocking, carrier release or mobile blacklist checks, and we are not affiliated with the GSMA.

Where the data comes fromPublic mobile TAC database (MIT licence, Copyright (c) 2026 Moaz Ebrahem), TAC codes published by Teltonika on its official wiki, and the protocol observed on devices connected to the Appogio platform. We publish no full IMEI and no customer data.

Frequently asked questions

What is the difference between Queclink's GV and GL families?

The GV — GV75, GV300, GV500 — is the vehicle and fleet line. The GLs are another line with their own protocol. They are not registered the same way.

Why do the part numbers look so alike?

Because the catalogue is full of very close families, and the difference between two may be exactly the input you need. Ask for the exact model in writing.

Can its log be read by eye?

No, it is binary. It has to be decoded, unlike protocols that send plain text.