APRS Packet Errors for OK1SLM-7 (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
20260209114802OK1SLM-7>APRSGW,TCPIP*,qAR,OK1SLM-7:!5045.51N/01518.24E#MeshCom#Libor/B=100/A=001804
20260209121817OK1SLM-7>APRSGW,TCPIP*,qAR,OK1SLM-7:!5045.51N/01518.24E#MeshCom#Libor/B=100/A=001804
20260209124832OK1SLM-7>APRSGW,TCPIP*,qAR,OK1SLM-7:!5045.51N/01518.24E#MeshCom#Libor/B=100/A=001804
20260209131847OK1SLM-7>APRSGW,TCPIP*,qAR,OK1SLM-7:!5045.51N/01518.24E#MeshCom#Libor/B=100/A=001804
20260209134902OK1SLM-7>APRSGW,TCPIP*,qAR,OK1SLM-7:!5045.51N/01518.24E#MeshCom#Libor/B=100/A=001804
20260209141921OK1SLM-7>APRSGW,TCPIP*,qAR,OK1SLM-7:!5045.51N/01518.24E#MeshCom#Libor/B=100/A=001804
20260209144940OK1SLM-7>APRSGW,TCPIP*,qAR,OK1SLM-7:!5045.51N/01518.24E#MeshCom#Libor/B=100/A=001804
20260209151955OK1SLM-7>APRSGW,TCPIP*,qAR,OK1SLM-7:!5045.51N/01518.24E#MeshCom#Libor/B=100/A=001804
20260209155010OK1SLM-7>APRSGW,TCPIP*,qAR,OK1SLM-7:!5045.51N/01518.24E#MeshCom#Libor/B=100/A=001804
20260209162025OK1SLM-7>APRSGW,TCPIP*,qAR,OK1SLM-7:!5045.51N/01518.24E#MeshCom#Libor/B=100/A=001804
20260209165040OK1SLM-7>APRSGW,TCPIP*,qAR,OK1SLM-7:!5045.51N/01518.24E#MeshCom#Libor/B=100/A=001804
20260209172051OK1SLM-7>APRSGW,TCPIP*,qAR,OK1SLM-7:!5045.51N/01518.24E#MeshCom#Libor/B=100/A=001804