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
20260311203207DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_270/00 g...t049r000p...P...h100b10163 Lux:0 WX-Alfeld-OST
20260311204235DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_225/00 g...t049r000p...P...h100b10164 Lux:0 WX-Alfeld-OST
20260311205302DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t048r000p...P...h100b10165 Lux:0 WX-Alfeld-OST
20260312120250DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_225/00 g...t054r000p...P...h80b10217 Lux:1554 WX-Alfeld-OST
20260312121317DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_270/00 g...t054r000p...P...h80b10215 Lux:2433 WX-Alfeld-OST
20260312130535DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_225/00 g...t055r000p...P...h68b10205 Lux:1608 WX-Alfeld-OST
20260312143943DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t055r000p...P...h74b10198 Lux:1145 WX-Alfeld-OST
20260312145011DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t055r000p...P...h75b10198 Lux:1109 WX-Alfeld-OST
20260312163748DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t052r000p...P...h71b10198 Lux:389 WX-Alfeld-OST