APRS Packet Errors for IRLP-4069 (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
20171123201623W4SNA-13>APUN10,TCPIP*,qAC,T2VAN:;IRLP-4069*232016z3622.65NI08021.86WW53.310MHz- PL100.0: IDLE
20171123211626W4SNA-13>APUN10,TCPIP*,qAC,T2ONTARIO:;IRLP-4069*232116z3622.65NI08021.86WW53.310MHz- PL100.0: IDLE
20171123212008W4SNA-13>APUN10,TCPIP*,qAC,T2QUEBEC:;IRLP-4069*232120z3622.65NC08021.86WW53.310MHz- PL100.0: Linked EL937578 KN4GGA
20171123212646W4SNA-13>APUN10,TCPIP*,qAC,T2GYOR:;IRLP-4069*232126z3622.65NI08021.86WW53.310MHz- PL100.0: IDLE
20171123220202W4SNA-13>APUN10,TCPIP*,qAC,T2GREECE:;IRLP-4069*232202z3622.65NC08021.86WW53.310MHz- PL100.0: Linked EL692951 KD4JTD
20171123220235W4SNA-13>APUN10,TCPIP*,qAC,T2NUERNBG:;IRLP-4069*232202z3622.65NI08021.86WW53.310MHz- PL100.0: IDLE
20171123230236W4SNA-13>APUN10,TCPIP*,qAC,T2TURKIYE:;IRLP-4069*232302z3622.65NI08021.86WW53.310MHz- PL100.0: IDLE
20171124000238W4SNA-13>APUN10,TCPIP*,qAC,T2PARIS:;IRLP-4069*240002z3622.65NI08021.86WW53.310MHz- PL100.0: IDLE
20171124010241W4SNA-13>APUN10,TCPIP*,qAC,T2EISBERG:;IRLP-4069*240102z3622.65NI08021.86WW53.310MHz- PL100.0: IDLE
20171124020244W4SNA-13>APUN10,TCPIP*,qAC,T2PARIS:;IRLP-4069*240202z3622.65NI08021.86WW53.310MHz- PL100.0: IDLE