APRS Packet Errors for DL4YEL-3 (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
20260208145848DL4YEL-3>APRSMC,TCPIP*,qAR,DL6YJB-1:!5136.91N/00724.50E#MeshCom Node Waltrop#Robert/B=100/A=000161
20260208150640DL4YEL-3>APRSMC,TCPIP*,qAR,DM0DOS-11:!5136.90N/00724.49E#MeshCom Node Waltrop#Robert/B=100/A=000121
20260208151838DL4YEL-3>APRSMC,TCPIP*,qAR,DB0OHL-12:!5136.89N/00724.47E#MeshCom Node Waltrop#Robert/B=100/A=000154
20260208154842DL4YEL-3>APRSMC,TCPIP*,qAR,DK8CB-99:!5136.91N/00724.50E#MeshCom Node Waltrop#Robert/B=100/A=000118
20260208161857DL4YEL-3>APRSMC,TCPIP*,qAR,DK8CB-99:!5136.91N/00724.51E#MeshCom Node Waltrop#Robert/B=100/A=000180
20260208174952DL4YEL-3>APRSMC,TCPIP*,qAR,DK8CB-99:!5136.89N/00724.49E#MeshCom Node Waltrop#Robert/B=100/A=000262
20260208185014DL4YEL-3>APRSMC,TCPIP*,qAR,DB0CRE-12:!5136.90N/00724.50E#MeshCom Node Waltrop#Robert/B=100/A=000151
20260208195047DL4YEL-3>APRSMC,TCPIP*,qAR,DL6YJB-1:!5136.91N/00724.51E#MeshCom Node Waltrop#Robert/B=100/A=000164
20260208201451DL4YEL-3>APRSMC,TCPIP*,qAR,DM0DOS-11:!5136.91N/00724.51E#MeshCom Node Waltrop#Robert/B=100/A=000292
20260208202201DL4YEL-3>APRSMC,TCPIP*,qAR,DL6YJB-1:!5136.92N/00724.47E#MeshCom Node Waltrop#Robert/B=100/A=000367