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
20251018015928	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 180159z0000.00NS00000.00W0
20251018022009	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 180220z0000.00NS00000.00W0
20251018025318	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 180253z0000.00NS00000.00W0
20251018031922	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 180319z0000.00NS00000.00W0
20251018034708	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 180347z0000.00NS00000.00W0
20251018041852	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 180418z0000.00NS00000.00W0
20251018044854	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 180448z0000.00NS00000.00W0
20251018051350	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 180513z0000.00NS00000.00W0
20251018053721	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 180537z0000.00NS00000.00W0
20251018060109	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 180601z0000.00NS00000.00W0
20251018062929	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 180629z0000.00NS00000.00W0
20251018065550	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 180655z0000.00NS00000.00W0
20251018072518	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 180725z0000.00NS00000.00W0