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
20251015094534	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 150945z0000.00NS00000.00W0
20251015100922	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 151009z0000.00NS00000.00W0
20251015103236	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 151032z0000.00NS00000.00W0
20251015110710	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 151107z0000.00NS00000.00W0
20251015113206	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 151132z0000.00NS00000.00W0
20251015115918	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 151159z0000.00NS00000.00W0
20251015122414	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 151224z0000.00NS00000.00W0
20251015124910	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 151249z0000.00NS00000.00W0
20251015131804	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 151318z0000.00NS00000.00W0
20251015134550	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 151345z0000.00NS00000.00W0
20251015141518	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 151415z0000.00NS00000.00W0
20251015144503	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 151445z0000.00NS00000.00W0
20251015151414	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 151514z0000.00NS00000.00W0