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
20250411200445	DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t053r000p...P...h100b10191 Lux:0 WX-Alfeld-OST
20250411202539	DO6GZ-WX>APRS,qAS,DO6GZ-L1:!5158.93N/00950.64E_.../00 g...t051r000p...P...h100b10191 Lux:0 WX-Alfeld-OST
20250411232325	DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t044r000p...P...h100b10193 Lux:0 WX-Alfeld-OST
20250412000514	DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t044r000p...P...h100b10192 Lux:0 WX-Alfeld-OST
20250412002609	DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t042r000p...P...h100b10190 Lux:0 WX-Alfeld-OST
20250412011826	DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_000/00 g...t042r000p...P...h100b10189 Lux:0 WX-Alfeld-OST