JS8 Spotter: The Must-Have Companion Tool for JS8Call
JS8Call is great at weak-signal keyboard messaging—but anyone who spends time on busy frequencies knows the downside: the activity scrolls nonstop, and you only see a small snapshot unless you chase offsets and click into conversations.
That’s where JS8 Spotter comes in.
In this episode, MJ (KW3KW) introduces JS8 Spotter as a “companion tool” that helps you track, search, organize, and exchange information across the JS8 ecosystem—especially useful for EmComm / MCOM groups and anyone who wants to make JS8 more functional and engaging.

What Is JS8 Spotter?
JS8 Spotter is a companion application for JS8Call that fills major gaps by:
- Tracking and sorting activity (callsigns, keywords, groups)
- Supporting fast “forms” reporting (similar concept to FLMSG, but optimized for JS8 workflows)
- Publishing messages that others can pull on-demand
The big idea: instead of getting buried in the live stream of traffic, you can search what matters, send structured reports quickly, and—most importantly—let others pull updates when they need them.
Why Use JS8 Spotter?
1) It turns the JS8 “firehose” into searchable intelligence
JS8Call activity can be overwhelming. JS8 Spotter lets you define search terms like:
- Specific callsigns
- Keywords (ex: “net”, “antenna”, “ARES”, etc.)
- Groups / word groups
Then it captures matching traffic so you can review full messages later—without being tethered to the screen.
2) It’s built for “set it and forget it” monitoring
A key theme is persistence: the longer you run it, the more useful data it collects. You can walk away, come back, and filter down to a concise list of things you actually care about.
3) It supports EmComm-style reporting with forms
JS8 Spotter includes structured forms (net check-ins, status/situation reports, etc.). These are fast to transmit because it sends only the alphanumeric answers, not the full question text.
That means:
- Shorter transmissions
- Cleaner reporting
- Easier to collect and forward reports during busy operations
The “Game Changer”: Not Just Push—Pull
MJ emphasizes the feature that makes JS8 Spotter feel different from typical message tools:
- You can publish a message/report
- Others can pull it later if they missed it
Example use cases:
- Daily weather
- Solar conditions
- “Traffic / news” bulletins
- Situation reports
- Group updates
Instead of re-sending the same info all day, you publish once and let stations retrieve it when needed.
Profiles, Background Search, Sorting, and Filtering
JS8 Spotter supports profiles so you can create different “views” for different use cases:
- A group profile (everyone watching the same keywords/callsigns)
- A “contacts only” profile (callsigns only)
- A “nets” profile (keywords like “net”, “check-in”, group names)
It also supports:
- Background scanning across profiles
- Filters (e.g., show only “net” hits)
- Time-based sorting (e.g., last 4 hours)
- Highlight windows (e.g., highlight who showed up in the last 30 minutes)
Result: you can reduce tons of activity into a short, actionable list.
Forms: How They Work and Why They’re Faster
The workflow described is:
- Fill out a form (like a “301 situation report”)
-
JS8 Spotter generates a compact message that includes:
-
- Destination group/callsign
- Form number
- Answer sequence (only the answers)
- Optional date/time format
Why it’s faster:
- You’re not sending “Question text + answer” repeatedly
- Just the coded answers go over the air
Important requirement: both stations must have the same form definitions installed—especially if you use custom forms.
FCC Compliance Note (Forms Must Be Public)
MJ notes that, to stay compliant, forms should be published on a public website. Standard forms are available on the developer’s site; if you create custom forms, operators often post them on a simple public page so others can reference them.
Three Key Areas to Learn First (So You Don’t Get Lost)
MJ recommends focusing on three menus inside JS8 Spotter:
-
Expect subsystem
Where you create/publish messages and manage pullable items. -
MC Forms
Where you fill out and send forms (which then post to the expect subsystem). -
MC Form Responses
Where you review incoming form submissions.
You can view responses as:
-
- A decoded Q/A view, or
- The full form layout pre-populated with answers (often easier to read/forward)
Extra Features: APRS / Email / SMS (Use With Realistic Expectations)
JS8 Spotter can also send certain outbound messages like SMS/email via gateways, but MJ frames it as:
- One-way and not always verifiable
- “Better than nothing” in a pinch
- For robust messaging, Winlink is often the better primary solution
A practical tip mentioned: save multiple gateways (different regions) so if one area is down, you can try another.
Who Should Use JS8 Spotter?
It’s not only for formal EmComm groups. JS8 Spotter is useful if you want to:
- Monitor specific stations you care about
- Track keywords that signal interesting activity
- Review complete messages later
- Coordinate nets with structured reporting
- Publish repeatable bulletins others can pull
In short: if you’re using JS8Call regularly, JS8 Spotter adds the organization and workflows JS8Call doesn’t provide natively.
Summary Takeaways
- JS8 Spotter is a high-value companion tool for JS8Call
- It adds search + tracking, forms, and publish/pull messaging
- It helps you stay persistent without staying glued to the rig
- It’s especially strong for MCOM/EmComm coordination where structured, repeatable reporting matters