APRS Packet Errors for LD9HN (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
20260208152035LD9HN>APTT4,LD9HS*,WIDE2-1,qAR,LA6GGA-10:!7041.46NL02340.29E#PHG4230 Hammerfest W3
20260208155033LD9HN>APTT4,LD9HS*,WIDE2-1,qAR,LA6GGA-10:!7041.46NL02340.29E#PHG4230 Hammerfest W3
20260208162029LD9HN>APTT4,LD9HS*,WIDE2-1,qAR,LA6GGA-10:!7041.46NL02340.29E#PHG4230 Hammerfest W3
20260208165027LD9HN>APTT4,LD9HS*,WIDE2-1,qAR,LA6GGA-10:!7041.46NL02340.29E#PHG4230 Hammerfest W3
20260208172023LD9HN>APTT4,LD9HS*,WIDE2-1,qAR,LA6GGA-10:!7041.46NL02340.29E#PHG4230 Hammerfest W3
20260208182017LD9HN>APTT4,LD9HS*,WIDE2-1,qAR,LA6GGA-10:!7041.46NL02340.29E#PHG4230 Hammerfest W3
20260208192012LD9HN>APTT4,LD9HS*,WIDE2-1,qAR,LA6GGA-10:!7041.46NL02340.29E#PHG4230 Hammerfest W3
20260208195009LD9HN>APTT4,LD9HS*,WIDE2-1,qAR,LA6GGA-10:!7041.46NL02340.29E#PHG4230 Hammerfest W3
20260208202006LD9HN>APTT4,LD9HS*,WIDE2-1,qAR,LA6GGA-10:!7041.46NL02340.29E#PHG4230 Hammerfest W3
20260208205003LD9HN>APTT4,LD9HS*,WIDE2-1,qAR,LA6GGA-10:!7041.46NL02340.29E#PHG4230 Hammerfest W3