APRS Packet Errors for OE6BID (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
20260209170302OE6BID>APDG03,TCPIP*,qAC,T2FINLAND:!4724.56NY01515.63EYYaesu DMO with EA7EE Sofware
20260209172306OE6BID>APDG03,TCPIP*,qAC,T2CSNGRAD:!4724.56NY01515.63EYYaesu DMO with EA7EE Sofware
20260209174306OE6BID>APDG03,TCPIP*,qAC,T2CZECH:!4724.56NY01515.63EYYaesu DMO with EA7EE Sofware
20260209180308OE6BID>APDG03,TCPIP*,qAC,T2CZECH:!4724.56NY01515.63EYYaesu DMO with EA7EE Sofware
20260209182310OE6BID>APDG03,TCPIP*,qAC,T2UKRAINE:!4724.56NY01515.63EYYaesu DMO with EA7EE Sofware
20260209184312OE6BID>APDG03,TCPIP*,qAC,T2PRT:!4724.56NY01515.63EYYaesu DMO with EA7EE Sofware
20260209190314OE6BID>APDG03,TCPIP*,qAC,T2UK:!4724.56NY01515.63EYYaesu DMO with EA7EE Sofware
20260209192315OE6BID>APDG03,TCPIP*,qAC,T2CSNGRAD:!4724.56NY01515.63EYYaesu DMO with EA7EE Sofware
20260209194021OE6BID>APDG03,TCPIP*,qAC,T2DENMARK:!4724.56NY01515.63EYYaesu DMO with EA7EE Sofware
20260209200023OE6BID>APDG03,TCPIP*,qAC,T2SPAIN:!4724.56NY01515.63EYYaesu DMO with EA7EE Sofware
20260209202024OE6BID>APDG03,TCPIP*,qAC,T2FINLAND:!4724.56NY01515.63EYYaesu DMO with EA7EE Sofware