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
20250711175122DO6GZ-WX>APRS,qAS,DO6GZ-L1:!5158.93N/00950.64E_270/00 g...t075r000p...P...h60b10170 Lux:4701 WX-Alfeld-OST
20250711203842DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_135/00 g...t066r000p...P...h100b10171 Lux:0 WX-Alfeld-OST
20250711213058DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_090/00 g...t065r000p...P...h100b10170 Lux:0 WX-Alfeld-OST
20250711215153DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_090/00 g...t064r000p...P...h100b10169 Lux:0 WX-Alfeld-OST
20250712010006DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_315/00 g...t062r000p...P...h100b10160 Lux:0 WX-Alfeld-OST
20250712025507DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_090/00 g...t061r000p...P...h100b10157 Lux:0 WX-Alfeld-OST
20250712043942DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_270/00 g...t060r000p...P...h100b10152 Lux:170 WX-Alfeld-OST
20250712045010DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_090/00 g...t060r000p...P...h100b10152 Lux:214 WX-Alfeld-OST
20250712052132DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_315/00 g...t060r000p...P...h100b10148 Lux:554 WX-Alfeld-OST
20250712085043DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_135/00 g...t065r000p...P...h100b10133 Lux:3545 WX-Alfeld-OST