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
20261016030002VE1EP-13>APVR30,TCPIP*,qAC,T2FINLAND:;IRLP-2625*160300zI0s IDLE
20261016033101VE1EP-13>APVR30,TCPIP*,qAC,T2OREGON:;IRLP-2625*160331zI0s IDLE
20261016033149VE1EP-13>APVR30,TCPIP*,qAC,T2RDU:;IRLP-2625*160331zI0s IDLE
20261016040002VE1EP-13>APVR30,TCPIP*,qAC,T2FINLAND:;IRLP-2625*160400zI0s IDLE
20261016050001VE1EP-13>APVR30,TCPIP*,qAC,T2CAEAST:;IRLP-2625*160500zI0s IDLE
20261016060002VE1EP-13>APVR30,TCPIP*,qAC,T2OREGON:;IRLP-2625*160600zI0s IDLE
20261016070003VE1EP-13>APVR30,TCPIP*,qAC,T2TAS:;IRLP-2625*160700zI0s IDLE
20261016080002VE1EP-13>APVR30,TCPIP*,qAC,T2SPAIN:;IRLP-2625*160800zI0s IDLE