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
20260827010001VE1EP-13>APVR30,TCPIP*,qAC,T2CHILE:;IRLP-2625*270100zI0s IDLE
20260827020002VE1EP-13>APVR30,TCPIP*,qAC,T2SYDNEY:;IRLP-2625*270200zI0s IDLE
20260827030001VE1EP-13>APVR30,TCPIP*,qAC,T2CHILE:;IRLP-2625*270300zI0s IDLE
20260827033859VE1EP-13>APVR30,TCPIP*,qAC,T2PANAMA:;IRLP-2625*270338zI0s IDLE
20260827033917VE1EP-13>APVR30,TCPIP*,qAC,T2SYDNEY:;IRLP-2625*270339zI0s IDLE
20260827040002VE1EP-13>APVR30,TCPIP*,qAC,T2SYDNEY:;IRLP-2625*270400zI0s IDLE
20260827050002VE1EP-13>APVR30,TCPIP*,qAC,T2POLC:;IRLP-2625*270500zI0s IDLE
20260827060001VE1EP-13>APVR30,TCPIP*,qAC,T2CAEAST:;IRLP-2625*270600zI0s IDLE