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
20251014043944	DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_000/00 g...t049r000p...P...h100b10273 Lux:0 WX-Alfeld-OST
20251014064514	DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_315/00 g...t051r000p...P...h100b10273 Lux:223 WX-Alfeld-OST
20251014072704	DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_315/00 g...t052r000p...P...h100b10272 Lux:399 WX-Alfeld-OST
20251014080854	DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_045/00 g...t052r000p...P...h100b10272 Lux:550 WX-Alfeld-OST
20251014081922	DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_000/00 g...t052r000p...P...h100b10272 Lux:645 WX-Alfeld-OST
20251014112737	DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_270/00 g...t055r000p...P...h100b10267 Lux:691 WX-Alfeld-OST
20251014125119	DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_135/00 g...t056r000p...P...h100b10264 Lux:969 WX-Alfeld-OST
20251014150716	DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_135/00 g...t057r000p...P...h100b10259 Lux:528 WX-Alfeld-OST
20251014152811	DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_135/00 g...t057r000p...P...h100b10258 Lux:102 WX-Alfeld-OST