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
20260824030002VE1EP-13>APVR30,TCPIP*,qAC,T2RADOM:;IRLP-2625*240300zI0s IDLE
20260824040002VE1EP-13>APVR30,TCPIP*,qAC,T2SYDNEY:;IRLP-2625*240400zI0s IDLE
20260824050002VE1EP-13>APVR30,TCPIP*,qAC,T2CHILE:;IRLP-2625*240500zI0s IDLE
20260824060002VE1EP-13>APVR30,TCPIP*,qAC,T2SYDNEY:;IRLP-2625*240600zI0s IDLE
20260824070003VE1EP-13>APVR30,TCPIP*,qAC,T2SPAIN:;IRLP-2625*240700zI0s IDLE
20260824080001VE1EP-13>APVR30,TCPIP*,qAC,T2CHILE:;IRLP-2625*240800zI0s IDLE