APRS Packet Errors for IZ0CZW-11 (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
20260208132945	IZ0CZW-11>APLRG1,TCPIP*,qAC,T2CHILE:!L9Va>Qoy-_ !GLoRa APRS Ext=0.22V
20260208132951	IZ0CZW-11>APLRG1,WIDE1-1,qAR,IU0SPL-11:=L9Va>Qoy-_ !GLoRa APRS Ext=0.22V
20260208142945	IZ0CZW-11>APLRG1,TCPIP*,qAC,T2CHILE:!L9Va>Qoy-_ !GLoRa APRS Ext=0.22V
20260208142952	IZ0CZW-11>APLRG1,WIDE1-1,qAR,IU0QVP-10:=L9Va>Qoy-_ !GLoRa APRS Ext=0.22V
20260208152946	IZ0CZW-11>APLRG1,TCPIP*,qAC,T2CHILE:!L9Va>Qoy-_ !GLoRa APRS Ext=0.22V
20260208152951	IZ0CZW-11>APLRG1,WIDE1-1,qAR,IU0QVP-10:=L9Va>Qoy-_ !GLoRa APRS Ext=0.22V
20260208162945	IZ0CZW-11>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L9Va>Qoy-_ !GLoRa APRS Ext=0.22V
20260208162952	IZ0CZW-11>APLRG1,WIDE1-1,qAR,IU0PXN-10:=L9Va>Qoy-_ !GLoRa APRS Ext=0.22V
20260208172945	IZ0CZW-11>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L9Va>Qoy-_ !GLoRa APRS Ext=0.22V
20260208172951	IZ0CZW-11>APLRG1,WIDE1-1,qAR,IU0PXN-10:=L9Va>Qoy-_ !GLoRa APRS Ext=0.22V
20260208182945	IZ0CZW-11>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L9Va>Qoy-_ !GLoRa APRS Ext=0.22V
20260208182951	IZ0CZW-11>APLRG1,WIDE1-1,qAR,IU0PXN-10:=L9Va>Qoy-_ !GLoRa APRS Ext=0.22V