APRS Packet Errors for OK1TEC-22 (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
20260208132533OK1TEC-22>APLRG1,TCPIP*,qAC,T2CZECH:!L4nPtR?)Aa xGJablonec nad Nisou
20260208135633OK1TEC-22>APLRG1,TCPIP*,qAC,T2CZECH:!L4nPtR?)Aa xGJablonec nad Nisou
20260208142733OK1TEC-22>APLRG1,TCPIP*,qAC,T2CZECH:!L4nPtR?)Aa xGJablonec nad Nisou
20260208145833OK1TEC-22>APLRG1,TCPIP*,qAC,T2CZECH:!L4nPtR?)Aa xGJablonec nad Nisou
20260208152935OK1TEC-22>APLRG1,TCPIP*,qAC,T2CZECH:!L4nPtR?)Aa xGJablonec nad Nisou
20260208160035OK1TEC-22>APLRG1,TCPIP*,qAC,T2CZECH:!L4nPtR?)Aa xGJablonec nad Nisou
20260208163135OK1TEC-22>APLRG1,TCPIP*,qAC,T2CZECH:!L4nPtR?)Aa xGJablonec nad Nisou
20260208170235OK1TEC-22>APLRG1,TCPIP*,qAC,T2CZECH:!L4nPtR?)Aa xGJablonec nad Nisou
20260208173336OK1TEC-22>APLRG1,TCPIP*,qAC,T2CZECH:!L4nPtR?)Aa xGJablonec nad Nisou
20260208180436OK1TEC-22>APLRG1,TCPIP*,qAC,T2CZECH:!L4nPtR?)Aa xGJablonec nad Nisou
20260208183536OK1TEC-22>APLRG1,TCPIP*,qAC,T2CZECH:!L4nPtR?)Aa xGJablonec nad Nisou
20260208190636OK1TEC-22>APLRG1,TCPIP*,qAC,T2CZECH:!L4nPtR?)Aa xGJablonec nad Nisou