Seconds per QSO: Measuring Your Average QSO Time

November 19, 20268 min readContest statistics
Seconds per QSO: Measuring Your Average QSO Time

Short answer: A rate of 120 QSOs per hour sounds abstract, but it means one QSO every 30 seconds on average. Turning rates into seconds per QSO makes it easier to see where time goes: calling CQ, waiting, searching, repeating a callsign or tuning for the next station. Divide 3600 by the QSOs in an hour, compare the result for different hours and bands, and use it to decide what to shorten. The idea is simple, and the insight comes from comparing the numbers across the contest.

From rate to seconds

Everybody knows the rate in QSOs per hour, because loggers show it on the screen. The same number can be written differently. If you make 90 QSOs in an hour, the average time per QSO is 3600 divided by 90, which is 40 seconds. At 180 QSOs per hour it is 20 seconds, and at 60 per hour it is one minute. The average includes everything: the CQ you send, the pause while you listen, the exchange, the confirmation, the logging and any time you spend between QSOs.

Why bother? Because seconds are a more concrete unit than a rate. It is difficult to feel the difference between 100 and 110 QSOs per hour, but it is easy to imagine saving three seconds on every QSO. A rate is a result. Seconds per QSO point to the actions behind it, and actions are what you can change in the next contest.

Get the number from your own log

You do not need special equipment. Take the number of QSOs in a chosen period and divide the period in seconds by the number. For a full hour use 3600, for ten minutes 600. A sheet of rate by hour, such as the one in a log report, gives you the hourly numbers directly. Your logger’s rate meter gives short-term values, for example for the last ten or sixty minutes, which you can convert in the same way.

Work with full hours for a general picture and with shorter windows when you want to analyse something special, such as a pileup. Avoid windows that include a break, because off time makes the average meaningless. If you want to know more about the rate figures themselves, the article on contest rates explains 10-minute and 60-minute rates, and the one about the rate meter explains how the logger calculates them.

What the average hides

An average hides the shape. In a run, QSOs come in bursts: a few seconds each while a pileup lasts, then a gap while you call CQ with nobody answering. Forty seconds per QSO may be made of ten fast QSOs at 15 seconds and a long pause. In search and pounce the pattern is different: tuning, listening and waiting for a gap take most of the time, and the QSO itself is short.

That is why the average works best as a comparison tool, not as a verdict. Compare your own numbers in different conditions: run versus search and pounce, one band versus another, the first hour versus the last, day one versus day two. If the average time per QSO on 20 metres is half of that on 15, you know where the contest was won. If it doubles in the last four hours, you know where concentration or conditions fell away. Our article on run versus search and pounce shows how to split the two modes in the statistics.

Where the seconds go

Break a single QSO into parts and the opportunities appear. Take a typical run QSO: you send CQ, a station answers, you send the callsign back, they send the exchange, you confirm and log, and you call CQ again. Each part has a minimum length, but many have slack. A CQ message that is longer than necessary, a pause before the reply, a second repeat of the exchange that the other station did not need, and a slow keyboard entry can add several seconds each.

For repeats, the advice about partial callsign copies and about asking efficiently pays back twice: fewer busted calls and fewer lost seconds.

Speed is not the same as efficiency

Do not shorten the QSO at any cost. A QSO that is fast but wrong is worse than a slow one, because it costs the QSO and sometimes a penalty. If you reduce the seconds per QSO and the number of errors in your log increases, the net result is negative. Always read the two numbers together: the average time and the number of flagged QSOs after the contest. A good change reduces the first and keeps the second stable.

It is also true that the right speed depends on the conditions. In a strong pileup a very short exchange works, but on a weak band the extra repeat may be the right choice. A contester who adapts the length of the QSO to the signal is more efficient than one who uses one fixed rhythm at all times. The numbers will show you where that adaptation worked.

A worked example

Imagine a station that made 1,260 QSOs in 24 hours of operating, with two hours of off time. That is 22 operating hours, or 79,200 seconds, so the average is about 63 seconds per QSO. On the face of it this is a slow contest, but the hourly view tells a different story. On 20 metres in the afternoon the station made 140 QSOs in an hour, 26 seconds each. On 80 metres at night it made 40 QSOs in an hour, 90 seconds each. The overall average hides two very different kinds of hours.

Now the plan becomes specific. The station cannot make 80 metres faster by operating harder, because the band simply supports fewer calls at night. But it can ask whether the time on 80 metres was well spent. If each night QSO on 80 metres is a multiplier or a new country, the 90 seconds are worth it. If many of them are ordinary QSOs that could have been made on 20 metres in a third of the time, the schedule needs a change. Seconds per QSO do not give the answer; they ask the right question about the way time was used.

Use the same approach for single-band entries, where the choice of hours matters even more. A single-band station cannot move to another band, so the only variable is the way the hour is used. The seconds per QSO in the hours when a band is open and when it is nearly closed show the value of staying on the frequency, of calling CQ and of going searching for new stations.

A simple analysis you can do after a contest

  1. Copy the number of QSOs for each hour from the rate sheet of your log report.
  2. Calculate 3600 divided by that number for each hour, ignoring hours with a long break.
  3. Mark the three fastest and the three slowest hours and write down what you were doing in each: running, searching, which band.
  4. Do the same for each band, using the QSOs and the operating time on that band.
  5. Choose one change for the next contest, for example a shorter CQ on the band where you were slowest, and write it into your notes.

This takes half an hour, and it gives you a specific plan rather than a general wish to be faster. Compare the result with the hour-by-hour analysis of the same log to see the full picture.

Using last year’s numbers as a target

If you have the numbers from last year, they make a concrete target. Suppose your average time on 40 metres was 36 seconds in the night hours and you want to be at 32. That is not a dramatic change, but it adds up over many hours. A year-on-year comparison, such as the one described in comparing contest results across years, shows whether the change worked and whether it came with a higher error rate.

Keep the targets small and specific. One improvement per band is more realistic than a general promise to speed up, and it is easier to check in the next log. A log report that shows statistics for several years in one place is a convenient source of such numbers.

Related reading

The bottom line

Seconds per QSO is the same information as the rate, written in a way that points to actions. Calculate it from your log, compare runs, bands and hours, and choose one change for the next contest. Keep an eye on the error count, and do not trade accuracy for speed. If you want to see how a report presents your rates and bands, look at the sample on the contests and pricing pages and the FAQ.

FAQ

How do I convert QSOs per hour into seconds per QSO?

Divide 3600 by the number of QSOs in the hour. For example, 120 QSOs in an hour is 30 seconds per QSO.

Is a shorter time per QSO always better?

No. It is better only if the error rate stays the same. A fast but wrong QSO costs more than it saves.

Should I include breaks in the calculation?

No. Use hours without a long break, otherwise the average does not describe your operating.

Why is my time per QSO different on run and on search and pounce?

The two methods spend time in different places. Compare each against itself across bands and hours, not against each other.

Where do I find the hourly numbers?

In the hour-by-hour table of your log statistics, or in the rate display of your logging program.

#Contest Statistics#Hour-by-Hour Analysis#Rate Meter#Rates#Run vs Search and Pounce
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.