APRS Packet Errors for DM0RS-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
20260208150018DM0RS-10>APLG0,TCPIP*,qAC,APRSFI-I1:!5111.00NL00713.30E&LoRa APRS iGate / RX only
20260208153018DM0RS-10>APLG0,TCPIP*,qAC,APRSFI-I1:!5111.00NL00713.30E&LoRa APRS iGate / RX only
20260208160022DM0RS-10>APLG0,TCPIP*,qAC,APRSFI-I1:!5111.00NL00713.30E&LoRa APRS iGate / RX only
20260208163022DM0RS-10>APLG0,TCPIP*,qAC,APRSFI-I1:!5111.00NL00713.30E&LoRa APRS iGate / RX only
20260208170026DM0RS-10>APLG0,TCPIP*,qAC,APRSFI-I1:!5111.00NL00713.30E&LoRa APRS iGate / RX only
20260208173033DM0RS-10>APLG0,TCPIP*,qAC,APRSFI-I1:!5111.00NL00713.30E&LoRa APRS iGate / RX only
20260208180032DM0RS-10>APLG0,TCPIP*,qAC,APRSFI-I1:!5111.00NL00713.30E&LoRa APRS iGate / RX only
20260208183036DM0RS-10>APLG0,TCPIP*,qAC,APRSFI-I1:!5111.00NL00713.30E&LoRa APRS iGate / RX only
20260208190041DM0RS-10>APLG0,TCPIP*,qAC,APRSFI-I1:!5111.00NL00713.30E&LoRa APRS iGate / RX only
20260208193043DM0RS-10>APLG0,TCPIP*,qAC,APRSFI-I1:!5111.00NL00713.30E&LoRa APRS iGate / RX only
20260208200048DM0RS-10>APLG0,TCPIP*,qAC,APRSFI-I1:!5111.00NL00713.30E&LoRa APRS iGate / RX only
20260208203048DM0RS-10>APLG0,TCPIP*,qAC,APRSFI-I1:!5111.00NL00713.30E&LoRa APRS iGate / RX only