APRS Packet Errors for DL4MFM-99 (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
20260208151126DL4MFM-99>APRSGW,TCPIP*,qAR,DL4MFM-99:!5224.44NM00759.00E&MeshCom Node#DL4MFM-99/A=000174
20260208154138DL4MFM-99>APRSGW,TCPIP*,qAR,DL4MFM-99:!5224.44NM00759.00E&MeshCom Node#DL4MFM-99/A=000174
20260208161153DL4MFM-99>APRSGW,TCPIP*,qAR,DL4MFM-99:!5224.44NM00759.00E&MeshCom Node#DL4MFM-99/A=000174
20260208164208DL4MFM-99>APRSGW,TCPIP*,qAR,DL4MFM-99:!5224.44NM00759.00E&MeshCom Node#DL4MFM-99/A=000174
20260208171225DL4MFM-99>APRSGW,TCPIP*,qAR,DL4MFM-99:!5224.44NM00759.00E&MeshCom Node#DL4MFM-99/A=000174
20260208174240DL4MFM-99>APRSGW,TCPIP*,qAR,DL4MFM-99:!5224.44NM00759.00E&MeshCom Node#DL4MFM-99/A=000174
20260208181253DL4MFM-99>APRSGW,TCPIP*,qAR,DL4MFM-99:!5224.44NM00759.00E&MeshCom Node#DL4MFM-99/A=000174
20260208184308DL4MFM-99>APRSGW,TCPIP*,qAR,DL4MFM-99:!5224.44NM00759.00E&MeshCom Node#DL4MFM-99/A=000174
20260208191323DL4MFM-99>APRSGW,TCPIP*,qAR,DL4MFM-99:!5224.44NM00759.00E&MeshCom Node#DL4MFM-99/A=000174
20260208194340DL4MFM-99>APRSGW,TCPIP*,qAR,DL4MFM-99:!5224.44NM00759.00E&MeshCom Node#DL4MFM-99/A=000174
20260208201355DL4MFM-99>APRSGW,TCPIP*,qAR,DL4MFM-99:!5224.44NM00759.00E&MeshCom Node#DL4MFM-99/A=000174
20260208204406DL4MFM-99>APRSGW,TCPIP*,qAR,DL4MFM-99:!5224.44NM00759.00E&MeshCom Node#DL4MFM-99/A=000174