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
20251013232618ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *132326z0000.00NS00000.00W0
20251013235205ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *132352z0000.00NS00000.00W0
20251014001809ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *140018z0000.00NS00000.00W0
20251014004737ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *140047z0000.00NS00000.00W0
20251014011847ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *140118z0000.00NS00000.00W0
20251014013803ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *140138z0000.00NS00000.00W0
20251014021237ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *140212z0000.00NS00000.00W0
20251014024040ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *140240z0000.00NS00000.00W0
20251014031025ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *140310z0000.00NS00000.00W0
20251014033322ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *140333z0000.00NS00000.00W0
20251014035727ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *140357z0000.00NS00000.00W0