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
20250916090350ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *160903z0000.00NS00000.00W0
20250916092903ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *160929z0000.00NS00000.00W0
20250916100047ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *161000z0000.00NS00000.00W0
20250916102833ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *161028z0000.00NS00000.00W0
20250916105113ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *161051z0000.00NS00000.00W0
20250916111518ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *161115z0000.00NS00000.00W0
20250916114213ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *161142z0000.00NS00000.00W0
20250916121158ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *161211z0000.00NS00000.00W0
20250916124325ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *161243z0000.00NS00000.00W0
20250916130315ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *161303z0000.00NS00000.00W0
20250916132936ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *161329z0000.00NS00000.00W0
20250916135523ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *161355z0000.00NS00000.00W0
20250916142144ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *161421z0000.00NS00000.00W0
20250916144930ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *161449z0000.00NS00000.00W0