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
20260317204932DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t046r000p...P...h100b10258 Lux:0 WX-Alfeld-OST
20260317205959DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t046r000p...P...h100b10259 Lux:0 WX-Alfeld-OST
20260318024502DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t034r000p...P...h100b10275 Lux:0 WX-Alfeld-OST
20260318041909DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_.../00 g...t031r000p...P...h100b10287 Lux:0 WX-Alfeld-OST
20260318064533DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t037r000p...P...h100b10302 Lux:1517 WX-Alfeld-OST
20260318091159DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_000/00 g...t051r000p...P...h62b10308 Lux:1108 WX-Alfeld-OST