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
20250701020825	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 010208z0000.00NS00000.00W0
20250701023503	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 010235z0000.00NS00000.00W0
20250701025544	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 010255z0000.00NS00000.00W0
20250701032853	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 010328z0000.00NS00000.00W0
20250701035332	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 010353z0000.00NS00000.00W0
20250701042101	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 010421z0000.00NS00000.00W0
20250701044540	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 010445z0000.00NS00000.00W0
20250701050837	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 010508z0000.00NS00000.00W0
20250701053731	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 010537z0000.00NS00000.00W0
20250701060318	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 010603z0000.00NS00000.00W0
20250701062558	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 010625z0000.00NS00000.00W0
20250701065941	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 010659z0000.00NS00000.00W0
20250701072022	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 010720z0000.00NS00000.00W0
20250701074734	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 010747z0000.00NS00000.00W0