APRS Packet Errors for SA6LKX-99 (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
20260209145149SA6LKX-99>APRSGW,TCPIP*,qAR,SA6LKX-99:!5743.83N/01156.81E-Meshcom 4.0/B=100/A=000016
20260209152149SA6LKX-99>APRSGW,TCPIP*,qAR,SA6LKX-99:!5743.83N/01156.81E-Meshcom 4.0/B=100/A=000016
20260209155149SA6LKX-99>APRSGW,TCPIP*,qAR,SA6LKX-99:!5743.83N/01156.81E-Meshcom 4.0/B=036/A=000016
20260209162150SA6LKX-99>APRSGW,TCPIP*,qAR,SA6LKX-99:!5743.83N/01156.81E-Meshcom 4.0/B=100/A=000016
20260209165150SA6LKX-99>APRSGW,TCPIP*,qAR,SA6LKX-99:!5743.83N/01156.81E-Meshcom 4.0/B=031/A=000016
20260209172150SA6LKX-99>APRSGW,TCPIP*,qAR,SA6LKX-99:!5743.83N/01156.81E-Meshcom 4.0/B=031/A=000016
20260209175150SA6LKX-99>APRSGW,TCPIP*,qAR,SA6LKX-99:!5743.83N/01156.81E-Meshcom 4.0/B=028/A=000016
20260209182150SA6LKX-99>APRSGW,TCPIP*,qAR,SA6LKX-99:!5743.83N/01156.81E-Meshcom 4.0/B=100/A=000016
20260209185150SA6LKX-99>APRSGW,TCPIP*,qAR,SA6LKX-99:!5743.83N/01156.81E-Meshcom 4.0/B=029/A=000016
20260209192150SA6LKX-99>APRSGW,TCPIP*,qAR,SA6LKX-99:!5743.83N/01156.81E-Meshcom 4.0/B=027/A=000016
20260209195150SA6LKX-99>APRSGW,TCPIP*,qAR,SA6LKX-99:!5743.83N/01156.81E-Meshcom 4.0/B=023/A=000016
20260209202150SA6LKX-99>APRSGW,TCPIP*,qAR,SA6LKX-99:!5743.83N/01156.81E-Meshcom 4.0/B=023/A=000016