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
20251219180002VE1EP-13>APVR30,TCPIP*,qAC,T2PANAMA:;IRLP-2625*191800zC0s C REF9029
20251219190002VE1EP-13>APVR30,TCPIP*,qAC,T2PERTH:;IRLP-2625*191900zC0s C REF9029
20251219192139VE1EP-13>APVR30,TCPIP*,qAC,T2SPAIN:;IRLP-2625*191921zI0s IDLE
20251219192634VE1EP-13>APVR30,TCPIP*,qAC,T2CAEAST:;IRLP-2625*191926zC0s C REF9029
20251219200002VE1EP-13>APVR30,TCPIP*,qAC,T2SPAIN:;IRLP-2625*192000zC0s C REF9029
20251219210002VE1EP-13>APVR30,TCPIP*,qAC,T2LAUSITZ:;IRLP-2625*192100zC0s C REF9029
20251219220002VE1EP-13>APVR30,TCPIP*,qAC,T2DENMARK:;IRLP-2625*192200zC0s C REF9029
20251219230002VE1EP-13>APVR30,TCPIP*,qAC,T2PERTH:;IRLP-2625*192300zC0s C REF9029