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
20250619034628ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *190346z0000.00NS00000.00W0
20250619040834ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *190408z0000.00NS00000.00W0
20250619043512ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *190435z0000.00NS00000.00W0
20250619050332ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *190503z0000.00NS00000.00W0
20250619052953ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *190529z0000.00NS00000.00W0
20250619055938ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *190559z0000.00NS00000.00W0
20250619062559ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *190625z0000.00NS00000.00W0
20250619065635ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *190656z0000.00NS00000.00W0
20250619072421ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *190724z0000.00NS00000.00W0
20250619074735ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *190747z0000.00NS00000.00W0
20250619081032ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *190810z0000.00NS00000.00W0
20250619084000ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *190840z0000.00NS00000.00W0
20250619090115ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *190901z0000.00NS00000.00W0