APRS Packet Errors for DO6GZ-WX (last 24 hours)

This table contains packets in which findU has detected an error. This is an automated system, no manual checking of these packets has been done. Most common cause of this is mistakes in entering the latitude/longitude into hard-coded digis, or positions of 0/0. If packets of yours appear here, and you have looked at it carefully and cannot find the error, look again. I've been watching these error messages in my log, and believe my parser is reasonably correct. Go get the APRS spec to be sure. If you have done that, and are CERTAIN the packet is a legal APRS packet, then it is possible that there is an error in my my parser. Only email me if you are absolutely, positively certain...ask yourself, would I bet $100!

time (UTC)Packet
20260401162657DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t051r000p...P...h70b10239 Lux:845 WX-Alfeld-OST
20260401174009DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t048r000p...P...h85b10237 Lux:188 WX-Alfeld-OST
20260401180105DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t045r000p...P...h100b10239 Lux:37 WX-Alfeld-OST
20260402090519DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_225/00 g...t050r000p...P...h100b10185 Lux:1156 WX-Alfeld-OST
20260402103926DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_270/00 g...t054r000p...P...h62b10175 Lux:1245 WX-Alfeld-OST
20260402141905DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_090/00 g...t057r000p...P...h43b10157 Lux:1627 WX-Alfeld-OST