APRS Packet Errors for ZL2BAU (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
20250913023716ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *130237z0000.00NS00000.00W0
20250913030229ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *130302z0000.00NS00000.00W0
20250913033413ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *130334z0000.00NS00000.00W0
20250913040159ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *130401z0000.00NS00000.00W0
20250913042439ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *130424z0000.00NS00000.00W0
20250913044844ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *130448z0000.00NS00000.00W0
20250913051539ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *130515z0000.00NS00000.00W0
20250913054524ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *130545z0000.00NS00000.00W0
20250913061651ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *130616z0000.00NS00000.00W0
20250913063641ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *130636z0000.00NS00000.00W0
20250913070302ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *130703z0000.00NS00000.00W0
20250913072849ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *130728z0000.00NS00000.00W0
20250913075510ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *130755z0000.00NS00000.00W0