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
20250726035051	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 260350z0000.00NS00000.00W0
20250726041206	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 260412z0000.00NS00000.00W0
20250726044458	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 260444z0000.00NS00000.00W0
20250726051028	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 260510z0000.00NS00000.00W0
20250726053922	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 260539z0000.00NS00000.00W0
20250726060435	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 260604z0000.00NS00000.00W0
20250726062823	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 260628z0000.00NS00000.00W0
20250726070058	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 260700z0000.00NS00000.00W0
20250726072810	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 260728z0000.00NS00000.00W0
20250726075141	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 260751z0000.00NS00000.00W0
20250726082342	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 260823z0000.00NS00000.00W0
20250726084639	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 260846z0000.00NS00000.00W0
20250726091533	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 260915z0000.00NS00000.00W0