APRS Packet Errors for DH1FR-2 (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
20260209091610	DH1FR-2>APRSGW,TCPIP*,qAR,DH1FR-2:!5051.09N/00906.46E-MeshCom 4.0, Ralf, F34/A=000801
20260209094625	DH1FR-2>APRSGW,TCPIP*,qAR,DH1FR-2:!5051.09N/00906.46E-MeshCom 4.0, Ralf, F34/A=000801
20260209101641	DH1FR-2>APRSGW,TCPIP*,qAR,DH1FR-2:!5051.09N/00906.46E-MeshCom 4.0, Ralf, F34/A=000801
20260209104656	DH1FR-2>APRSGW,TCPIP*,qAR,DH1FR-2:!5051.09N/00906.46E-MeshCom 4.0, Ralf, F34/A=000801
20260209111711	DH1FR-2>APRSGW,TCPIP*,qAR,DH1FR-2:!5051.09N/00906.46E-MeshCom 4.0, Ralf, F34/A=000801
20260209114726	DH1FR-2>APRSGW,TCPIP*,qAR,DH1FR-2:!5051.09N/00906.46E-MeshCom 4.0, Ralf, F34/A=000801
20260209121739	DH1FR-2>APRSGW,TCPIP*,qAR,DH1FR-2:!5051.09N/00906.46E-MeshCom 4.0, Ralf, F34/A=000801
20260209124754	DH1FR-2>APRSGW,TCPIP*,qAR,DH1FR-2:!5051.09N/00906.46E-MeshCom 4.0, Ralf, F34/A=000801
20260209131810	DH1FR-2>APRSGW,TCPIP*,qAR,DH1FR-2:!5051.09N/00906.46E-MeshCom 4.0, Ralf, F34/A=000801
20260209134825	DH1FR-2>APRSGW,TCPIP*,qAR,DH1FR-2:!5051.09N/00906.46E-MeshCom 4.0, Ralf, F34/A=000801
20260209141840	DH1FR-2>APRSGW,TCPIP*,qAR,DH1FR-2:!5051.09N/00906.46E-MeshCom 4.0, Ralf, F34/A=000801
20260209144855	DH1FR-2>APRSGW,TCPIP*,qAR,DH1FR-2:!5051.09N/00906.46E-MeshCom 4.0, Ralf, F34/A=000801