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
20250417151251	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 171512z0000.00NS00000.00W0
20250417153804	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 171538z0000.00NS00000.00W0
20250417160459	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 171604z0000.00NS00000.00W0
20250417163137	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 171631z0000.00NS00000.00W0
20250417170247	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 171702z0000.00NS00000.00W0
20250417172203	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 171722z0000.00NS00000.00W0
20250417175148	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 171751z0000.00NS00000.00W0
20250417181900	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 171819z0000.00NS00000.00W0
20250417185044	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 171850z0000.00NS00000.00W0
20250417191813	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 171918z0000.00NS00000.00W0
20250417193820	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 171938z0000.00NS00000.00W0
20250417201220	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 172012z0000.00NS00000.00W0
20250417203750	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 172037z0000.00NS00000.00W0