APRS Packet Errors for 2E0ONV (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
202602091322062E0ONV>APDW18,TCPIP*,qAC,T2ERFURT:!R4XT1MX{N& ! 2E0ONV USING DIGIPI
202602091352062E0ONV>APDW18,TCPIP*,qAC,T2ERFURT:!R4XT1MX{N& ! 2E0ONV USING DIGIPI
202602091422062E0ONV>APDW18,TCPIP*,qAC,T2ERFURT:!R4XT1MX{N& ! 2E0ONV USING DIGIPI
202602091452062E0ONV>APDW18,TCPIP*,qAC,T2ERFURT:!R4XT1MX{N& ! 2E0ONV USING DIGIPI
202602091522062E0ONV>APDW18,TCPIP*,qAC,T2ERFURT:!R4XT1MX{N& ! 2E0ONV USING DIGIPI
202602091552062E0ONV>APDW18,TCPIP*,qAC,T2ERFURT:!R4XT1MX{N& ! 2E0ONV USING DIGIPI
202602091622062E0ONV>APDW18,TCPIP*,qAC,T2ERFURT:!R4XT1MX{N& ! 2E0ONV USING DIGIPI
202602091652062E0ONV>APDW18,TCPIP*,qAC,T2ERFURT:!R4XT1MX{N& ! 2E0ONV USING DIGIPI
202602091722062E0ONV>APDW18,TCPIP*,qAC,T2ERFURT:!R4XT1MX{N& ! 2E0ONV USING DIGIPI
202602091752062E0ONV>APDW18,TCPIP*,qAC,T2ERFURT:!R4XT1MX{N& ! 2E0ONV USING DIGIPI
202602091822062E0ONV>APDW18,TCPIP*,qAC,T2ERFURT:!R4XT1MX{N& ! 2E0ONV USING DIGIPI
202602091852062E0ONV>APDW18,TCPIP*,qAC,T2ERFURT:!R4XT1MX{N& ! 2E0ONV USING DIGIPI