GPS tracker emulation for monitoring systems

Emulate GPS trackers from GUI or CLI.

FakeGPS Tracker 2.3.0 sends synthetic GPS data to monitoring servers from a desktop app or a headless command line. Replay GPX routes, run profiles over SSH or CI, and test Windows, Linux and macOS deployments without physical hardware.

v2.3.0 build 15 — Windows · macOS · Linux · CLI
LIVE FEED
Tracker active
Latitude38.72264° N
Longitude-9.14051° W
Altitude47.3m
Speed24.6km/h
Accuracy±3m
Heading142°
Active profile
commute_morning.gpx
Capabilities

GUI and CLI for realistic GPS tracker tests.

01

GPX track replay

Import GPX from a dialog, history or drag and drop. Choose a starting point, speed and send interval; pause, resume, stop or loop route playback.

02

Headless CLI

Run without a graphical session in Terminal, over SSH, or in CI. Start several profiles at once with different IDs.

03

20 protocol variants

Version 2.3.0 supports 20 protocol variants: the previous 18 formats plus RTT Lite (rtt003) and RTT (rtt006). Both RTT variants support TCP and TLS.

04

TCP, UDP & SSL/TLS

Send data over plain TCP, encrypted TCP SSL/TLS, or UDP to compatible tracking and fleet platforms.

05

Profiles and logs

Share JSON profiles between GUI and CLI, preserve leading zeros and supported letters in device IDs, configure telemetry and keep a work log. The GUI accepts up to 20 ID characters; protocol limits apply.

06

Windows, Linux, macOS

Installers and portable packages include the required runtime. Users do not need Node.js, npm or Electron.

Version 2.3.0

What is new in 2.3.0.

Two RTT formats and longer device IDs. CLI, macOS, multiple profiles and eight languages were already available in earlier releases.

20
protocol variants
20
GUI ID characters
GUI + CLI
shared protocol set
01

RTT Lite (rtt003)

The open version 003 format is available in GUI and CLI over TCP or TLS. Lite does not require a receiver acknowledgement.

02

RTT (rtt006)

The full RTT format supports TCP/TLS and its receiver response, with localhost JSON profile examples for both RTT variants. Set your own server address and port.

03

Device IDs up to 20 characters

The GUI preserves the full ID, supported letters and leading zeros. Limits depend on the protocol: GT06 allows up to 16 characters and EGTS up to 15; longer values are rejected with a clear error.

04

OpenStreetMap loading fixed

Includes the base OpenStreetMap loading fix. Night mode, track color, all four map layers and textual attribution are preserved.

RTT Lite counts socket writes; an RTT006 acknowledgement does not prove database storage. A lost response can cause retries and duplicates. Field availability and precision depend on the protocol.

Earlier release: Version 2.2.0
Version 2.2.0

What is new compared with 2.1.3.

CLI, macOS support, multi-profile runs and eight interface languages were already available in 2.1.3. The main 2.2.0 change is protocol coverage: from 6 formats to 18 protocol variants.

18
protocol variants
12
new formats
GUI + CLI
same protocol set
01

New protocol families

Added Teltonika Codec 8/8E, Galileosky, Queclink GL200 @Track ASCII V1.02, Navtelecom NTCB/FLEX 2.0, Ruptela, Arnavi Protocol III, NaviSet v2, NaviSet with tags, ADM51 1.08, FORT 5D and JT/T 808 revision 2013.

02

Transport rules per protocol

Teltonika and Queclink support TCP, TLS and UDP. Galileosky, Navtelecom, Ruptela, Arnavi, NaviSet, ADM, FORT and JT/T 808 2013 support TCP and TLS.

03

Reliable exchange handling

The app handles connection and authorization rules, fragmented TCP responses, acknowledgement matching, reconnects and retries of the current point after failures or timeouts.

04

Safer profiles

IDs, transport choices and GPX altitude values are validated before transmission. New ID restrictions do not affect the original six formats.

Queclink ASCII and the earlier GT06 / GL200 mode are different formats. The complete field reference is documented in PROTOCOLS.md inside CLI packages.

Protocols

20 protocol variants for GUI and CLI profiles.

Choose the protocol in the app or in the JSON profile. The protocol does not change the server address or port automatically.

Kept from earlier versions

ProtocolJSON profile IDTransport
Wialon IPSexistingwialon-ipsTCP, TLS, UDP
TK103 / GPS103existingtk103TCP, TLS, UDP
GT06 / GL200existinggt06TCP, TLS, UDP
MeitrackexistingmeitrackTCP, TLS, UDP
EGTSexistingegtsTCP, TLS, UDP
SeTracker / BeesureexistingsetrackerTCP, TLS, UDP
Teltonika Codec 8existingteltonikaTCP, TLS, UDP
Teltonika Codec 8 Extendedexistingteltonika-8eTCP, TLS, UDP
GalileoskyexistinggalileoskyTCP, TLS
Queclink GL200 @Track ASCII V1.02existingqueclinkTCP, TLS, UDP
Navtelecom NTCB/FLEX 2.0existingnavtelecomTCP, TLS
RuptelaexistingruptelaTCP, TLS
Arnavi Protocol IIIexistingarnaviTCP, TLS
NaviSet v2existingnavisetTCP, TLS
NaviSet with tagsexistingnaviset-tagsTCP, TLS
ADM51 1.08existingadmTCP, TLS
FORT 5DexistingfortTCP, TLS
JT/T 808 revision 2013existingjt808TCP, TLS

Added in 2.3.0

ProtocolJSON profile IDTransport
RTT Lite (rtt003)newrtt003TCP, TLS
RTT (rtt006)newrtt006TCP, TLS

Queclink ASCII and the earlier GT06 / GL200 mode are different formats. Field availability and precision depend on the selected protocol; the full field reference is in PROTOCOLS.md inside CLI packages. RTT Lite counts socket writes; an RTT006 acknowledgement does not prove database storage. A lost response can cause retries and duplicates. Field availability and precision depend on the protocol.

Workflow

From package to live tracking in six steps.

01

Download a package

Use the Windows installer, Linux AppImage or DEB, macOS Apple Silicon ZIP, or a standalone CLI package for automation.

02

Configure profile

Enter the device ID or IMEI, choose a protocol, transport, server address, port, speed and send interval.

03

Use the built-in test server

fakegps.com runs a live GPS server. Use host 'fakegps.com', port '5569', protocol 'Meitrack' — no setup needed. Or point the app at your own server.

04

Draw or load a GPX route

Draw a route point by point on fakegps.com or load an existing GPX file in the app or CLI profile.

Draw route →
05

Start GUI or CLI

Press Start in the app, or run the CLI profile from Terminal, SSH or CI. Multiple profiles can run at the same time.

06

Verify in real time

Go to fakegps.com, enter your device IMEI or ID, and watch the tracker move live on the map as data arrives.

Check device → →
CLI guide

How to run FakeGPS Tracker from the command line.

Use the standalone CLI package when you need automation, SSH access, CI checks or several tracker profiles running in parallel without a graphical session.

01

Download CLI package

Choose the CLI archive for your OS: Windows win32-x64, Linux x64 or macOS darwin-arm64. Unpack it into a working folder.

02

Create or edit a profile

Use an example profile as a template. Set device ID or IMEI, protocol, transport, host, port, GPX file, speed and send interval.

03

Validate before sending

Run with --validate to check the profile and GPX file without opening a network connection.

04

Start transmission

Run the same command without --validate. The CLI sends positions until the route ends, loops, or you stop the process.

05

Run multiple profiles

Start separate CLI processes with different profiles and IDs. This is useful for load tests and multi-device demos.

CLI quick start
# 1. Check that the CLI starts
./fakegps-tracker-cli --version
./fakegps-tracker-cli --help

# 2. Validate a profile without connecting to a server
./fakegps-tracker-cli --profile examples/device-a.json --validate

# 3. Send one profile to your test server
./fakegps-tracker-cli --profile profiles/device-a.json

# 4. Run several trackers at once
./fakegps-tracker-cli --profile profiles/device-a.json &
./fakegps-tracker-cli --profile profiles/device-b.json &
wait

# Validate the new RTT profile examples without connecting
./fakegps-tracker-cli --profile examples/rtt003.json --validate
./fakegps-tracker-cli --profile examples/rtt006.json --validate

No desktop session required

CLI works in Terminal, SSH sessions and CI jobs. Node.js, npm and Electron are bundled in the package.

macOS first launch

If macOS blocks downloaded files, follow MACOS-FIRST-RUN.txt and allow only this verified bundle.

Linux runtime

The CLI runtime targets Linux kernel 4.18+ and glibc 2.28+. GUI packages may need a desktop session; AppImage may need FUSE.

Desktop app

The same tracker emulator on Windows and macOS.

Day and night maps, four map layers and a custom track color. Screenshots show an earlier interface version; the current 2.3.0 changes are listed above.

FakeGPS Tracker on Windows
Windows GUI with live map, GPX route, protocol settings and tracker parameters.
FakeGPS Tracker on macOS
macOS Apple Silicon build with the same map workflow and built-in CLI package.
Download

FakeGPS Tracker 2.3.0 build 15 for Windows, macOS and Linux.

GUI packages include the app and CLI runtime. Standalone CLI packages are available for automation and servers.

Save the Windows Setup file to a local folder, such as Downloads, before running it.

Apple Silicon only. The Mac ZIP is signed ad-hoc, without Developer ID or notarization. Gatekeeper may require System Settings → Privacy & Security → Open Anyway. See MACOS-FIRST-RUN.txt.

SHA-256 checksums are published in SHA256SUMS.txt.