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
20250418055128	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 180551z0000.00NS00000.00W0
20250418061624	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 180616z0000.00NS00000.00W0
20250418064302	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 180643z0000.00NS00000.00W0
20250418071304	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 180713z0000.00NS00000.00W0
20250418073254	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 180732z0000.00NS00000.00W0
20250418080057	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 180800z0000.00NS00000.00W0
20250418083332	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 180833z0000.00NS00000.00W0
20250418085447	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 180854z0000.00NS00000.00W0
20250418092108	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 180921z0000.00NS00000.00W0
20250418094547	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 180945z0000.00NS00000.00W0
20250418101515	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 181015z0000.00NS00000.00W0
20250418104227	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 181042z0000.00NS00000.00W0
20250418110632	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 181106z0000.00NS00000.00W0
20250418114015	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 181140z0000.00NS00000.00W0