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
20250314175649ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *141756z0000.00NS00000.00W0
20250314182219ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *141822z0000.00NS00000.00W0
20250314184459ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *141844z0000.00NS00000.00W0
20250314191211ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *141912z0000.00NS00000.00W0
20250314194230ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *141942z0000.00NS00000.00W0
20250314200220ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *142002z0000.00NS00000.00W0
20250314203438ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *142034z0000.00NS00000.00W0
20250314210025ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *142100z0000.00NS00000.00W0
20250314213317ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *142133z0000.00NS00000.00W0
20250314215341ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *142153z0000.00NS00000.00W0
20250314222508ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *142225z0000.00NS00000.00W0
20250314225601ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *142256z0000.00NS00000.00W0
20250314231807ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *142318z0000.00NS00000.00W0