ON4KST contest workflow for 144 MHz and above

KST4Contest

ON4KST shows you the traffic. KST4Contest helps turn it into an operating decision by combining chat, candidate prioritisation, sked planning, AirScout data and logger integration in one desktop client.

The available information is filtered, related to active stations and presented in a contest-oriented workflow. The final decision still belongs to the operator.

Functions sharing the same station context
✈️ AirScout Integration Use AirScout AP predictions in candidate evaluation, the timeline and sked planning.
💬 Dual Chat Categories Log in to two ON4KST categories and handle both message streams in one station list and interface.
📡 DXCluster Server Send direction warnings as DX Cluster spots to compatible logging software when a usable QRG is known.
KST4Contest Features
🔄 Log Synchronization Import worked stations and current frequencies from supported contest loggers so filters and band information follow the log.
⚡ Macros and Variables Build recurring chat messages from configurable text blocks and variables such as the current QRG or locator.

The operating problem

The useful station is rarely the only station in the chat

During an active contest, messages, sked requests, frequency information and band changes arrive continuously. The task is to identify which part of that traffic matters now, which candidate should be monitored and which contact is better scheduled for later.

Observe

Messages, locators, detected frequencies and known band activity are assigned to stations across as many as two ON4KST chat categories.

Evaluate

Direction, distance, worked status, NOT-QRV information, chat activity, sked context and aircraft scatter data feed filters and candidate scores.

Act

Candidates can be contacted, scheduled or monitored. Skeds remain visible, while supported loggers and station interfaces receive the information required for the next operating step.

Functions

One workflow, shared context

The individual functions are not isolated tools. They use the same station, message, band and timing information, so that a change in one part of the workflow can also affect filters, priorities and reminders.

Limits

A priority score is not a propagation forecast

KST4Contest can only evaluate the information it knows. Scores, AP windows, filters and path profiles support the operator's decision; they do not guarantee a contact. If the input data is incomplete or outdated, the result can be incomplete or outdated as well.

Project status

Stable for operation, Nightly for testing

KST4Contest is open-source software. The current stable release is the normal choice for contest operation. Nightly builds follow ongoing development and are useful when a particular fix or feature needs testing. A few minutes before a contest is not the ideal time to discover what changed.