APRS Packet Errors for DL1MR-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
20260208183759	DL1MR-10>APGE01,TCPIP*,qAC,T2KOBLENZ:!5139.86N/00711.05E-APRS-Service
20260208190800	DL1MR-10>APGE01,TCPIP*,qAC,T2KOBLENZ:!5139.86N/00711.05E-APRS-Service
20260208193759	DL1MR-10>APGE01,TCPIP*,qAC,T2KOBLENZ:!5139.86N/00711.05E-APRS-Service
20260208200759	DL1MR-10>APGE01,TCPIP*,qAC,T2KOBLENZ:!5139.86N/00711.05E-APRS-Service
20260208203800	DL1MR-10>APGE01,TCPIP*,qAC,T2KOBLENZ:!5139.86N/00711.05E-APRS-Service
20260208210759	DL1MR-10>APGE01,TCPIP*,qAC,T2KOBLENZ:!5139.86N/00711.05E-APRS-Service
20260208213800	DL1MR-10>APGE01,TCPIP*,qAC,T2KOBLENZ:!5139.86N/00711.05E-APRS-Service
20260208220800	DL1MR-10>APGE01,TCPIP*,qAC,T2KOBLENZ:!5139.86N/00711.05E-APRS-Service
20260208223759	DL1MR-10>APGE01,TCPIP*,qAC,T2KOBLENZ:!5139.86N/00711.05E-APRS-Service
20260208230800	DL1MR-10>APGE01,TCPIP*,qAC,T2KOBLENZ:!5139.86N/00711.05E-APRS-Service
20260208233759	DL1MR-10>APGE01,TCPIP*,qAC,T2KOBLENZ:!5139.86N/00711.05E-APRS-Service
20260209000012	DL1MR-10>APGE01,TCPIP*,qAC,T2KOBLENZ:!5139.86N/00711.05E-Have a lot of fun! vy 73 Ralf
20260209000759	DL1MR-10>APGE01,TCPIP*,qAC,T2KOBLENZ:!5139.86N/00711.05E-APRS-Service