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
20251202234215VE1EP-13>APVR30,TCPIP*,qAC,T2CHILE:;IRLP-2625*022342zI0s IDLE
20251202234224VE1EP-13>APVR30,TCPIP*,qAC,T2TURKIYE:;IRLP-2625*022342zC0s C STN2100
20251202235317VE1EP-13>APVR30,TCPIP*,qAC,T2PANAMA:;IRLP-2625*022353zI0s IDLE
20251202235513VE1EP-13>APVR30,TCPIP*,qAC,T2SPAIN:;IRLP-2625*022355zC0s C STN2050
20251202235606VE1EP-13>APVR30,TCPIP*,qAC,T2SPAIN:;IRLP-2625*022356zI0s IDLE
20251202235658VE1EP-13>APVR30,TCPIP*,qAC,T2TAS:;IRLP-2625*022356zC0s C REF9300
20251203000002VE1EP-13>APVR30,TCPIP*,qAC,T2TURKIYE:;IRLP-2625*030000zC0s C REF9300
20251203010002VE1EP-13>APVR30,TCPIP*,qAC,T2SPAIN:;IRLP-2625*030100zC0s C REF9300
20251203020002VE1EP-13>APVR30,TCPIP*,qAC,T2PERTH:;IRLP-2625*030200zC0s C REF9300
20251203030002VE1EP-13>APVR30,TCPIP*,qAC,T2SYDNEY:;IRLP-2625*030300zC0s C REF9300
20251203040001VE1EP-13>APVR30,TCPIP*,qAC,T2CSNGRAD:;IRLP-2625*030400zC0s C REF9300
20251203050001VE1EP-13>APVR30,TCPIP*,qAC,T2SPAIN:;IRLP-2625*030500zC0s C REF9300