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
20251224120001VE1EP-13>APVR30,TCPIP*,qAC,T2CSNGRAD:;IRLP-2625*241200zC0s C REF9300
20251224130002VE1EP-13>APVR30,TCPIP*,qAC,T2BELGIUM:;IRLP-2625*241300zC0s C REF9300
20251224131401VE1EP-13>APVR30,TCPIP*,qAC,T2TAS:;IRLP-2625*241314zI0s IDLE
20251224133922VE1EP-13>APVR30,TCPIP*,qAC,T2SYDNEY:;IRLP-2625*241339zC0s C REF9029
20251224134207VE1EP-13>APVR30,TCPIP*,qAC,T2SYDNEY:;IRLP-2625*241342zI0s IDLE
20251224134214VE1EP-13>APVR30,TCPIP*,qAC,T2BC:;IRLP-2625*241342zC0s C REF9103
20251224134234VE1EP-13>APVR30,TCPIP*,qAC,T2PERTH:;IRLP-2625*241342zC0s C REF9013
20251224135314VE1EP-13>APVR30,TCPIP*,qAC,T2UKRAINE:;IRLP-2625*241353zI0s IDLE
20251224135322VE1EP-13>APVR30,TCPIP*,qAC,T2PERTH:;IRLP-2625*241353zC0s C REF9029
20251224140002VE1EP-13>APVR30,TCPIP*,qAC,T2PERTH:;IRLP-2625*241400zC0s C REF9029
20251224150002VE1EP-13>APVR30,TCPIP*,qAC,T2TAS:;IRLP-2625*241500zC0s C REF9029
20251224152307VE1EP-13>APVR30,TCPIP*,qAC,T2UKRAINE:;IRLP-2625*241523zI0s IDLE
20251224152314VE1EP-13>APVR30,TCPIP*,qAC,T2SYDNEY:;IRLP-2625*241523zC0s C REF9013
20251224160001VE1EP-13>APVR30,TCPIP*,qAC,T2UKRAINE:;IRLP-2625*241600zC0s C REF9013
20251224170002VE1EP-13>APVR30,TCPIP*,qAC,T2PANAMA:;IRLP-2625*241700zC0s C REF9013