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
20250325232609ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *252326z0000.00NS00000.00W0
20250326000026ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *260000z0000.00NS00000.00W0
20250326002704ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *260027z0000.00NS00000.00W0
20250326004711ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *260047z0000.00NS00000.00W0
20250326012003ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *260120z0000.00NS00000.00W0
20250326014300ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *260143z0000.00NS00000.00W0
20250326020955ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *260209z0000.00NS00000.00W0
20250326023508ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *260235z0000.00NS00000.00W0
20250326030652ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *260306z0000.00NS00000.00W0
20250326033438ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *260334z0000.00NS00000.00W0
20250326035718ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *260357z0000.00NS00000.00W0
20250326042123ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *260421z0000.00NS00000.00W0
20250326044818ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *260448z0000.00NS00000.00W0
20250326051803ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *260518z0000.00NS00000.00W0