They do not accept adminip or dns
The adminip and dns commands belong to the GT06 and h02 families. On a TK103 they do nothing. If you administer a mixed fleet, this is the most common cause of "half the batch migrated".
Hardware guide · tk103 · port 5002
The TK103 family is old, cheap and still everywhere. It takes a hostname happily — but a few units announce themselves under a truncated IMEI, and then look like they never arrived.
| Protocol | Port | Server command | APN command | Tested on |
|---|---|---|---|---|
| tk103 | 5002 | SERVER,666666,0,<host>,5002,0# | APN,666666,<APN># | 23 vehicles in service (9 plus 14 Askoll e-bikes) |
Server: trackers.moongpstracker.com (169.58.68.140), TCP. Some firmware refuses domain names — then use the IP.
TK103 is a Chinese tracker design from the early 2010s, cloned into hundreds of variants — the flat black "soap bar" units you find on scooters and e-bikes. They speak the tk103 protocol and are configured with comma-separated SMS commands terminated by a hash.
Unlike the GT06 clones, TK103 units generally do resolve domain names, so you can use the hostname and not care about our IP changing.
The APN belongs to the SIM, not to the tracker. These are the two we use ourselves:
On both, the APN username and password are empty — which is the usual case on IoT SIMs. If your SIM comes from a mobile operator, ask them for all three values.
Send both SMS from any phone. 666666 is the TK103 factory password. Note the trailing # on each command: without it the device ignores the message.
SERVER,666666,0,trackers.moongpstracker.com,5002,0# The third field is the address mode: 0 means "what follows is a domain name". The last field is the protocol (0 = TCP).
APN,666666,<APN># APN username and password go in two extra comma-separated fields if your SIM needs them. Most IoT SIMs do not.
SERVER,666666,1,169.58.68.140,5002,0# Third field 1 means "what follows is an IP address". Use this on firmware that cannot resolve domain names — the symptom is a device that acknowledges SERVER and then never connects.
After the device is configured it turns up in Unknown devices in the Moon panel — or straight on your map, if you registered its identifier first. The first position normally lands within minutes.
Which values arrive depends on the device and the installation, never on your licence: every Moon account has the whole platform. See what the platform does.
The things that cost us time on real vehicles, written down so they do not cost you any.
The adminip and dns commands belong to the GT06 and h02 families. On a TK103 they do nothing. If you administer a mixed fleet, this is the most common cause of "half the batch migrated".
A subset of TK103 devices announce their identifier as a leading zero followed by the LAST ELEVEN DIGITS of the IMEI, not the full 15-digit number printed on the case. On our own migration this bit us: fourteen devices were registered under the IMEI on the box, and stayed silent, while the real identifier sat in Unknown devices under a number nobody recognised.
If a TK103 does not appear after the SERVER command, look through Unknown devices for an ID that ends the same way as your IMEI. That is your device. Register it under the identifier it actually announces.
Every TK103 command ends with #. A phone keyboard that autocorrects or an SMS gateway that strips it turns the command into a message the device discards without replying.
The commands on this page use the factory password (666666). A tracker left on its factory password can be reconfigured by anyone who knows its SIM number. Change it, or use SIMs that cannot receive SMS from outside numbers — the 1NCE and Truphone SIMs we ship are set up that way.
Send the commands yourself and register the device in the panel, or tell us what you have and we will confirm what it can do on Moon before you commit to anything.
No account yet? Send us the make and model and we will set the device up on a demo account for you.
Not sure it is the right model? Send it to support@moongpstracker.com and we will tell you before you buy.
The compatibility hub lists every open port against the protocol it serves.
teltonika · port 5027
teltonika · port 5027
gt06 (some units: gt02) · port 5023 (gt02 units: 5022)
h02 · port 5013
h02 · port 5013
watch · port 5093
JT808 / Huabao · port 5015
We use cookies only to measure how the site is used (Google Analytics). No marketing, no profiling. See the cookie policy.