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
20260526073036DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_000/00 g...t081r000p...P...h70b10311 Lux:2936 WX-Alfeld-OST
20260526080159DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_135/00 g...t085r000p...P...h62b10309 Lux:2807 WX-Alfeld-OST
20260526081226DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_090/00 g...t082r000p...P...h84b10308 Lux:2877 WX-Alfeld-OST
20260526085417DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_090/00 g...t087r000p...P...h45b10305 Lux:3027 WX-Alfeld-OST
20260526091512DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t086r000p...P...h40b10304 Lux:3105 WX-Alfeld-OST
20260526093607DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t087r000p...P...h36b10302 Lux:4711 WX-Alfeld-OST
20260526102824DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t083r000p...P...h40b10296 Lux:1634 WX-Alfeld-OST
20260526121300DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t085r000p...P...h40b10285 Lux:1491 WX-Alfeld-OST
20260526123355DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t085r000p...P...h43b10282 Lux:1500 WX-Alfeld-OST