APRS Packet Errors for DL6MB-21 (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
20260208151735DL6MB-21>APRSMC,TCPIP*,qAR,DG6YCB-10:!5159.25N0654.44EVMeshCom GTW JO31KX#Peter/B=100/A=000157
20260208154750DL6MB-21>APRSMC,TCPIP*,qAR,DG6YCB-10:!5159.25N0654.44EVMeshCom GTW JO31KX#Peter/B=100/A=000154
20260208161804DL6MB-21>APRSGW,TCPIP*,qAR,DL6MB-21:!5159.26N0654.44EVMeshCom GTW JO31KX#Peter/B=100/A=000161
20260208164632DL6MB-21>APRSMC,TCPIP*,qAR,DG6YCB-10:!5159.25N0654.44EVMeshCom GTW JO31KX#Peter/B=100/A=000151
20260208171621DL6MB-21>APRSMC,TCPIP*,qAR,DG6YCB-10:!5159.26N0654.44EVMeshCom GTW JO31KX#Peter/B=100/A=000141
20260208173632DL6MB-21>APRSMC,TCPIP*,qAR,DG6YCB-10:!5159.25N0654.44EVMeshCom GTW JO31KX#Peter/B=100/A=000154
20260208180647DL6MB-21>APRSMC,TCPIP*,qAR,DG6YCB-10:!5159.25N0654.44EVMeshCom GTW JO31KX#Peter/B=100/A=000138
20260208190721DL6MB-21>APRSMC,TCPIP*,qAR,DG6YCB-10:!5159.26N0654.44EVMeshCom GTW JO31KX#Peter/B=100/A=000144
20260208193732DL6MB-21>APRSMC,TCPIP*,qAR,DG6YCB-10:!5159.25N0654.44EVMeshCom GTW JO31KX#Peter/B=100/A=000151
20260208200747DL6MB-21>APRSMC,TCPIP*,qAR,DG6YCB-10:!5159.26N0654.44EVMeshCom GTW JO31KX#Peter/B=100/A=000167