Real-Time Contesting (RTC) is a new technology that enables contest adjudication in near real time. We have launched a new project: https://hamscore.com/.
It may look similar to our Online Scoring project, but there is one major difference:
No more submitting logs and waiting months for contest results. FINAL RESULTS are available just minutes after the contest ends!
During the contest, the system continuously collects log data directly from participants’ logging software. The server processes the submitted logs in real time and displays the calculated scores on a live scoreboard at https://hamscore.com/ .
After the contest ends, participants have a few minutes to make any necessary corrections. Once this period expires, the final results are published, and each participant receives a personal log-check report:
Currently we support the following contests:
CWOps mini – CWT – four CWT sessions on Wednesdays
ICWT MST– three MST sessions on Mondays
K1USN -every Friday and Monday
Weekly RTTY – every Thursday (NA) night
CWOps Open
NAQP
NA Sprint
HELVETIA
MN-QSO-PARTY
RTC Contest
and a few more
Setup RTC in N1MM+ log:
1. Get your RTC PIN first — otherwise, your score postings will be rejected.
You can find your RTC PIN on your profile page at HAMSCORE.com Profile Page (you must be logged in).
HAMSCORE.com uses the same user database as our other project, https://contestonlinescore.com/ or COSB , so please use your COSB credentials to log in.
2. In the N1MM+ “Configurer -> Score Reporting” check the “Include real time QSO data real time scoring” option
3. The new “Real Time QSO Reporting PIN” field will appear. Enter your PIN into that field
4. Click on the “OK” button on the bottom. The RTC PIN will be saved FOREVER !!! So you don’t need to enter it again after your logger starts
The logger accepts the only RTC PIN which is a number in the range of 10000 – 999999.
Be sure to enter the correct exchange information: your name and CWOps number. Otherwise, your exchange will be reported as an invalid “Name Exchange,” and your QSOs or probably the whole log may be marked as “Wrong Exchange,” making them invalid in your correspondents’ logs.
Setup RTC in DXLog:
The RTC option added to the DXLog starting from the version 2.6.8.
1. Click Commands|Live score|Setup|Live score server settings
Please note the RTC server (HAMSCORE.com) starts accepting logs 3 (Three) hours before a contest starts.
Please log in to HAMSCORE.com. On your personal profile page, you will find two links: one to your log-checking results and another to your Cabrillo log file.
During testing mode, the results are displayed instantly. In normal operation mode, only your submitted log will be available initially, without any checking results. The log-checking reports will be published after the contest status in the scoreboard header changes to: “Contest is finished. Results are published.”
Once the “Contest is finished. Results are published” status appears, the actual Score/QSO/Multiplier data will also become visible on the scoreboard. During the contest itself, only the RTC Score is displayed in real time. QSO and multiplier totals shown during the contest are based solely on the participants’ claimed data.
We designed the system this way to minimize the possibility of online assistance influencing operators during the contest.
The Contest Online ScoreBoard is not supporting the Russian DX Contest in 2024 due to the RDXC treating Ukrainian regions as Russian. They are clearly and deliberately violating International amateur radio agreements as this would promote illegal country or region activations in amateur radio terms:
Donetsk region
Lugansk region
Kherson region
Zaporozhye region
We see an obvious HAM Spirit violation by involving dirty politics into HAM Radio contesting.
The screenshot taken from the RDXC official website. The contest rules page (in Russian language):
Support for the RDXC will be re-evaluated next year.
We will not serve other Russian contests that claim the Ukrainian occupied territories as part of Russia. There will be no special message.
