APRS Packet Errors for PE2KMV (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
20181218210103PE2KMV>APRS,P*,qAS,AA5ZT-R:;PZA*182947.16NP01048.9E#PHGDPNETA Transr(0ONL
20181218230132PE2KMV>APRS,TCP*,qAS,AA5ZT-R:;PS-.44NP00830.18E#PH210DANPOCSAG Transme(4C(NIE
20181219000024PE2KMV>APRS,TCPIP*,qAS,AA5ZT-R:;PS-F5ZLK 0z4714.84N132.1PHG2280DAPNET PTranster(2389)(INE)
20181219000202PE2KMV>APRS,TCPIP*,qAS,AA5ZT-R:;PS-DB0AB90002z5340.401014.15E#PH2DPE OSGTasitr2A(NIE
20181219000204PE2KMV>APRS,TCPIPv,qAR,AA5ZT-R:;PS02z3438.10SP1433E#PHG1260DAPNET POCSAG Trans567CDEF)(ONLINE)
20181219000206PE2KMV>APRS,TCPIP*,S,pe2kmv,qAR,AA5ZT-R:;PS-SM0RUX*190001801.14E#PHG020mit(014589CD)OLN)