STATISTICS FROM THE G4UCJ / G4001SWL LOGBOOK
Here are some statistics from my own logbook, now that I have over 240000 QSO’s and loggings (getting towards a quarter of a million loggings - that is crazy!), thought it may be interesting to see what I had been doing all this time!
For me, digital log keeping started back in July 1996, so that is the earliest data that appears in these tables. I have had a thin out and removed a lot of duplicates from the log, plus checked that all the DXCC are correct. Do not rely on your logging program to be 100% accurate, the country data that it uses needs to be carefully checked so that the correct DXCC is assigned to each callsign - this is especially true with the more unusual callsigns and special prefixes.
Some USA stations who have callsigns from various United States overseas territories have moved back to mainland USA but kept their overseas territories (US) callsign. An example of this is KH6M, a Hawaiian callsign, but the owner/operator and physical station is definitely resident on mainland USA. If he signed as W4/KH6M (I think he is resident in the #4 call area), there would be no confusion.
Luckily electronic logbooks that update their callsign databases regularly have most of these exceptions incorporated and will indicate the correct DXCC when entered. The FCC seem to have relaxed the necessity to identify the call area you are in. I have worked W6’s (CA) that have been in the #2 call area (NY, NJ, etc) and did not sign with the correct call area prefix (such as W2/W6xxx for example). I’ve been caught out in the past, by one or two of these overseas calls that were resident on the mainland - very frustrating!!
I believe there may still be some entries that need changing, which will be done when time allows. Sadly I do not have my logs or QSL cards from 1982-1996, as they were destroyed (without warning) by a third party, many years ago, much to my despair.
The statistics really needed a page of their own, so that they can be expanded and incorporate extra data.
Well, that was the plan. However, I had to stop using HRD Logbook (the last, free version that is), due to its incompatibility with Windows 10. There are new versions of HRD since it was purchased by a group of developers and I’m sure it is as good as ever, but I cannot justify spending around £100 to register and use it.
My new logging program (Logger32) does not provide the level of stats that HRD did, hence the reduction in detail.