Skip to content

gridtracker2

Live map of FT8/JS8 activity, fed by WSJT-X and JS8Call

What it does

Listens to WSJT-X or JS8Call over UDP and draws every decode on a live world map by grid square -- who is being heard where, on which band, in real time. Tracks wanted grids, states and DXCC entities against your log, and can send spots onward to PSK Reporter.

Why you would want it

FT8 without a map is a list of callsigns; with GridTracker it becomes situational awareness -- band openings are visible as they happen, and a needed grid lights up the moment it transmits. The de facto companion to WSJT-X. GridTracker2 is the maintained successor to the original GridTracker that AHRL v26 shipped.

Before it will work

WSJT-X or JS8Call running with UDP reporting enabled (WSJT-X: Settings -> Reporting -> UDP Server). No radio access of its own -- everything arrives over the network from the decoder.

How it installs

  • prebuilt deb from https://gitlab.com/api/v4/projects/61942134/packages/generic/GridTracker2/2.260812.0/GridTracker2-2.260812.0-amd64.deb — arch x86_64
  • prebuilt deb from https://gitlab.com/api/v4/projects/61942134/packages/generic/GridTracker2/2.260812.0/GridTracker2-2.260812.0-arm64.deb — arch aarch64

Known problems

An Electron application, so the .deb is large (~110 MB) and CPU/RAM use is browser-class -- relevant on a Raspberry Pi. The vendor .deb installs to /opt and provides its own desktop entry.

Keeping it current

  • probe: none
  • strategy: reinstall
  • Releases land in the GitLab package registry (gitlab.com/gridtracker.org/gridtracker2), versioned by date like 2.260812.0. No probe method reads a GitLab registry yet; when one exists this manifest is its first user.

Where to get help with the software itself

The GridTracker project -- gitlab.com/gridtracker.org/gridtracker2 issues, and an active Discord linked from the project site.

Source: catalog/packages/gridtracker2.yaml