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
20251119174827DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_270/00 g...t036r002p...P...h100b10040 Lux:0 WX-Alfeld-OST
20251119210707DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_315/00 g...t037r001p...P...h100b10029 Lux:0 WX-Alfeld-OST
20251119211735DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_315/00 g...t037r002p...P...h100b10029 Lux:0 WX-Alfeld-OST
20251119220952DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_315/00 g...t037r000p...P...h100b10024 Lux:0 WX-Alfeld-OST
20251119223046DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_315/00 g...t037r000p...P...h100b10024 Lux:0 WX-Alfeld-OST
20251120035455DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_270/00 g...t033r000p...P...h100b10024 Lux:0 WX-Alfeld-OST
20251120045739DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_090/00 g...t033r000p...P...h100b10032 Lux:0 WX-Alfeld-OST
20251120064213DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_045/00 g...t033r000p...P...h100b10049 Lux:8 WX-Alfeld-OST
20251120073431DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_045/00 g...t034r000p...P...h100b10060 Lux:84 WX-Alfeld-OST
20251120074458DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_135/00 g...t034r000p...P...h100b10063 Lux:95 WX-Alfeld-OST