APRS Packet Errors for LZ1ZAF-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
20260209092726LZ1ZAF-12>APRSGW,TCPIP*,qAR,LZ1ZAF-12:!4208.30N/02447.52E#MeshCom GW/B=079/A=000531
20260209095741LZ1ZAF-12>APRSGW,TCPIP*,qAR,LZ1ZAF-12:!4208.30N/02447.52E#MeshCom GW/B=098/A=000531
20260209102801LZ1ZAF-12>APRSGW,TCPIP*,qAR,LZ1ZAF-12:!4208.30N/02447.52E#MeshCom GW/B=085/A=000531
20260209105816LZ1ZAF-12>APRSGW,TCPIP*,qAR,LZ1ZAF-12:!4208.30N/02447.52E#MeshCom GW/B=088/A=000531
20260209112829LZ1ZAF-12>APRSGW,TCPIP*,qAR,LZ1ZAF-12:!4208.30N/02447.52E#MeshCom GW/B=100/A=000531
20260209115844LZ1ZAF-12>APRSGW,TCPIP*,qAR,LZ1ZAF-12:!4208.30N/02447.52E#MeshCom GW/B=096/A=000531
20260209122859LZ1ZAF-12>APRSGW,TCPIP*,qAR,LZ1ZAF-12:!4208.30N/02447.52E#MeshCom GW/B=100/A=000531
20260209125914LZ1ZAF-12>APRSGW,TCPIP*,qAR,LZ1ZAF-12:!4208.30N/02447.52E#MeshCom GW/B=100/A=000531
20260209132929LZ1ZAF-12>APRSGW,TCPIP*,qAR,LZ1ZAF-12:!4208.30N/02447.52E#MeshCom GW/B=090/A=000531
20260209135944LZ1ZAF-12>APRSGW,TCPIP*,qAR,LZ1ZAF-12:!4208.30N/02447.52E#MeshCom GW/B=091/A=000531
20260209142956LZ1ZAF-12>APRSGW,TCPIP*,qAR,LZ1ZAF-12:!4208.30N/02447.52E#MeshCom GW/B=076/A=000531