APRS Packet Errors for LD3TO (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
20260208143051LD3TO>APOT30,WIDE2-2,qAR,LD2GI:!6024.76NS00959.72E#PHG3800 W2, NORn Tosevikseter
20260208143946LD3TO>APOT30,LD2GI*,WIDE2-1,qAR,LA4MIA-10:!6024.76NS00959.72E#PHG3800 W2, NORn Tosevikseter
20260208145936LD3TO>APOT30,WIDE2-2,qAR,LD2GI:!6024.76NS00959.72E#PHG3800 W2, NORn Tosevikseter
20260208152831LD3TO>APOT30,WIDE2-2,qAR,LD2GI:!6024.76NS00959.72E#PHG3800 W2, NORn Tosevikseter
20260208155720LD3TO>APOT30,WIDE2-2,qAR,LD2OH:!6024.76NS00959.72E#PHG3800 W2, NORn Tosevikseter
20260208162611LD3TO>APOT30,WIDE2-2,qAR,LD2GI:!6024.76NS00959.72E#PHG3800 W2, NORn Tosevikseter
20260208165502LD3TO>APOT30,WIDE2-2,qAR,LD2GI:!6024.76NS00959.72E#PHG3800 W2, NORn Tosevikseter
20260208172348LD3TO>APOT30,WIDE2-2,qAR,LD2GI:!6024.76NS00959.72E#PHG3800 W2, NORn Tosevikseter
20260208175240LD3TO>APOT30,WIDE2-2,qAR,LD2GI:!6024.76NS00959.72E#PHG3800 W2, NORn Tosevikseter
20260208182127LD3TO>APOT30,WIDE2-2,qAR,LD2OH:!6024.76NS00959.72E#PHG3800 W2, NORn Tosevikseter
20260208185013LD3TO>APOT30,WIDE2-2,qAR,LD2OH:!6024.76NS00959.72E#PHG3800 W2, NORn Tosevikseter
20260208191906LD3TO>APOT30,WIDE2-2,qAR,LD2GI:!6024.76NS00959.72E#PHG3800 W2, NORn Tosevikseter
20260208201648LD3TO>APOT30,WIDE2-2,qAR,LD2GI:!6024.76NS00959.72E#PHG3800 W2, NORn Tosevikseter