APRS Packet Errors for LD6SG (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
20260208162643	LD6SG>APOT30,WIDE2-2,qAR,LA4YKA-10:!6235.77NL00854.35E#PHG20001/1100Moh Sunndal
20260208165642	LD6SG>APOT30,WIDE2-2,qAR,LA4YKA-10:!6235.77NL00854.35E#PHG20001/1100Moh Sunndal
20260208172643	LD6SG>APOT30,WIDE2-2,qAR,LA4YKA-10:!6235.77NL00854.35E#PHG20001/1100Moh Sunndal
20260208175642	LD6SG>APOT30,WIDE2-2,qAR,LA4YKA-10:!6235.77NL00854.35E#PHG20001/1100Moh Sunndal
20260208182643	LD6SG>APOT30,WIDE2-2,qAR,LA4YKA-10:!6235.77NL00854.35E#PHG20001/1100Moh Sunndal
20260208185643	LD6SG>APOT30,WIDE2-2,qAR,LA4YKA-10:!6235.77NL00854.35E#PHG20001/1100Moh Sunndal
20260208192644	LD6SG>APOT30,WIDE2-2,qAR,LA4YKA-10:!6235.77NL00854.35E#PHG20001/1100Moh Sunndal
20260208195644	LD6SG>APOT30,WIDE2-2,qAR,LA4YKA-10:!6235.77NL00854.35E#PHG20001/1100Moh Sunndal
20260208202645	LD6SG>APOT30,WIDE2-2,qAR,LA4YKA-10:!6235.77NL00854.35E#PHG20001/1100Moh Sunndal
20260208205645	LD6SG>APOT30,WIDE2-2,qAR,LA4YKA-10:!6235.77NL00854.35E#PHG20001/1100Moh Sunndal
20260208212645	LD6SG>APOT30,WIDE2-2,qAR,LA4YKA-10:!6235.77NL00854.35E#PHG20001/1100Moh Sunndal
20260208215645	LD6SG>APOT30,WIDE2-2,qAR,LA4YKA-10:!6235.77NL00854.35E#PHG20001/1100Moh Sunndal