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
20251107212528	DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_270/00 g...t043r000p...P...h100b10145 Lux:0 WX-Alfeld-OST
20251107215650	DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_315/00 g...t043r000p...P...h100b10144 Lux:0 WX-Alfeld-OST
20251107220717	DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_315/00 g...t043r000p...P...h100b10143 Lux:0 WX-Alfeld-OST
20251107224907	DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_000/00 g...t043r000p...P...h100b10143 Lux:0 WX-Alfeld-OST
20251108000219	DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_315/00 g...t042r000p...P...h100b10145 Lux:0 WX-Alfeld-OST
20251108010503	DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_000/00 g...t042r000p...P...h100b10146 Lux:0 WX-Alfeld-OST
20251108011530	DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_315/00 g...t042r000p...P...h100b10146 Lux:0 WX-Alfeld-OST