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
20260201120002VE1EP-13>APVR30,TCPIP*,qAC,T2SPAIN:;IRLP-2625*011200zC0s C REF9029
20260201130002VE1EP-13>APVR30,TCPIP*,qAC,T2PERTH:;IRLP-2625*011300zC0s C REF9029
20260201140002VE1EP-13>APVR30,TCPIP*,qAC,T2ROMANIA:;IRLP-2625*011400zC0s C REF9029
20260201150002VE1EP-13>APVR30,TCPIP*,qAC,T2CAEAST:;IRLP-2625*011500zC0s C REF9029
20260201160002VE1EP-13>APVR30,TCPIP*,qAC,T2ROMANIA:;IRLP-2625*011600zC0s C REF9029
20260201160258VE1EP-13>APVR30,TCPIP*,qAC,T2SYDNEY:;IRLP-2625*011602zI0s IDLE
20260201160304VE1EP-13>APVR30,TCPIP*,qAC,T2SPAIN:;IRLP-2625*011603zC0s C REF9029
20260201160426VE1EP-13>APVR30,TCPIP*,qAC,T2CHILE:;IRLP-2625*011604zI0s IDLE
20260201160432VE1EP-13>APVR30,TCPIP*,qAC,T2BC:;IRLP-2625*011604zC0s C REF9300
20260201162503VE1EP-13>APVR30,TCPIP*,qAC,T2SPAIN:;IRLP-2625*011625zI0s IDLE
20260201162509VE1EP-13>APVR30,TCPIP*,qAC,T2CHILE:;IRLP-2625*011625zC0s C REF9029
20260201170002VE1EP-13>APVR30,TCPIP*,qAC,T2SYDNEY:;IRLP-2625*011700zC0s C REF9029