APRS Packet Errors for DO1PBL-12 (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
20260209093405DO1PBL-12>APRSMC,TCPIP*,qAR,DB9EP-12:!5103.61N/00655.17E-MeshCom Hitdorf#DO1PBL-12/B=100/A=000328
20260209100420DO1PBL-12>APRSMC,TCPIP*,qAR,DD3JN-12:!5103.61N/00655.17E-MeshCom Hitdorf#DO1PBL-12/B=100/A=000328
20260209103435DO1PBL-12>APRSMC,TCPIP*,qAR,DK5SM-12:!5103.61N/00655.17E-MeshCom Hitdorf#DO1PBL-12/B=100/A=000328
20260209110450DO1PBL-12>APRSMC,TCPIP*,qAR,DB9EP-12:!5103.61N/00655.17E-MeshCom Hitdorf#DO1PBL-12/B=100/A=000328
20260209113505DO1PBL-12>APRSMC,TCPIP*,qAR,DK5SM-12:!5103.61N/00655.17E-MeshCom Hitdorf#DO1PBL-12/B=100/A=000328
20260209120527DO1PBL-12>APRSMC,TCPIP*,qAR,DK5SM-12:!5103.61N/00655.17E-MeshCom Hitdorf#DO1PBL-12/B=100/A=000328
20260209123532DO1PBL-12>APRSMC,TCPIP*,qAR,DK5SM-12:!5103.61N/00655.17E-MeshCom Hitdorf#DO1PBL-12/B=100/A=000328
20260209130542DO1PBL-12>APRSMC,TCPIP*,qAR,DK5SM-12:!5103.61N/00655.17E-MeshCom Hitdorf#DO1PBL-12/B=100/A=000328
20260209133602DO1PBL-12>APRSMC,TCPIP*,qAR,DK5SM-12:!5103.61N/00655.17E-MeshCom Hitdorf#DO1PBL-12/B=100/A=000328
20260209143631DO1PBL-12>APRSMC,TCPIP*,qAR,DB9EP-12:!5103.61N/00655.17E-MeshCom Hitdorf#DO1PBL-12/B=100/A=000328