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
20251105181103DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t051r000p...P...h100b10185 Lux:0 WX-Alfeld-OST
20251105211915DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_315/00 g...t044r000p...P...h100b10180 Lux:0 WX-Alfeld-OST
20251105212943DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_315/00 g...t044r000p...P...h100b10179 Lux:0 WX-Alfeld-OST
20251106025352DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t039r000p...P...h100b10162 Lux:0 WX-Alfeld-OST
20251106030419DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_135/00 g...t038r000p...P...h100b10161 Lux:0 WX-Alfeld-OST
20251106050947DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_315/00 g...t039r000p...P...h100b10155 Lux:0 WX-Alfeld-OST
20251106081802DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_000/00 g...t043r000p...P...h100b10146 Lux:676 WX-Alfeld-OST
20251106091020DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t048r000p...P...h100b10143 Lux:823 WX-Alfeld-OST
20251106114713DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_000/00 g...t057r000p...P...h100b10131 Lux:1005 WX-Alfeld-OST