APRS Packet Errors for DO6GZ-WX (last 6 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
20240508144028DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_315/00 g...t066r014p...P...h34b10269 Lux:1351 WX-Alfeld-OST
20240508154314DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_045/00 g...t066r017p...P...h35b10269 Lux:1721 WX-Alfeld-OST
20240508160409DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_135/00 g...t067r003p...P...h32b10268 Lux:1490 WX-Alfeld-OST
20240508161436DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_315/00 g...t067r007p...P...h32b10267 Lux:1314 WX-Alfeld-OST
20240508163531DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_135/00 g...t066r009p...P...h32b10268 Lux:1236 WX-Alfeld-OST
20240508165626DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_135/00 g...t065r000p...P...h33b10268 Lux:1030 WX-Alfeld-OST
20240508193319DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_315/00 g...t053r010p...P...h64b10280 Lux:0 WX-Alfeld-OST