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
20261020210002VE1EP-13>APVR30,TCPIP*,qAC,T2LAUSITZ:;IRLP-2625*202100zI0s IDLE
20261020220002VE1EP-13>APVR30,TCPIP*,qAC,T2TAS:;IRLP-2625*202200zI0s IDLE
20261020230002VE1EP-13>APVR30,TCPIP*,qAC,T2EDM:;IRLP-2625*202300zI0s IDLE
20261021000002VE1EP-13>APVR30,TCPIP*,qAC,T2SPAIN:;IRLP-2625*210000zI0s IDLE
20261021010003VE1EP-13>APVR30,TCPIP*,qAC,T2TAS:;IRLP-2625*210100zI0s IDLE
20261021020002VE1EP-13>APVR30,TCPIP*,qAC,T2TAS:;IRLP-2625*210200zI0s IDLE