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
20250630194413	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 301944z0000.00NS00000.00W0
20250630201756	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 302017z0000.00NS00000.00W0
20250630204201	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 302042z0000.00NS00000.00W0
20250630211402	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 302114z0000.00NS00000.00W0
20250630213301	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 302133z0000.00NS00000.00W0
20250630215956	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 302159z0000.00NS00000.00W0
20250630223015	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 302230z0000.00NS00000.00W0
20250630225710	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 302257z0000.00NS00000.00W0
20250630232132	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 302321z0000.00NS00000.00W0
20250630234952	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 302349z0000.00NS00000.00W0
20250701001630	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 010016z0000.00NS00000.00W0
20250701004018	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 010040z0000.00NS00000.00W0
20250701010912	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 010109z0000.00NS00000.00W0