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
20251106001401ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *060014z0000.00NS00000.00W0
20251106004238ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *060042z0000.00NS00000.00W0
20251106010859ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *060108z0000.00NS00000.00W0
20251106013702ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *060137z0000.00NS00000.00W0
20251106020937ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *060209z0000.00NS00000.00W0
20251106023416ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *060234z0000.00NS00000.00W0
20251106030128ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *060301z0000.00NS00000.00W0
20251106032425ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *060324z0000.00NS00000.00W0
20251106035444ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *060354z0000.00NS00000.00W0
20251106042645ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *060426z0000.00NS00000.00W0
20251106045016ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *060450z0000.00NS00000.00W0
20251106051222ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *060512z0000.00NS00000.00W0
20251106053917ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *060539z0000.00NS00000.00W0
20251106060140ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *060601z0000.00NS00000.00W0