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
20260329172053VE1EP-13>APVR30,TCPIP*,qAC,T2SPAIN:;IRLP-2625*291720zC0s C REF9013
20260329172111VE1EP-13>APVR30,TCPIP*,qAC,T2ERFURT:;IRLP-2625*291721zI0s IDLE
20260329172531VE1EP-13>APVR30,TCPIP*,qAC,T2ERFURT:;IRLP-2625*291725zC0s C REF9013
20260329172547VE1EP-13>APVR30,TCPIP*,qAC,T2SPAIN:;IRLP-2625*291725zI0s IDLE
20260329172600VE1EP-13>APVR30,TCPIP*,qAC,T2SYDNEY:;IRLP-2625*291725zC0s C REF9029
20260329180013VE1EP-13>APVR30,TCPIP*,qAC,T2UKRAINE:;IRLP-2625*291800zC0s C REF9029
20260329190001VE1EP-13>APVR30,TCPIP*,qAC,T2CHILE:;IRLP-2625*291900zC0s C REF9029
20260329200002VE1EP-13>APVR30,TCPIP*,qAC,T2SYDNEY:;IRLP-2625*292000zC0s C REF9029
20260329210001VE1EP-13>APVR30,TCPIP*,qAC,T2PANAMA:;IRLP-2625*292100zC0s C REF9029
20260329220001VE1EP-13>APVR30,TCPIP*,qAC,T2DENMARK:;IRLP-2625*292200zC0s C REF9029