APRS Packet Errors for LD3NF (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
20260208131219LD3NF>APOT30,LD3KS,WIDE2*,qAR,LD2GI:!6013.30N100934.02E#15C Fil-In, Norefjell
20260208134111LD3NF>APOT30,WIDE2-1,qAR,LD2GI:!6013.30N100934.02E#15C Fil-In, Norefjell
20260208141005LD3NF>APOT30,WIDE2-1,qAR,LD1FE:!6013.30N100934.02E#16C Fil-In, Norefjell
20260208143858LD3NF>APOT30,WIDE2-1,qAR,LD2GI:!6013.30N100934.02E#17C Fil-In, Norefjell
20260208150807LD3NF>APOT30,WIDE2-1,qAR,LD2GI:!6013.30N100934.02E#17C Fil-In, Norefjell
20260208160603LD3NF>APOT30,WIDE2-1,qAR,LD2OH:!6013.30N100934.02E#16C Fil-In, Norefjell
20260208163501LD3NF>APOT30,WIDE2-1,qAR,LD2OH:!6013.30N100934.02E#17C Fil-In, Norefjell
20260208170353LD3NF>APOT30,WIDE2-1,qAR,LD2OH:!6013.30N100934.02E#16C Fil-In, Norefjell
20260208173249LD3NF>APOT30,WIDE2-1,qAR,LD2OH:!6013.30N100934.02E#16C Fil-In, Norefjell
20260208180141LD3NF>APOT30,WIDE2-1,qAR,LD2OH:!6013.30N100934.02E#16C Fil-In, Norefjell
20260208183030LD3NF>APOT30,WIDE2-1,qAR,LD1FE:!6013.30N100934.02E#15C Fil-In, Norefjell