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
20251206210001VE1EP-13>APVR30,TCPIP*,qAC,T2BIO:;IRLP-2625*062100zC0s C REF9029
20251206220001VE1EP-13>APVR30,TCPIP*,qAC,T2CAEAST:;IRLP-2625*062200zC0s C REF9029
20251206225710VE1EP-13>APVR30,TCPIP*,qAC,T2PANAMA:;IRLP-2625*062257zI0s IDLE
20251206230002VE1EP-13>APVR30,TCPIP*,qAC,T2CSNGRAD:;IRLP-2625*062300zI0s IDLE
20251206231956VE1EP-13>APVR30,TCPIP*,qAC,T2UKRAINE:;IRLP-2625*062319zC0s C REF9029
20251206234005VE1EP-13>APVR30,TCPIP*,qAC,T2ERFURT:;IRLP-2625*062340zI0s IDLE
20251206234310VE1EP-13>APVR30,TCPIP*,qAC,T2SYDNEY:;IRLP-2625*062343zC0s C REF9021
20251206234641VE1EP-13>APVR30,TCPIP*,qAC,T2PANAMA:;IRLP-2625*062346zI0s IDLE
20251206234648VE1EP-13>APVR30,TCPIP*,qAC,T2CHILE:;IRLP-2625*062346zC0s C REF9012
20251207000001VE1EP-13>APVR30,TCPIP*,qAC,T2SPAIN:;IRLP-2625*070000zC0s C REF9012
20251207010003VE1EP-13>APVR30,TCPIP*,qAC,T2SYDNEY:;IRLP-2625*070100zC0s C REF9012
20251207011816VE1EP-13>APVR30,TCPIP*,qAC,T2UKRAINE:;IRLP-2625*070118zI0s IDLE
20251207011824VE1EP-13>APVR30,TCPIP*,qAC,T2CHILE:;IRLP-2625*070118zC0s C REF9029
20251207020002VE1EP-13>APVR30,TCPIP*,qAC,T2SPAIN:;IRLP-2625*070200zC0s C REF9029