Gridtracker — Log4om

That’s when I discovered the quiet power of connecting to Log4OM .

GridTracker’s alert system pings me when a rare DX entity or a new grid appears. I work the station. Log4OM logs it. Later, when I run a “Missing Grids” report in Log4OM, the data is already there. No reconciliation weekends. No “wait, did I log that?” gridtracker log4om

Then I stumbled on the integration. One toggle. One TCP port. One “aha” moment. That’s when I discovered the quiet power of

At first, I treated them as separate tools: GridTracker for the live, dopamine‑hit visual of chasing grids on a world map, and Log4OM for the serious business of archival logging. But running them in parallel felt like driving with two steering wheels. Duplicate entries. Missing timestamps. The occasional logged QSO that never made it to my master log. Log4OM logs it

Because a QSO you don’t log is a QSO you never made. And a grid you don’t track is a grid you’ll work twice.

It started as a messy pile of digital breadcrumbs. After every contest or casual FT8 session, I’d have a half‑empty ADIF file here, a manual pencil note there, and a GridTracker map full of colorful blips that vanished the moment I closed the window. My logging was a leaky bucket. Something had to change.