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
20251208072352DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_090/00 g...t053r000p...P...h100b10139 Lux:33 WX-Alfeld-OST
20251208075514DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_.../00 g...t053r000p...P...h100b10141 Lux:158 WX-Alfeld-OST
20251208081609DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_270/00 g...t054r000p...P...h100b10142 Lux:228 WX-Alfeld-OST
20251208093950DO6GZ-WX>APRS,qAO,DL8KM-13:!5158.93N/00950.64E_270/00 g...t055r000p...P...h100b10148 Lux:862 WX-Alfeld-OST
20251208095017DO6GZ-WX>APRS,qAO,DL8KM-13:!5158.93N/00950.64E_315/00 g...t055r000p...P...h100b10150 Lux:814 WX-Alfeld-OST
20251208104235DO6GZ-WX>APRS,qAO,DL8KM-13:!5158.93N/00950.64E_225/00 g...t056r000p...P...h100b10145 Lux:956 WX-Alfeld-OST
20251208114520DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_270/00 g...t057r000p...P...h100b10143 Lux:1399 WX-Alfeld-OST
20251208121643DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t057r000p...P...h100b10140 Lux:775 WX-Alfeld-OST