APRS Packet Errors for OK1PHU-23 (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
20260208141424OK1PHU-23>APRSWX,TCPIP*,qAC,T2UKRAINE:=4945.67N/01555.28E_.../...g...t37b10069
20260208151131OK1PHU-23>APRSWX,TCPIP*,qAC,T2ROMANIA:=4945.67N/01555.28E_.../...g...t37b10072
20260208160904OK1PHU-23>APRSWX,TCPIP*,qAC,T2POLC:=4945.67N/01555.28E_.../...g...t36b10074
20260208170616OK1PHU-23>APRSWX,TCPIP*,qAC,T2CSNGRAD:=4945.67N/01555.28E_.../...g...t36b10079
20260208180323OK1PHU-23>APRSWX,TCPIP*,qAC,T2SPAIN:=4945.67N/01555.28E_.../...g...t35b10083
20260208190113OK1PHU-23>APRSWX,TCPIP*,qAC,T2BELGIUM:=4945.67N/01555.28E_.../...g...t36b10083