APRS Packet Errors for SM4JAY-12 (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
20260209091516SM4JAY-12>APRSGW,TCPIP*,qAR,SM4JAY-12:!6052.38N/01322.97E#Meshcom test/B=100/A=001270
20260209094516SM4JAY-12>APRSGW,TCPIP*,qAR,SM4JAY-12:!6052.38N/01322.97E#Meshcom test/B=026/A=001270
20260209101517SM4JAY-12>APRSGW,TCPIP*,qAR,SM4JAY-12:!6052.38N/01322.97E#Meshcom test/B=031/A=001270
20260209104517SM4JAY-12>APRSGW,TCPIP*,qAR,SM4JAY-12:!6052.38N/01322.97E#Meshcom test/B=031/A=001270
20260209111517SM4JAY-12>APRSGW,TCPIP*,qAR,SM4JAY-12:!6052.38N/01322.97E#Meshcom test/B=100/A=001270
20260209114517SM4JAY-12>APRSGW,TCPIP*,qAR,SM4JAY-12:!6052.38N/01322.97E#Meshcom test/B=041/A=001270
20260209121517SM4JAY-12>APRSGW,TCPIP*,qAR,SM4JAY-12:!6052.38N/01322.97E#Meshcom test/B=039/A=001270
20260209124517SM4JAY-12>APRSGW,TCPIP*,qAR,SM4JAY-12:!6052.38N/01322.97E#Meshcom test/B=022/A=001270
20260209131517SM4JAY-12>APRSGW,TCPIP*,qAR,SM4JAY-12:!6052.38N/01322.97E#Meshcom test/B=100/A=001270
20260209134517SM4JAY-12>APRSGW,TCPIP*,qAR,SM4JAY-12:!6052.38N/01322.97E#Meshcom test/B=100/A=001270
20260209141517SM4JAY-12>APRSGW,TCPIP*,qAR,SM4JAY-12:!6052.38N/01322.97E#Meshcom test/B=100/A=001270
20260209144517SM4JAY-12>APRSGW,TCPIP*,qAR,SM4JAY-12:!6052.38N/01322.97E#Meshcom test/B=027/A=001270