APRS Packet Errors for 3VA (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
202002161504253VA>AN,TCPqAC,TBEC,qAR,N3ENM-10:;RR/R 144z481N/0.16WrRR Reer on.470
202002161547253VA>APN,TCPIqAC,T2UEBEC,qAR,N3ENM-10:;E3RRR/R*z4218.81N/0302.16WrVE3 Reperon 1470 Mh
202002161911243VA>PU25AC,TEC,qAR,N3ENM-10:;R/R 44z41/083WrVERpeat 145Mhz.
202002162024213VA>AN,TCPqAC,TBEC,qAR,N3ENM-10:;II/R 145z481N/0.16WrII Reer ib.060
202002162025213VA>APU25N,TCPIP*,qAS,T2CAEAST:;VE3III/12214218.8N302.1VE3IIepeatib 1460 Mh