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
20260327003007DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t028r000p...P...h100b10211 Lux:0 WX-Alfeld-OST
20260327004034DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_000/00 g...t028r000p...P...h100b10211 Lux:0 WX-Alfeld-OST
20260327014318DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_135/00 g...t030r000p...P...h100b10215 Lux:0 WX-Alfeld-OST
20260327015345DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_135/00 g...t031r000p...P...h100b10215 Lux:0 WX-Alfeld-OST
20260327042008DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_045/00 g...t034r000p...P...h100b10225 Lux:0 WX-Alfeld-OST
20260327043036DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t034r000p...P...h100b10226 Lux:0 WX-Alfeld-OST
20260327052253DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t033r000p...P...h100b10232 Lux:56 WX-Alfeld-OST
20260327054348DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_135/00 g...t034r000p...P...h100b10234 Lux:127 WX-Alfeld-OST