APRS Packet Errors for DL1OMP-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
20260209150126DL1OMP-10>APDW18,TCPIP*,qAC,T2DENMARK:!4912.61N1058.67E-2m & LoRa i-Gate Untersteinbach
20260209153126DL1OMP-10>APDW18,TCPIP*,qAC,T2DENMARK:!4912.61N1058.67E-2m & LoRa i-Gate Untersteinbach
20260209160126DL1OMP-10>APDW18,TCPIP*,qAC,T2DENMARK:!4912.61N1058.67E-2m & LoRa i-Gate Untersteinbach
20260209163126DL1OMP-10>APDW18,TCPIP*,qAC,T2DENMARK:!4912.61N1058.67E-2m & LoRa i-Gate Untersteinbach
20260209170126DL1OMP-10>APDW18,TCPIP*,qAC,T2DENMARK:!4912.61N1058.67E-2m & LoRa i-Gate Untersteinbach
20260209173126DL1OMP-10>APDW18,TCPIP*,qAC,T2DENMARK:!4912.61N1058.67E-2m & LoRa i-Gate Untersteinbach
20260209180126DL1OMP-10>APDW18,TCPIP*,qAC,T2DENMARK:!4912.61N1058.67E-2m & LoRa i-Gate Untersteinbach
20260209183126DL1OMP-10>APDW18,TCPIP*,qAC,T2DENMARK:!4912.61N1058.67E-2m & LoRa i-Gate Untersteinbach
20260209190126DL1OMP-10>APDW18,TCPIP*,qAC,T2DENMARK:!4912.61N1058.67E-2m & LoRa i-Gate Untersteinbach
20260209193126DL1OMP-10>APDW18,TCPIP*,qAC,T2DENMARK:!4912.61N1058.67E-2m & LoRa i-Gate Untersteinbach
20260209200126DL1OMP-10>APDW18,TCPIP*,qAC,T2DENMARK:!4912.61N1058.67E-2m & LoRa i-Gate Untersteinbach
20260209203126DL1OMP-10>APDW18,TCPIP*,qAC,T2DENMARK:!4912.61N1058.67E-2m & LoRa i-Gate Untersteinbach