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
20260223150006VE1EP-13>APVR30,TCPIP*,qAC,T2SYDNEY:;IRLP-2625*231500zI0s IDLE
20260223160002VE1EP-13>APVR30,TCPIP*,qAC,T2CSNGRAD:;IRLP-2625*231600zI0s IDLE
20260223160317VE1EP-13>APVR30,TCPIP*,qAC,T2CHILE:;IRLP-2625*231603zI0s IDLE
20260223160459VE1EP-13>APVR30,TCPIP*,qAC,T2SYDNEY:;IRLP-2625*231604zI0s IDLE
20260223160528VE1EP-13>APVR30,TCPIP*,qAC,T2CHILE:;IRLP-2625*231605zI0s IDLE
20260223162517VE1EP-13>APVR30,TCPIP*,qAC,T2CHILE:;IRLP-2625*231625zI0s IDLE
20260223162631VE1EP-13>APVR30,TCPIP*,qAC,T2PERTH:;IRLP-2625*231626zI0s IDLE
20260223170001VE1EP-13>APVR30,TCPIP*,qAC,T2CSNGRAD:;IRLP-2625*231700zI0s IDLE
20260223180001VE1EP-13>APVR30,TCPIP*,qAC,T2BC:;IRLP-2625*231800zI0s IDLE
20260223190002VE1EP-13>APVR30,TCPIP*,qAC,T2CHILE:;IRLP-2625*231900zI0s IDLE
20260223200002VE1EP-13>APVR30,TCPIP*,qAC,T2PANAMA:;IRLP-2625*232000zI0s IDLE