APRS Packet Errors for DL3DP-10 (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
20260209131428DL3DP-10>APLG0,TCPIP*,qAC,T2BELGIUM:!5121.36NL00715.78E&http://dl3dp.de LoRa-RxGate
20260209134428DL3DP-10>APLG0,TCPIP*,qAC,T2BELGIUM:!5121.36NL00715.78E&http://dl3dp.de LoRa-RxGate
20260209141433DL3DP-10>APLG0,TCPIP*,qAC,T2BELGIUM:!5121.36NL00715.78E&http://dl3dp.de LoRa-RxGate
20260209144438DL3DP-10>APLG0,TCPIP*,qAC,T2BELGIUM:!5121.36NL00715.78E&http://dl3dp.de LoRa-RxGate
20260209151438DL3DP-10>APLG0,TCPIP*,qAC,T2BELGIUM:!5121.36NL00715.78E&http://dl3dp.de LoRa-RxGate
20260209154443DL3DP-10>APLG0,TCPIP*,qAC,T2BELGIUM:!5121.36NL00715.78E&http://dl3dp.de LoRa-RxGate
20260209161448DL3DP-10>APLG0,TCPIP*,qAC,T2BELGIUM:!5121.36NL00715.78E&http://dl3dp.de LoRa-RxGate
20260209164448DL3DP-10>APLG0,TCPIP*,qAC,T2BELGIUM:!5121.36NL00715.78E&http://dl3dp.de LoRa-RxGate
20260209171448DL3DP-10>APLG0,TCPIP*,qAC,T2BELGIUM:!5121.36NL00715.78E&http://dl3dp.de LoRa-RxGate
20260209174448DL3DP-10>APLG0,TCPIP*,qAC,T2BELGIUM:!5121.36NL00715.78E&http://dl3dp.de LoRa-RxGate
20260209181451DL3DP-10>APLG0,TCPIP*,qAC,T2BELGIUM:!5121.36NL00715.78E&http://dl3dp.de LoRa-RxGate
20260209184453DL3DP-10>APLG0,TCPIP*,qAC,T2BELGIUM:!5121.36NL00715.78E&http://dl3dp.de LoRa-RxGate