APRS Packet Errors for LD7TS (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
20260209092340LD7TS>APOT30,UGWSYY-13,qAR,LD7TG:!6302.46NL01018.16E# 13.7V 29C
20260209095412LD7TS>APOT30,UGWSYY-13,qAR,LD7TG:!6302.46NL01018.16E# 13.7V 31C
20260209102450LD7TS>APOT30,UGWSYY-13,qAR,LD7TG:!6302.46NL01018.16E# 13.7V 29C
20260209105515LD7TS>APOT30,UGWSYY-13,qAR,LD7TG:!6302.46NL01018.16E# 13.7V 29C
20260209112539LD7TS>APOT30,UGWSYY-13,qAR,LD7TG:!6302.46NL01018.16E# 13.7V 29C
20260209115604LD7TS>APOT30,UGWSYY-13,qAR,LD7TG:!6302.46NL01018.16E# 13.7V 29C
20260209122629LD7TS>APOT30,UGWSYY-13,qAR,LD7TG:!6302.46NL01018.16E# 13.7V 30C
20260209125654LD7TS>APOT30,UGWSYY-13,qAR,LD7TG:!6302.46NL01018.16E# 13.7V 30C
20260209132716LD7TS>APOT30,UGWSYY-13,qAR,LD7TG:!6302.46NL01018.16E# 13.7V 30C
20260209135744LD7TS>APOT30,UGWSYY-13,qAR,LD7TG:!6302.46NL01018.16E# 13.7V 31C
20260209142806LD7TS>APOT30,UGWSYY-13,qAR,LD7TG:!6302.46NL01018.16E# 13.7V 31C