ad: dxeng
Please login help/register callsign: password: secure login
Database News Forums Swapmeet Resources Contact
 14:44:41 UTC 28 Nov 2014 
Advanced Search Current Hot Callsigns XML Logbook Data QSL ListMaker Database Downloads DX Spotting Network Ham Club Database QSL Corner Top Web Contacts Expired Callsigns QRZ's 1993 FCC Database Daily Update Reports Just Added Callsigns Database Help Forum
Amateur Radio News General Announcements Special Events, Contests, etc. Hamfests and Conventions Silent Keys Headlines
Forums Home Discussions, Editorials, Talk Technical Forums Logging and Contesting RV and Mobile Help Forums
Ham Radio Gear for Sale Ham Made Gear General Merchandise Swapmeet Hot List Ham to Ham References Stolen Radios, Scams and Rip-offs
Site Menu... Practice Amateur Radio Exams Amateur Radio Study Guides Online License Renewals License Wall Certificates Commercial Ham Radio Links DX Country Atlas Grid Mapper Ham Radio Trivia Quiz Life Member Honor Roll
Help Desk, for accounts, lost passwords, etc. Add your callsign to QRZ Subscription Services Users Help Forum Frequently Asked Questions - FAQ QRZ en Espanol Privacy Statement Advertise with QRZ List of Current Advertisers About QRZ Donate to QRZ Contact us
ad: L-HROutlet
ad: l-assoc
ad: l-rl
ad: l-WarrenG
ad: l-Waters
ad: l-Heil
ad: l-gcopper
ad: l-tentec
ad: l-innov

Login is required for additional detail.


Email: Login required to view

Ham Member Lookups: 33983


HRDLog.net QSOs worked:

The picture is of MT. Dominion about 25 miles NNW of my QTH.

Thanks for dropping by my QRZ page!


I seem to have trouble with LOTW indicating correct WAS status.  Example:

I worked N4UPX on 80 and 20 JT65.  The QSOs show up in the LOTW data base BUT my WAS status DOES NOT show that I have MS (N4UPX) on 80 or 20!  I wouldn't have even noticed EXCEPT that in BOTH cases MS is the last state I needed for that band/mode for WAS.

Also even though I have a JT65 WAS confirmed in LOTW on say 160M I still DO NOT show a DIG WAS confirmed for 160....there is a lot of that in LOTW.

In the first case the QSO mode in the data base seems OK..JT65 (DIG)....the mode DOESN'T say only DIG  which is a known ?problem? ?situation? in getting JT65 credit for a JT65 QSO logged only as a DIG QSO.

I can probably understand the DIG/JT65 issue but WHY the data base errors with properly logged QSOs?

Please email me at K7LFY@yahoo.com if you know why this happens and how to fix it. TNX  es 73.  Bob


I need ID, ME, MT, NV, RI, AND WY to complete my QRPP (<1W) JT65 WAS.  So if you see me in the waterfall PLEASE feel free to work me again!  I will be on JT9 also working a QRPP WAS there so please give my another call if you see me.  I am only half done there.....

TNX es 73

I have been a ham since 1960. I operate 160-2mostly CW but now also RTTY, JT 65 and JT9 and DM780 digtal modes. Chasing DX, QRPP, RTTY,  CW and some contesting are probably my favorite ham things.

I personally only use the electronic QSLing processes and that saves a ton of $USD$ - - - AND it is FAST! I usually upload to LoTW and eQSL almost immediately.

When you see your CALL above our QSO is already in eQSL(AG) and LoTW and HRDLog. Hopefully.

If you send me a paper QSL - I will send you back a paper QSL by return mail.

I now have some bureau QSLs to answer - please be patient.  AND Please start using LoTW, eQSL etc. if you aren't already!!!

If I am operating you will usually see my "ON AIR"sign in QRZ and the frequency at which I am operating.

CU on the air,



1439488 Last modified: 2014-11-14 15:14:37, 4076 bytes

Login Required

Login is required for additional detail.

Apply for a new Vanity callsign...

You must be logged in to file a report on this page

Please login now...

Currently updating logbook display.
ad: giga-db
Copyright © 2014 by QRZ.COM
Fri Nov 28 14:44:41 2014 UTC
CPU: 0.048 sec 39472 bytes mp