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
20251106163148ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *061631z0000.00NS00000.00W0
20251106170423ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *061704z0000.00NS00000.00W0
20251106173351ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *061733z0000.00NS00000.00W0
20251106180137ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *061801z0000.00NS00000.00W0
20251106182326ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *061823z0000.00NS00000.00W0
20251106185203ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *061852z0000.00NS00000.00W0
20251106191500ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *061915z0000.00NS00000.00W0
20251106194701ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *061947z0000.00NS00000.00W0
20251106200833ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *062008z0000.00NS00000.00W0
20251106204051ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *062040z0000.00NS00000.00W0
20251106210405ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *062104z0000.00NS00000.00W0
20251106213657ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *062136z0000.00NS00000.00W0
20251106220227ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *062202z0000.00NS00000.00W0