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
20260208131459	OK2ZAW-26>APRSMC,TCPIP*,qAR,OK2ZAW-25:!4933.81N/01555.94E-MeshCom EU8/B=079/A=001900
20260208134459	OK2ZAW-26>APRSMC,TCPIP*,qAR,OK2ZAW-25:!4933.81N/01555.94E-MeshCom EU8/B=096/A=001900
20260208141500	OK2ZAW-26>APRSMC,TCPIP*,qAR,OK2ZAW-25:!4933.81N/01555.94E-MeshCom EU8/B=087/A=001900
20260208144500	OK2ZAW-26>APRSMC,TCPIP*,qAR,OK2ZAW-25:!4933.81N/01555.94E-MeshCom EU8/B=078/A=001900
20260208151500	OK2ZAW-26>APRSMC,TCPIP*,qAR,OK2ZAW-25:!4933.81N/01555.94E-MeshCom EU8/B=100/A=001900
20260208154500	OK2ZAW-26>APRSMC,TCPIP*,qAR,OK2ZAW-25:!4933.81N/01555.94E-MeshCom EU8/B=100/A=001900
20260208161500	OK2ZAW-26>APRSMC,TCPIP*,qAR,OK2ZAW-25:!4933.81N/01555.94E-MeshCom EU8/B=100/A=001900
20260208164500	OK2ZAW-26>APRSMC,TCPIP*,qAR,OK2ZAW-25:!4933.81N/01555.94E-MeshCom EU8/B=100/A=001900
20260208171500	OK2ZAW-26>APRSMC,TCPIP*,qAR,OK2ZAW-25:!4933.81N/01555.94E-MeshCom EU8/B=078/A=001900
20260208174500	OK2ZAW-26>APRSMC,TCPIP*,qAR,OK2ZAW-25:!4933.81N/01555.94E-MeshCom EU8/B=088/A=001900
20260208181500	OK2ZAW-26>APRSMC,TCPIP*,qAR,OK2ZAW-25:!4933.81N/01555.94E-MeshCom EU8/B=100/A=001900
20260208184500	OK2ZAW-26>APRSMC,TCPIP*,qAR,OK2ZAW-25:!4933.81N/01555.94E-MeshCom EU8/B=085/A=001900