
GPS tracker for RMPD and SENT: which systems connect to the Moisa Logistics account
The search “GPS tracker for RMPD” hides two different devices. The first is the locator whose number sits in the RMPD or SENT and without whose positions Poland fines you. The second is the fleet tracker where the dispatcher watches the trucks. We explain the difference, say what GPS Polish law requires, and list the systems that connect to the Moisa Logistics account: Wialon, Navixy, cloudGPS, Mapon, TrustTrack, Freetrack and Tekson Fleet.
Key figures
In short
- A GPS tracker for RMPD, in the legal sense, is a locator: the e-TOLL PL app on the driver’s phone, an OBU or a fixed ZSL registered by an operator in PUESC for SENT. Its number goes into the RMPD and the SENT.
- A fleet tracker (Wialon, Mapon, TrustTrack and others) shows trucks to the dispatcher, but does not send positions to PUESC on its own until a ZSL operator registers it for SENT.
- Seven tracker systems connect directly to the Moisa Logistics account: Wialon, Navixy, cloudGPS, Mapon, TrustTrack, Freetrack and Tekson Fleet - with their dealers.
- Other providers have no direct connection yet: write to us and we will arrange data transfer with the provider.
- From a connected tracker we only see vehicles and coordinates - for the fleet map, RMPD and RMPD 406 trip tracking and the start-point check.
A trip tracker and an RMPD locator: two different things
The RMPD and SENT locator
Mandatory. Sends positions to the PUESC register, and its number goes into the notification. It is the e-TOLL PL app, an OBU or a ZSL registered by an operator for SENT. No position - a 10,000 zł fine for the carrier.The fleet tracker
For the dispatcher. Shows vehicles in your monitoring system (Wialon, Mapon, TrustTrack…). In the Moisa Logistics account it adds the fleet map and a comparison with PUESC data, but on its own it does not replace the locator.The law draws this line directly. The locator or device number is a mandatory RMPD field (art. 28b(3)(12) of the Polish Road Transport Act). The SENT act calls a locator a device running software provided by the Head of KAS (in practice, e-TOLL PL), and an external location system (ZSL) a carrier’s system with a device in the vehicle through which positions reach the register. OBU and ZSL devices for SENT and e-TOLL are registered only by the OBU/ZSL operator (PUESC FAQ 07.05). So a fleet tracker becomes a locator only when its provider is a ZSL operator and has registered your particular device for SENT, not just for e-TOLL (07.15). More in the GPS locator for RMPD and SENT.
Which GPS Poland requires for RMPD: the short answer
For RMPD and SENT, Poland does not accept “any GPS”, only one of three options:
| Option | Where the number comes from | Worth knowing |
|---|---|---|
| The e-TOLL PL app on the driver’s phone | The app shows its identifier after the first start | The simplest start; depends on battery, internet and phone settings |
| OBU - on-board unit | The operator registers the device in PUESC and issues a business number | For SENT and RMPD - only if the operator registered it for SENT |
| ZSL - fixed tracker | The ZSL operator registers the device and issues a business number | Does not depend on a phone; your fleet tracker can be a ZSL if the provider is an operator |
The PUESC FAQ recommends a pair: OBU or ZSL as the main locator and the e-TOLL PL app as the backup (07.13). Whether your tracker provider is a ZSL operator you can check with them or in the official list of OBU/ZSL operators admitted to e-TOLL on etoll.gov.pl. Keep in mind: that list is about e-TOLL admission, and the registration of a specific device for SENT is confirmed by the operator.
A GPS for SENT is the same set. There has been no separate SENT GEO app since 01.12.2021: positions for SENT and RMPD are sent by e-TOLL PL, and the name SENT-GEO stayed with the PUESC module that receives positions. How this works on the driver’s phone is covered in SENT on the driver’s phone.
GPS tracker for RMPD in the account: which systems connect
A tracker connects to the Moisa Logistics account not by device brand but by the system where you see your vehicles. In “Profile” → “Integrations” → “GPS trackers” you pick your provider (dealer) or the system directly, and the “Step-by-step guide” leads you on. Here are all systems and brands that connect today:
| System | Brands and dealers | How it connects |
|---|---|---|
| Wialon | Wialon Hosting and Local; Укр-Астра, overseer, KTSM, KM ТРЕЙД, SKY-TRACK, Antenor, GG-Tech, ЄВРОМОБАЙЛ, gpska, GPS-Group, BITREK | Sign in through the Wialon page with your own login and password (only Wialon sees the password) or a Wialon token |
| Navixy | TA GPS (TIPSTER), Navixy Europe, Navixy America, Navixy dealers with their own address | The Navixy account owner’s login and password: we sign in once, create a “Moisa Logistics” key and sign out; we do not store the password |
| cloudGPS | cloudGPS, GlobusCloud (SKT “Globus”) | A token from “Profile” → “API” with read-only rights |
| Mapon | Mapon and its partners | API key: Settings → API keys → CREATE API KEY; you choose the vehicles for the key |
| TrustTrack | Ruptela TrustTrack, Persey SSM (ПЕРСЕЙ ССМ), Linqo | API key: Account settings → API key settings → New API key |
| Freetrack | Freetrack (gps.freetrack.ua) | A separate user for Moisa with access to the right vehicles, and that user’s token |
| Tekson Fleet | Tekson (app.teksonfleet.com) | “Stały dostęp przez API”: API link, login and password |
Dealer tiles in the account are marked “via Wialon”, “via TrustTrack” and so on. If you sign in to Wialon through a dealer’s site, the address on that dealer’s tile is already filled in: Укр-Астра - trek.ukrastra.com.ua, overseer - gps2.overseer.ua, KTSM - wialon.gps-garant.com.ua, KM ТРЕЙД - hosting.km-trade.net, SKY-TRACK - monitoring.skytrack.com.ua, Antenor - gps.antenor.online, GG-Tech - wln.gg-tech.com.ua, ЄВРОМОБАЙЛ - local.euromobile.com.ua. Dealer not among the tiles? Enter the site where you sign in into the Wialon address field.
Instructions for each system
Step-by-step setup for your system is in separate guides:
- Wialon and RMPD: how to connect a Wialon tracker
- Navixy and RMPD: connect a Navixy or TA GPS (TIPSTER) tracker
- cloudGPS and GlobusCloud: connecting a tracker to RMPD tracking
- Mapon and RMPD: how to connect a Mapon tracker
- TrustTrack RMPD: connect a Ruptela or Linqo tracker by API key
- Freetrack and RMPD: how to connect the tracker
- Tekson Fleet RMPD: connect your tracker through API access
Your provider is not in the table: write to us
Some providers our customers work with have no direct connection yet: Teltonika, Forguard, ProfGPS, ВІДІС, ВЮСТ, 130, Форум ОКО, Protracking, Moniterra, ТахоСервіс-Рівне. In the account they sit in the “On request” block. Write to our support and we will arrange data transfer with the provider. We do not promise an exact timeframe.
Before you write, check where exactly you see your vehicles. If you sign in to one of the systems in the table - for example, devices of another brand show up in your Wialon - choose that system: the brand of the tracker itself does not matter here.
What a connected tracker gives for RMPD and RMPD 406
From a connected system we only get read access: the list of vehicles and their coordinates. We change nothing in your system. Vehicles are matched to your fleet by licence plate on their own, and data refreshes every 5 minutes. Then it works like this:
- Fleet map. Vehicles on a trip with RMPD tracking - with the order number and the route driven, others - from the tracker, with the time of the last point next to each.
- RMPD and RMPD 406 trip tracking. PUESC data is the basis. The tracker adds a dashed line next to the PUESC line if the system provides movement history, and a “fine risk” entry when it sees movement and PUESC does not. When PUESC is silent and the tracker shows the truck standing, tracking pauses without an alert.
- Route check in the RMPD form. When the vehicle is now far from the start point, a yellow warning appears: the distance, where the vehicle is and when it was seen. It does not block filing and only asks you to check the start date and place.
The company owner connects the system; several accounts of one system are added separately. You can disconnect at any time: we delete the access on our side, and you delete the “Moisa Logistics” key in your system. What tracking looks like is shown in why RMPD 406 and trip tracking, and how to check a position in PUESC yourself - in the RMPD 406 guide.
Common GPS mistakes with RMPD
| Mistake | How to spot it | What to do |
|---|---|---|
| The fleet tracker number was entered in the RMPD | RMPD 406 shows no position | Enter e-TOLL PL, an OBU or a ZSL registered in SENT - with an RMPD 101 update |
| The device is registered only for e-TOLL | Tolls are paid, but the RMPD has no position | The operator adds the SENT service; check this before the trip (FAQ 07.15) |
| Connecting the tracker to the account was taken as a locator | The truck is on the fleet map, but there is no PUESC line | Check the locator number in the RMPD and start the SENT/RMPD trip in e-TOLL PL |
| A dealer of another system was chosen | The guide does not match your system’s menu | Choose the system where you actually see your vehicles |
| A new vehicle was not added to the access | It is missing from the fleet map | Add it to the Mapon key, the Tekson share or the Freetrack user |
What happens when a fleet tracker is mistaken for a locator - three real cases in car transporters and GPS fines.
What trip tracking costs
- RMPD, full service - 500 UAH per document; self-service in the account - 100 UAH (first 10 days - 0 UAH). Tracking is already included in the RMPD price.
- An RMPD prepared elsewhere - RMPD 406 for 50 UAH: a map from PUESC data and an alert when the GPS signal drops.
Order: RMPD full service, RMPD self-service, RMPD 406.
Frequently asked questions
Sources
- Ustawa z dnia 6 września 2001 r. o transporcie drogowym, tekst jednolity Dz.U. 2025 poz. 1490 (art. 28, 28b, 28c, 89a1, załączniki nr 1 i 3)checked 18 November 2026
- Ustawa o systemie monitorowania drogowego i kolejowego przewozu towarów (SENT), tekst jednolity Dz.U. 2024 poz. 1218: art. 2, 3 ust. 6, 5-11, 13-17, 21-24, 31-32 (dla RMPD - przez art. 28b ust. 5 ustawy o transporcie drogowym)checked 18 November 2026
- PUESC - FAQ SENT, 07. Obsługa zewnętrznych systemów lokalizacji ZSL/OBU (07.05-07.20, aplikacja e-TOLL PL jako lokalizator zapasowy)checked 21 November 2026
- e-TOLL - Urządzenia pokładowe OBU i ZSLchecked 21 November 2026
- e-TOLL - Operatorzy OBU/ZSL dopuszczeni do systemu e-TOLL (lista operatorów i urządzeń, PDF)checked 21 November 2026
- e-TOLL - Aplikacja e-TOLL PLchecked 21 November 2026
- e-TOLL - Mobile applications for e-TOLL and SENT (17.06.2021): SENT GEO driver application for SENT until 31.10.2021, from 01.11.2021 e-TOLL PL the only application; the dates were later moved: SENT GEO for SENT until 30.11.2021, e-TOLL PL the only application from 01.12.2021checked 19 November 2026
- PUESC - Aplikacje mobilne: „Aplikacja Kierowcy SENT GEO” na potrzeby SENT tylko do 30 listopada 2021 r.; od 1 grudnia 2021 r. jedyna aplikacja do przekazywania danych geolokalizacyjnych do systemu SENT to e-TOLL PLchecked 21 November 2026
- e-TOLL - One application for e-TOLL and SENT systems since December 1 (07.12.2021): since 01.12.2021 e-TOLL PL is the only application transferring geolocation data to e-TOLL and SENTchecked 21 November 2026
Need documents for a trip?
Create a free account and prepare the document in your account - by yourself or with our team’s hands. Or leave a request: we will call you and tell you what you need for your particular trip.
More news



We are on TikTok
How to prepare documents from your phone, what is changing for carriers and where to save - in short videos.



