Find the Worst Hour in Your Log and Learn From It

November 21, 20268 min readContest statistics
Find the Worst Hour in Your Log and Learn From It

Short answer: Every contest has a worst hour: the lowest rate while you were operating, the hour with the most errors or the hour where something went wrong. Find it in the hour-by-hour table, check what you were doing, separate causes you can change from causes you cannot, and write down one specific action for next time. Do not look only at the lowest number: compare it with the hours before and after, and with the same hour in earlier years. One honest look at the weakest hour often gives a larger gain than polishing the best one.

Why the worst hour is worth your time

After a contest most people look at their best hour: the peak rate, the lucky run, the pileup that never ended. It feels good, and it is useful as a benchmark, but it rarely tells you what to change. The worst hour is different. It is the point where something went wrong, and in many cases the same thing goes wrong again next year if nobody looks at it.

A weak hour is not always a failure. Conditions can be poor, the band can be closed or a break can be planned. The task is to separate those hours from the ones where you lost rate because of a choice, a fault or fatigue. That separation is the first useful result of the review, and it needs only the data you already have.

Find it in the hourly table

Open the hour-by-hour table of your log, in your logger or in a log report. It lists, for each hour, the QSOs, the bands, often the multipliers and sometimes the points. Mark the hours with the lowest QSO count while you were operating. Do not include hours with planned breaks or hours when you slept, because they say nothing about performance. The article about hour-by-hour analysis explains how to read the table, and off times and breaks in statistics shows how to separate them.

Look at three hours in a row: the one before, the weak one and the one after. A dip in the middle of two good hours has a different cause from three weak hours in a row. A dip may point to a fault or a decision, and a long weak stretch points to conditions or fatigue. The shape tells you where to look.

Ask what you were doing

Next, reconstruct the hour. Look at the log lines for that period: which band, which frequency, how many QSOs were runs and how many were search and pounce. Check your notes, if you made any, and think about what happened around you. Was there a technical fault, a meal, a visitor, a call from outside? Did you change bands several times? Did you spend a long time looking for a multiplier?

It helps to write one sentence about the cause. If you cannot write it, say so, and note what additional data would help next time. The article on marking moments during the contest suggests how to make the reconstruction easier.

Compare with other hours and other years

A single number is hard to interpret. Compare the weak hour with the average of the contest, and with the same hour in earlier years, if you have those logs. If the same hour is weak every year, the cause is likely structural: a band that is always closed then, or a habit of taking a break at that time. If it is weak only this year, look for a one-time cause.

The comparison with other years is one of the best uses of a saved history. A log report that compares your log with your previous years makes it quick, and the article on comparing contest results across years shows what to look at. Check whether conditions were different, using the notes in solar flux and propagation, before you blame yourself.

Errors as well as rate

The worst hour in terms of rate is not always the worst in terms of quality. Look also at the hour with the most errors, if you have a report that flags them. Errors cluster in tired hours, in the night, after a long run and in hours with poor signals. An hour with a good rate and many busted calls can cost more than an hour with a low rate and clean QSOs.

If your log report lists flagged QSOs with their times, group them by hour. A hump in the middle of the night or in the last hours tells you where to protect your accuracy, perhaps with a break, a slower speed or a stricter rule about repeats. The articles on fatigue and errors by hour and night hours and logging errors explain the pattern.

Turn the answer into one action

Do not leave the review with a general feeling. Write one specific action for the next contest. Good actions are small and checkable: start the planned break at a fixed time, move to 15 metres earlier in the afternoon, prepare the antenna for the second night, check the noise level before the start, shorten the CQ message. If the cause was outside your control, write that too, and move on without guilt.

  1. Name the hour, the band and the rate.
  2. Write the cause in one sentence, or write that you do not know.
  3. Decide whether it can be changed.
  4. Write one action, with a date or a place where it fits in the preparation.
  5. Check the same hour next time.

Over a few contests the list of actions grows into a personal checklist, and the weak hours become fewer and shallower.

An example of a weak hour explained

Take a station whose hourly table shows 62 QSOs in most afternoon hours, but only 21 between 15:00 and 16:00 UTC on the second day. The hours before and after are normal, so the dip is local. Looking at the log lines for that hour shows that the station moved from 20 to 15 metres three times and made most of the QSOs by search and pounce. The notes say that the 20-metre run frequency was taken over by a strong station, and the operator did not want to give it up, then tried twice to come back. The cause is clear: a contested frequency and indecision, not poor conditions.

The action follows directly. Next time, decide in advance how long to defend a frequency, and move to a clean one after a fixed number of minutes without a rate. The station writes this as a rule in its contest notes, and in the next contest the same hour does not repeat the dip. The numbers in the example are invented, but the pattern is typical: a weak hour that looks mysterious in the table becomes simple when the log lines and the notes are read together.

A second example is a dip that shows no technical cause and no change of band. Then the log lines may show a long series of slow QSOs with several repeats, which points to fatigue, and the action is a short rest before the hour, not more effort during it. In both cases the review is cheap, and it replaces a vague feeling with a plan.

Keep the weak hours in perspective

Finally, remember that every contest has weak hours, and that the best operators have them too. The aim is not an even rate, which is unrealistic, but a rate that matches the conditions and the plan. Do not let the review spoil the pleasure of the contest. A short, honest look, an action and a break from the numbers is the healthiest way to use statistics.

Do not forget the second worst

When the worst hour is explained, look at the second and third. Sometimes the worst hour has a special cause, such as a fault, and the next ones show a more common pattern. It is useful to see both, because the special cause is a thing to prevent, while the pattern is a thing to plan around. A short table with three rows, the hour, the cause and the action, is enough for a personal record.

Share the result with a friend or a club if you like. A group that looks at weak hours together can find patterns that one person misses, and the talk is a good way to spend an evening after a contest. For ideas on the follow-up, see the post-contest review routine.

Related reading

The bottom line

The worst hour in your log is a free lesson. Find it, rebuild what happened, compare it with other hours and years, look at the errors too and write one action for the next contest. You can read how a report presents hourly statistics and flagged QSOs in the FAQ and on the contests page.

FAQ

Should I count hours when I took a break?

No. Exclude planned breaks and sleep, because they do not describe your operating.

What if the worst hour was caused by conditions?

Then write that, check whether other years show the same, and consider whether another band or plan would have been better.

Is the lowest rate always the worst hour?

Not always. An hour with a good rate but many errors can be worse. Look at both rate and quality.

How many hours should I analyse?

Start with the worst one, then the second and third. More than that is rarely needed.

Do I need special software?

No. An hourly table from your logger or a log report is enough, together with your notes.

#Contest Goals#Contest Statistics#Hour-by-Hour Analysis#Post-Contest Review#Rates
Check your contest log before you submit it.Check. Analyse. Improve your contest log every year.
Start checking

More from the blog

All articles →
Also from LY4A · free

Never miss the DX you are waiting for.

LY4A DX Reminder. Tell it which callsign you are waiting for, on which bands and in which mode. It watches five DX clusters in the background and raises a real alarm the moment that callsign shows up — even while your phone is silenced.

  • Free — no ads, no account
  • DXScape, DXSummit, DXHeat, PSK Reporter, RBN
  • 160 m to 70 cm · CW, SSB, FT8, FT4, RTTY
  • iPhone, Android, Windows and Mac

ly4a.com ↗

Made by the same team

More tools from our team

Built by Internet Solutions. Each one saves you time in a different way.