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
20250530041320ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *300413z0000.00NS00000.00W0
20250530044504ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *300445z0000.00NS00000.00W0
20250530051341ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *300513z0000.00NS00000.00W0
20250530054127ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *300541z0000.00NS00000.00W0
20250530060913ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *300609z0000.00NS00000.00W0
20250530063517ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *300635z0000.00NS00000.00W0
20250530065814ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *300658z0000.00NS00000.00W0
20250530072725ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *300727z0000.00NS00000.00W0
20250530075545ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *300755z0000.00NS00000.00W0
20250530081751ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *300817z0000.00NS00000.00W0
20250530084338ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *300843z0000.00NS00000.00W0
20250530091124ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *300911z0000.00NS00000.00W0
20250530093603ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *300936z0000.00NS00000.00W0