APRS Packet Errors for IW5EIV (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
20260209092355IW5EIV>APX215,TCPIP*,qAC,T2FRANCE:=4344.65N/01059.41EySez. A.R.I Empoli IQ5EM
20260209095355IW5EIV>APX215,TCPIP*,qAC,T2FRANCE:=4344.65N/01059.41EySez. A.R.I Empoli IQ5EM
20260209102357IW5EIV>APX215,TCPIP*,qAC,T2FRANCE:=4344.65N/01059.41EySez. A.R.I Empoli IQ5EM
20260209105358IW5EIV>APX215,TCPIP*,qAC,T2FRANCE:=4344.65N/01059.41EySez. A.R.I Empoli IQ5EM
20260209112359IW5EIV>APX215,TCPIP*,qAC,T2FRANCE:=4344.65N/01059.41EySez. A.R.I Empoli IQ5EM
20260209115359IW5EIV>APX215,TCPIP*,qAC,T2FRANCE:=4344.65N/01059.41EySez. A.R.I Empoli IQ5EM
20260209122401IW5EIV>APX215,TCPIP*,qAC,T2FRANCE:=4344.65N/01059.41EySez. A.R.I Empoli IQ5EM
20260209132402IW5EIV>APX215,TCPIP*,qAC,T2LUBLIN:=4344.65N/01059.41EySez. A.R.I Empoli IQ5EM
20260209135404IW5EIV>APX215,TCPIP*,qAC,T2LUBLIN:=4344.65N/01059.41EySez. A.R.I Empoli IQ5EM
20260209142405IW5EIV>APX215,TCPIP*,qAC,T2LUBLIN:=4344.65N/01059.41EySez. A.R.I Empoli IQ5EM
20260209145406IW5EIV>APX215,TCPIP*,qAC,T2LUBLIN:=4344.65N/01059.41EySez. A.R.I Empoli IQ5EM