APRS Packet Errors for OK1JMB (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
20260209143914OK1JMB>APOSB4,TCPIP*,qAC,T2SPAIN:@091439z4952.88N1258.81EK054/001/A=001716Mirek OK1JMB
20260209143944OK1JMB>APOSB4,TCPIP*,qAC,T2SPAIN:@091439z4952.88N1258.81EK003/003/A=001719Mirek OK1JMB
20260209144015OK1JMB>APOSB4,TCPIP*,qAC,T2SPAIN:@091440z4952.88N1258.81EK258/000/A=001719Mirek OK1JMB
20260209144115OK1JMB>APOSB4,TCPIP*,qAC,T2SPAIN:@091441z4952.88N1258.81EK156/000/A=001719Mirek OK1JMB
20260209144216OK1JMB>APOSB4,TCPIP*,qAC,T2SPAIN:@091442z4952.88N1258.81EK165/000/A=001716Mirek OK1JMB
20260209144316OK1JMB>APOSB4,TCPIP*,qAC,T2SPAIN:@091443z4952.88N1258.81EK165/000/A=001719Mirek OK1JMB
20260209144346OK1JMB>APOSB4,TCPIP*,qAC,T2SPAIN:@091443z4952.88N1258.81EK359/000/A=001722Mirek OK1JMB
20260209144417OK1JMB>APOSB4,TCPIP*,qAC,T2SPAIN:@091444z4952.88N1258.81EK359/000/A=001726Mirek OK1JMB
20260209144447OK1JMB>APOSB4,TCPIP*,qAC,T2SPAIN:@091444z4952.88N1258.81EK323/001/A=001726Mirek OK1JMB
20260209144638OK1JMB>APOSB4,TCPIP*,qAC,T2SPAIN:@091446z4952.88N1258.81EK177/000/A=001732Mirek OK1JMB