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
20260208130620LD7TS>APOT30,UGWSYY-13,qAR,LD7TG:!6302.46NL01018.16E# 13.7V 33C
20260208133649LD7TS>APOT30,UGWSYY-13,qAR,LD7TG:!6302.46NL01018.16E# 13.7V 32C
20260208140717LD7TS>APOT30,UGWSYY-13,qAR,LD7TG:!6302.46NL01018.16E# 13.7V 31C
20260208143745LD7TS>APOT30,UGWSYY-13,qAR,LD7TG:!6302.46NL01018.16E# 13.7V 31C
20260208150811LD7TS>APOT30,UGWSYY-13,qAR,LD7TG:!6302.46NL01018.16E# 13.7V 32C
20260208153836LD7TS>APOT30,UGWSYY-13,qAR,LD7TG:!6302.46NL01018.16E# 13.6V 34C
20260208160904LD7TS>APOT30,UGWSYY-13,qAR,LD7TG:!6302.46NL01018.16E# 13.7V 31C
20260208163933LD7TS>APOT30,UGWSYY-13,qAR,LD7TG:!6302.46NL01018.16E# 13.7V 31C
20260208170959LD7TS>APOT30,UGWSYY-13,qAR,LD7TG:!6302.46NL01018.16E# 13.7V 31C
20260208174027LD7TS>APOT30,UGWSYY-13,qAR,LD7TG:!6302.46NL01018.16E# 13.7V 31C
20260208181058LD7TS>APOT30,UGWSYY-13,qAR,LD7TG:!6302.46NL01018.16E# 13.7V 31C
20260208184125LD7TS>APOT30,UGWSYY-13,qAR,LD7TG:!6302.46NL01018.16E# 13.7V 32C