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
20250417063040ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *170630z0000.00NS00000.00W0
20250417070059ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *170700z0000.00NS00000.00W0
20250417072504ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *170725z0000.00NS00000.00W0
20250417075614ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *170756z0000.00NS00000.00W0
20250417082053ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *170820z0000.00NS00000.00W0
20250417084947ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *170849z0000.00NS00000.00W0
20250417091335ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *170913z0000.00NS00000.00W0
20250417094445ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *170944z0000.00NS00000.00W0
20250417100617ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *171006z0000.00NS00000.00W0
20250417103420ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *171034z0000.00NS00000.00W0
20250417110439ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *171104z0000.00NS00000.00W0
20250417112901ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *171129z0000.00NS00000.00W0
20250417120153ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *171201z0000.00NS00000.00W0
20250417122507ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *171225z0000.00NS00000.00W0