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
20250823061957DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_090/00 g...t056r000p...P...h100b10175 Lux:635 WX-Alfeld-OST
20250823072242DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_.../00 g...t057r000p...P...h100b10178 Lux:1542 WX-Alfeld-OST
20250823074337DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_045/00 g...t058r000p...P...h100b10180 Lux:1544 WX-Alfeld-OST
20250823080432DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_225/00 g...t064r000p...P...h100b10177 Lux:4486 WX-Alfeld-OST
20250823091745DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_135/00 g...t059r000p...P...h100b10181 Lux:2414 WX-Alfeld-OST