APRS Packet Errors for VE1EP-13 (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
20260111180002VE1EP-13>APVR30,TCPIP*,qAC,T2CHILE:;IRLP-2625*111800zC0s C REF9029
20260111181527VE1EP-13>APVR30,TCPIP*,qAC,T2FINLAND:;IRLP-2625*111815zI0s IDLE
20260111190001VE1EP-13>APVR30,TCPIP*,qAC,T2CSNGRAD:;IRLP-2625*111900zI0s IDLE
20260111193303VE1EP-13>APVR30,TCPIP*,qAC,T2PERTH:;IRLP-2625*111933zC0s C REF9029
20260111194133VE1EP-13>APVR30,TCPIP*,qAC,T2CHILE:;IRLP-2625*111941zI0s IDLE
20260111200001VE1EP-13>APVR30,TCPIP*,qAC,T2SPAIN:;IRLP-2625*112000zI0s IDLE
20260111210001VE1EP-13>APVR30,TCPIP*,qAC,T2SYDNEY:;IRLP-2625*112100zI0s IDLE
20260111211816VE1EP-13>APVR30,TCPIP*,qAC,T2CHILE:;IRLP-2625*112118zC0s C REF9029
20260111212521VE1EP-13>APVR30,TCPIP*,qAC,T2SYDNEY:;IRLP-2625*112125zI0s IDLE
20260111212529VE1EP-13>APVR30,TCPIP*,qAC,T2PERTH:;IRLP-2625*112125zC0s C REF9029
20260111220002VE1EP-13>APVR30,TCPIP*,qAC,T2PERTH:;IRLP-2625*112200zC0s C REF9029
20260111230001VE1EP-13>APVR30,TCPIP*,qAC,T2TURKIYE:;IRLP-2625*112300zC0s C REF9029