Logging Amateur Radio Contacts Accurately Is Complicated

Logbook of the World

Let’s start with the Big Kahuna, ARRL’s Logbook of the World, which as I write this, has been down two weeks with no estimate time of recovery or useful detail other than:

2024-05-22 (a week after the outage): We have heard from many LoTW® users, asking about the status of the service and its data. This is not an LoTW server issue, and LoTW data is secure.
But what is the issue, and more importantly, when do you think it will it be resolved?

LotW conceptual overview

The model is logically represented by the image below where there are certificates used to “sign” the log as authentic (and upload it to LoTW and QRZ), and station locations with the specific location information I’ve operated from.

A block diagram showing logical elements for certificates and station locations in Logbook of the World's TQSL software.

Specifically, for my primary call sign, WT8P, I have multiple station locations that get set with the grid, ITU zone, CQ zone, state, county and, if applicable, National Park.

Getting your first certificate is a process beyond the scope of this discussion, so I’ll assume everyone has at least the first. For the conterminous US, I can use WT8P. However, if I want to be accurate, I’ll should create a station location in TQSL to note each location’s grid, county, state, ITU Zone, CQ Zone and, if applicable, park and (Island On The Air) designation. In the screenshot below, I had done these for Field Day, three US POTA sites (before K-0001 was renamed US-0001), and my home:

This diagram is showing multiple stations I've set up for my primary call sign.
Multiple station locations set up for primary call sign, WT8P

Create a station location

If I were going to operate in a new park, I simply Add Station Location in TQSL and fill out the information. For example, suppose I’m headed to Manhattan Project National Historical park in Los Alamos county, New Mexico. I’d look up some of the information on Parks on the Air, then fill in the details in TQSL using my WT8P call sign/certificate:

When I log these, I’d choose this “station” so anyone who worked me would then get credit for New Mexico. This is the step that most POTA folks are omitting, if they log at all. Ideally, they’d create a “station” for every park activated, then upload the logs using this as the reference.

Operating outside of your “DXCC” entity? Request a certificate

Things get a little more interesting when I operate outside of the conterminous United States. During my trip to the Canadian Maritimes, I planned to operate in Nova Scotia, New Brunswick and Prince Edward Island. Because Canada and the US have reciprocal operation privileges, there was no specific license or permit required, but I was obliged to identify as WT8P/VE1, WT8P/VE9 and WT8P/VY2, respectively. To log them accurately, I request a new certificate for each in the TQSL program. For the first four certificates one has, the request is handled via an auto-responder. I promptly received the certificate that I could import to TQSL. (For subsequent certificate requests, there is a delay as someone has to approve their creation. Thus /VE4, /VE5, /VE6, /VE7 had a three-day delay. Not a big deal.) Adding Iceland (TF/WT8P) and, last month, Faroe Islands (OY/WT8P) was the same process.

Screenshot of TQSL showing several certificates needed to "sign logs" with Logbook of the World.

OY/WT8P - Faroe Islands
TF/WT8P - Iceland
WT8P (my primary US call sign)
Several for provinces in Canada

One caveat when creating certificates: Do not set a password. This will just add an unnecessary and often confusing step in your process. We’re dealing with QSL logging, not securing Fort Knox, so one is overkill for most purposes.

Adding a new station location with a new certificate

Once I have a certificate for an entity, the process for adding a station location is the same. For example, if I activate the lone POTA in the Faroe Islands, I use my OY/WT8P call sign and fill out the information:


The other important site is QRZ.com since it’s very common and can do data interchange with Logbook of the World. Specially, any LoTW confirmations count as QRZ confirmations, but not the opposite. Its barrier to entry is lower, can be used as a call sign lookup, and there’s a separate set of awards one can work for.

As far as I can tell, it is perfectly fine importing the Logbook of the World data as it stands. Thus, you don’t explicitly need to do anything to your profile for a new park on the air other than log it with the information you have. However, because QRZ is often a lookup source, and seems to default to a single profile, this will generate a lot of discontinuities that affect other users.

Add the special suffix/prefix:

There’s no special setup for roaming station location, but if you have additional certificates, there are a few steps. First, navigate to the manager section, and add the secondary call sign. For example for the Faroe Islands, I will use a DX prefix of OY/.

One thing to be aware of is when you do this, it’s broadcast to others, which is not necessarily a bad thing, just surprising. Shortly after creating this, I received a request for info for the DX Newsletter as well as an offer from someone to manage paper QSLs.

Add contact information

It will then send you to another page with call sign information. I didn’t screenshot this the first time, but it’s identical to what I see on edit. Omitting the personal information (my name, address, email):

It should now appear in the Secondary Callsigns block of the User account information.

Add logbook start and stop dates

Before the “Logbook” is available in QRZ, you will also need to specify some information. I picked the same start date that I used for the certificate. For the end date, it seems any date after the time there is fine, so I picked a sufficiently far in the future 2043. I’ve also filled in the various zones, grid, and IOTA blocks used for QRZ’s purposes – most of these are information that we had from TQSL earlier.

This is a detailed dialog where one specifies the start- and stop-dates for a particular call sign (OY/WT8P) as well as the geographical characteristics.

Add your LoTW certificate

Finally, to enable data exchange with Logbook of the World, you’ll need to upload your certificate on the specific logbook page. In the drop-down, I would select OY/WT8P Logbook. On the bottom is this box:

Logbook of the World Import/Export - this is the part where I upload my certificates.

Because Logbook of the Web is currently Tango Uniform (“tits up” aka “dead”), I can’t demonstrate this step easily, but the document on QRZ is surprisingly useful. But briefly, in TQSL, one exports the certificate as a *.P12 file. This is then imported into QSL.


I will come out and just say that eqsl.cc is frustrating for the Parks on the Air user or any temporary operation. While its configuration section supports the concept of station locations, it disallows any temporal overlap. Rather, one has to chain together entries with a call sign existing in a specific location (county, state, country, and grid square) during a period of time. In other words, every time I did a POTA, I’d have to create a new entry and simultaneously expire my home location, then repeat it when back home.

eQSL is reporting an error that the thing I want to do - have a call sign be able to exist in multiple places, but select the place -- is not supported

The same rigid data structure applies to DX entities. When I was creating my /VE1 so I could upload the logs, I mistyped the grid and it rejected all of the uploaded QSLs. Because you cannot edit a location, I had to expire the existing /VE1, create a new one (with the matching grid) and re-upload those call signs.

That is too much busy-work. So, I apologize if any of you happen to be using eQSL.cc for awards, you’re going to get what you get.


After getting so frustrated with eQSL.cc, I was pleased that Clublog is very easy. Click on Settings -> “Callsigns” and add your new call sign:

When uploading them, just specify which call sign the entries pertain to. Easy Peasy.

What about those other boxes?

If I’m doing a Parks on the Air activation, I can add additional call signs here.

Parks on the Air, adding additional call signs.

But for my primary, it’s a joy to use after wrestling with eQSL. I can upload an ADIF-formatted file (an XML-style format that can have arbitrary additional fields) from either the mobile app (Ham RS) or desktop (N1MM+), then load that directly to the site.

Parks on the Air Log upload
It should be this simple.

The lone SOTA (summits on the air) I did was Acadia National Park, and also accepts an ADIF. While the hiking up the peak appeals to me, I’m just not serious about it to warrant spending more time. I will occasionally work someone on SOTA and try to log a spot to the site if I can remember the URL.

If I’m doing a contest, I will also upload something called a Cabrillo-formatted file to the contest site so it “counts” for the other person. Cabrillo-formatted documents have a long preamble, though their actual “logs” are simple lines. I used to get really worried about getting the data correct, but now rely on the contesting program N1MM+ to just magically export one on command.

I’ll also post a summary to “3830scores,” which is a self-reported leader board, but is also useful for seeing how you did over time.

3830 Scores letting me compare how different years of the 7th area QSO party went.

The QRZCQ block is something I used when I first started out, but decided was largely a complete waste of time. I had found its data to be somewhat stale, but what drove me away was how terrible it was at removing duplicates from logs. I also didn’t see much in the way of other hams confirming contacts.

HamQTH, aka Ham365.net, has a log, but also provides some useful integration that lets you upload between sites.

1 thought on “Logging Amateur Radio Contacts Accurately Is Complicated”

Leave a Comment

Your email address will not be published. Required fields are marked *