Call search
ERROR: No data for call DR0ZD found in our database!
The call DR0ZD looks like it could be from
![](data:image/gif;base64,R0lGODlhEgAMAPQAAAAAAAcAAA4AAEkAAGEAAGMAAGkdAEA2AHxjAH1qAH9qAJUAAJYAAMUAAMcAAMkAAMsAANY6ANg7AIJtAIJuAPzKAPzMAP/XAP/YAP/ZAP/aAAAAAAAAAAAAAAAAAAAAACH5BAAAAAAALAAAAAASAAwAAAVQICCOZGmeaJoGQuu+sBAMzGIv9Y3nzFBAEIdwGHQUjYXCUNhoOJrQYcEQqVqvWIkBYal4v2CwBZHAXM7odBqTSGgw8LhcrkkcKJO8fr+nHEIAOw==)
Germany
If DR0ZD is your callsign and you would like to add your call to the
database, you can register here and add the data afterwards.However, here are advanced search results for DR0ZD:
Advanced search
Here you can search for a part of a callsign, wildcard character is "%".
Some examples: DO%, DL%BI, I%JUO, %CW, XXX
You may also search for names, cities, locators or a part of it
ERROR, nothing found or something wrong...
Site search
Search for DR0ZD. Search results: dr0zd : 1.
|
Results 1 - 1 of 1. (0.013 seconds)
|
... 10m 15 2017-05-23 15:49:06 -- IS0DCR 59 59 USB 0.028495 10m 15 2017-05-22 15:52:56 OK UF3A 59 59 USB 0.014222 20m 16 2017-05-12 13:48:35 -- PI4ZHE 53 53 FM 0.145475 2m 14 2017-05-09 18:57:44 -- DK5DQ 59 59 USB 0.144000 2m 14 2017-05-09 17:36:31 -- DR0ZD 59 59 USB 0.144000 2m 14 2017-05-09 17:36:14 -- DL0LEN 59 59 USB 0.144000 2m 14 2017-05-09 17:28:30 -- HA0SZK -14 -14 JT65 7.076000 40m 15 2017-05-09 17:19:00 -- US1MV -7 -10 JT65 7.076000 40m 16 2017-05-09 17:08:00 -- UA3GDJ -3 -17 JT65 7.076000 40m 16 ...
http://qrzcq.com/log/PD3HIM - 249376 bytes
Result pages: << prev
1
next >>