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
20260208131736LZ1ZAF-12>APRSGW,TCPIP*,qAR,LZ1ZAF-12:!4208.30N/02447.52E#MeshCom GW/B=079/A=000531
20260208134754LZ1ZAF-12>APRSGW,TCPIP*,qAR,LZ1ZAF-12:!4208.30N/02447.52E#MeshCom GW/B=079/A=000531
20260208141809LZ1ZAF-12>APRSGW,TCPIP*,qAR,LZ1ZAF-12:!4208.30N/02447.52E#MeshCom GW/B=083/A=000531
20260208144823LZ1ZAF-12>APRSGW,TCPIP*,qAR,LZ1ZAF-12:!4208.30N/02447.52E#MeshCom GW/B=100/A=000531
20260208151838LZ1ZAF-12>APRSGW,TCPIP*,qAR,LZ1ZAF-12:!4208.30N/02447.52E#MeshCom GW/B=100/A=000531
20260208154853LZ1ZAF-12>APRSGW,TCPIP*,qAR,LZ1ZAF-12:!4208.30N/02447.52E#MeshCom GW/B=075/A=000531
20260208161912LZ1ZAF-12>APRSGW,TCPIP*,qAR,LZ1ZAF-12:!4208.30N/02447.52E#MeshCom GW/B=088/A=000531
20260208164927LZ1ZAF-12>APRSGW,TCPIP*,qAR,LZ1ZAF-12:!4208.30N/02447.52E#MeshCom GW/B=082/A=000531
20260208171940LZ1ZAF-12>APRSGW,TCPIP*,qAR,LZ1ZAF-12:!4208.30N/02447.52E#MeshCom GW/B=100/A=000531
20260208174956LZ1ZAF-12>APRSGW,TCPIP*,qAR,LZ1ZAF-12:!4208.30N/02447.52E#MeshCom GW/B=100/A=000531
20260208182011LZ1ZAF-12>APRSGW,TCPIP*,qAR,LZ1ZAF-12:!4208.30N/02447.52E#MeshCom GW/B=079/A=000531
20260208185026LZ1ZAF-12>APRSGW,TCPIP*,qAR,LZ1ZAF-12:!4208.30N/02447.52E#MeshCom GW/B=090/A=000531