APRS Packet Errors for LD5AG (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
20260209115141LD5AG>APOT21,WIDE2-1,qAO,LB6EH-10:!6028.40NL00517.60E#12.9V 24C DO Geitanuken
20260209122205LD5AG>APOT21,WIDE2-1,qAO,LB6EH-10:!6028.40NL00517.60E#12.8V 24C DO Geitanuken
20260209125232LD5AG>APOT21,WIDE2-1,qAO,LB6EH-10:!6028.40NL00517.60E#12.8V 24C DO Geitanuken
20260209132257LD5AG>APOT21,WIDE2-1,qAO,LB6EH-10:!6028.40NL00517.60E#12.8V 25C DO Geitanuken
20260209135339LD5AG>APOT21,WIDE2-1,qAO,LB6EH-10:!6028.40NL00517.60E#12.8V 24C DO Geitanuken
20260209142422LD5AG>APOT21,WIDE2-1,qAO,LB6EH-10:!6028.40NL00517.60E#12.8V 24C DO Geitanuken
20260209145449LD5AG>APOT21,WIDE2-1,qAO,LB6EH-10:!6028.40NL00517.60E#12.8V 25C DO Geitanuken
20260209152516LD5AG>APOT21,WIDE2-1,qAO,LB6EH-10:!6028.40NL00517.60E#12.9V 24C DO Geitanuken
20260209155544LD5AG>APOT21,WIDE2-1,qAO,LB6EH-10:!6028.40NL00517.60E#12.8V 24C DO Geitanuken
20260209162615LD5AG>APOT21,WIDE2-1,qAO,LB6EH-10:!6028.40NL00517.60E#12.8V 24C DO Geitanuken
20260209165658LD5AG>APOT21,WIDE2-1,qAO,LB6EH-10:!6028.40NL00517.60E#12.8V 25C DO Geitanuken
20260209172738LD5AG>APOT21,WIDE2-1,qAO,LB6EH-10:!6028.40NL00517.60E#12.9V 25C DO Geitanuken