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
20250531231647	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 312316z0000.00NS00000.00W0
20250531233910	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 312339z0000.00NS00000.00W0
20250601001145	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 010011z0000.00NS00000.00W0
20250601003857	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 010038z0000.00NS00000.00W0
20250601010950	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 010109z0000.00NS00000.00W0
20250601012906	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 010129z0000.00NS00000.00W0
20250601015618	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 010156z0000.00NS00000.00W0
20250601022114	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 010221z0000.00NS00000.00W0
20250601025008	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 010250z0000.00NS00000.00W0
20250601032010	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 010320z0000.00NS00000.00W0
20250601034705	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 010347z0000.00NS00000.00W0
20250601041451	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 010414z0000.00NS00000.00W0
20250601044419	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 010444z0000.00NS00000.00W0