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
20250917025126ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *170251z0000.00NS00000.00W0
20250917031150ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *170311z0000.00NS00000.00W0
20250917034135ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *170341z0000.00NS00000.00W0
20250917040415ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *170404z0000.00NS00000.00W0
20250917043815ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *170438z0000.00NS00000.00W0
20250917050038ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *170500z0000.00NS00000.00W0
20250917053313ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *170533z0000.00NS00000.00W0
20250917060025ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *170600z0000.00NS00000.00W0
20250917063118ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *170631z0000.00NS00000.00W0
20250917065034ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *170650z0000.00NS00000.00W0
20250917071746ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *170717z0000.00NS00000.00W0
20250917074242ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *170742z0000.00NS00000.00W0
20250917081136ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *170811z0000.00NS00000.00W0
20250917084138ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *170841z0000.00NS00000.00W0