APRS Packet Errors for OK2ZAW-26 (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
20260209104502OK2ZAW-26>APRSMC,TCPIP*,qAR,OK2ZAW-25:!4933.81N/01555.94E-MeshCom EU8/B=091/A=001900
20260209111503OK2ZAW-26>APRSMC,TCPIP*,qAR,OK2ZAW-25:!4933.81N/01555.94E-MeshCom EU8/B=100/A=001900
20260209114503OK2ZAW-26>APRSMC,TCPIP*,qAR,OK2ZAW-25:!4933.81N/01555.94E-MeshCom EU8/B=100/A=001900
20260209121503OK2ZAW-26>APRSMC,TCPIP*,qAR,OK2ZAW-25:!4933.81N/01555.94E-MeshCom EU8/B=096/A=001900
20260209124503OK2ZAW-26>APRSMC,TCPIP*,qAR,OK2ZAW-25:!4933.81N/01555.94E-MeshCom EU8/B=100/A=001900
20260209131503OK2ZAW-26>APRSMC,TCPIP*,qAR,OK2ZAW-25:!4933.81N/01555.94E-MeshCom EU8/B=084/A=001900
20260209134503OK2ZAW-26>APRSMC,TCPIP*,qAR,OK2ZAW-25:!4933.81N/01555.94E-MeshCom EU8/B=079/A=001900
20260209141503OK2ZAW-26>APRSMC,TCPIP*,qAR,OK2ZAW-25:!4933.81N/01555.94E-MeshCom EU8/B=100/A=001900
20260209144504OK2ZAW-26>APRSMC,TCPIP*,qAR,OK2ZAW-25:!4933.81N/01555.94E-MeshCom EU8/B=100/A=001900
20260209151503OK2ZAW-26>APRSMC,TCPIP*,qAR,OK2ZAW-25:!4933.81N/01555.94E-MeshCom EU8/B=100/A=001900
20260209154503OK2ZAW-26>APRSMC,TCPIP*,qAR,OK2ZAW-25:!4933.81N/01555.94E-MeshCom EU8/B=100/A=001900
20260209161503OK2ZAW-26>APRSMC,TCPIP*,qAR,OK2ZAW-25:!4933.81N/01555.94E-MeshCom EU8/B=100/A=001900