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
20250514171132ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *141711z0000.00NS00000.00W0
20250514173554ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *141735z0000.00NS00000.00W0
20250514180050ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *141800z0000.00NS00000.00W0
20250514182455ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *141824z0000.00NS00000.00W0
20250514185349ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *141853z0000.00NS00000.00W0
20250514192459ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *141924z0000.00NS00000.00W0
20250514195154ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *141951z0000.00NS00000.00W0
20250514201434ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *142014z0000.00NS00000.00W0
20250514204129ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *142041z0000.00NS00000.00W0
20250514210352ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *142103z0000.00NS00000.00W0
20250514212939ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *142129z0000.00NS00000.00W0
20250514220413ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *142204z0000.00NS00000.00W0
20250514223415ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *142234z0000.00NS00000.00W0