INTEGRATION GUIDE · BITREK

How to connect Bitrek devices to cloudGPS

cloudGPS receives Bitrek trackers natively. Point the device to our server and it appears on the platform — no middleware, no extra hardware.

Connection parameters

Configure your device with the following server settings. Devices are identified and must be added to your cloudGPS account beforehand.

Server (domain)bt.cloudgps.online
Port3202
TransportTCP
Data protocolBitrek
IdentificationIMEI
APNyour SIM operator's APN
cloudGPS is hardware-agnostic — Teltonika, Bitrek, Wialon-compatible and Globus devices run on one platform, so mixed fleets stay together.

Step-by-step setup

Get the device online in a few steps.

Add the device in cloudGPS

In your cloudGPS account add a new device of type Bitrek and enter its IMEI. Only authorized devices are accepted by the server.

Set the APN

Make sure the SIM card's mobile data APN is configured (and username/password if your operator requires them).

Point the device to the server

Set the server address, port and transport as below:

Server : bt.cloudgps.online
Port   : 3202 (TCP)

Via the manufacturer configurator or by SMS:

Verify

Once the device sends its first packet it goes online in cloudGPS within seconds — position, speed and sensor data appear on the map. If it stays offline, re-check APN, device authorization and that the port/TCP is reachable.

Tested models

Verified models include (any compatible model works):

BI 530RBI 810BI 910

What your fleet gets on cloudGPS

cloudGPS turns raw telemetry into actionable fleet data.

Need help connecting?

We help integrators and fleets bring devices onto cloudGPS — including bulk onboarding and migration from other platforms.

mail Contact us