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
20260523124509	DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t083r000p...P...h47b10285 Lux:2525 WX-Alfeld-OST
20260523135822	DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_090/00 g...t084r000p...P...h46b10284 Lux:3216 WX-Alfeld-OST
20260523152202	DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_135/00 g...t083r000p...P...h49b10281 Lux:2242 WX-Alfeld-OST
20260523153230	DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_135/00 g...t082r000p...P...h49b10281 Lux:2280 WX-Alfeld-OST
20260523162448	DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_135/00 g...t082r000p...P...h47b10279 Lux:2430 WX-Alfeld-OST