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
20250625084232	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 250842z0000.00NS00000.00W0
20250625091831	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 250918z0000.00NS00000.00W0
20250625094708	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 250947z0000.00NS00000.00W0
20250625101022	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 251010z0000.00NS00000.00W0
20250625103319	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 251033z0000.00NS00000.00W0
20250625110827	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 251108z0000.00NS00000.00W0
20250625112800	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 251128z0000.00NS00000.00W0
20250625115529	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 251155z0000.00NS00000.00W0
20250625121735	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 251217z0000.00NS00000.00W0
20250625124629	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 251246z0000.00NS00000.00W0
20250625131017	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 251310z0000.00NS00000.00W0
20250625134451	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 251344z0000.00NS00000.00W0
20250625141021	ZL2BAU>APX220,TCPIP,qAC,T2ZL:;Staging 251410z0000.00NS00000.00W0