APRS Packet Errors for XE2MFT-1 (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
20260208152615XE2MFT-1>APOT21,WIDE2-2,qAR,XE2MFT-2:!2340.39N/10347.70W# 14.0V 15C RED NACIONAL APRS XE PAPANTON
20260208162616XE2MFT-1>APOT21,WIDE2-2,qAR,XE2MFT-2:!2340.39N/10347.70W# 14.0V 17C RED NACIONAL APRS XE PAPANTON
20260208172616XE2MFT-1>APOT21,WIDE2-2,qAR,XE2MFT-2:!2340.39N/10347.70W# 14.0V 18C RED NACIONAL APRS XE PAPANTON
20260208182617XE2MFT-1>APOT21,WIDE2-2,qAR,XE2MFT-2:!2340.39N/10347.70W# 14.0V 20C RED NACIONAL APRS XE PAPANTON
20260208192617XE2MFT-1>APOT21,WIDE2-2,qAR,XE2MFT-2:!2340.39N/10347.70W# 14.0V 22C RED NACIONAL APRS XE PAPANTON
20260208202619XE2MFT-1>APOT21,XE1IFV-1*,WIDE2-1,qAR,XE1IFV-10:!2340.39N/10347.70W# 14.0V 23C RED NACIONAL APRS XE PAPANTON