APRS Packet Errors for DG0OPK-14 (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
20260208133856	DG0OPK-14>APRSMC,TCPIP*,qAR,DG0OPK-11:!5042.38N/01034.36E-Meshcom Steinb.-Hbg.#433.175 SF11 TEST/B=100/A=001640
20260208140900	DG0OPK-14>APRSMC,TCPIP*,qAR,DB0TAW-13:!5042.38N/01034.36E-Meshcom Steinb.-Hbg.#433.175 SF11 TEST/B=100/A=001640
20260208150927	DG0OPK-14>APRSMC,TCPIP*,qAR,DG0OPK-11:!5042.38N/01034.36E-Meshcom Steinb.-Hbg.#433.175 SF11 TEST/B=100/A=001640
20260208153943	DG0OPK-14>APRSMC,TCPIP*,qAR,DB0TAW-13:!5042.38N/01034.36E-Meshcom Steinb.-Hbg.#433.175 SF11 TEST/B=100/A=001640
20260208160957	DG0OPK-14>APRSMC,TCPIP*,qAR,DB0TAW-13:!5042.38N/01034.36E-Meshcom Steinb.-Hbg.#433.175 SF11 TEST/B=100/A=001640
20260208171029	DG0OPK-14>APRSMC,TCPIP*,qAR,DB0TAW-13:!5042.38N/01034.36E-Meshcom Steinb.-Hbg.#433.175 SF11 TEST/B=100/A=001640
20260208174059	DG0OPK-14>APRSMC,TCPIP*,qAR,DB0NH-3:!5042.38N/01034.36E-Meshcom Steinb.-Hbg.#433.175 SF11 TEST/B=100/A=001640
20260208184116	DG0OPK-14>APRSMC,TCPIP*,qAR,DB0TAW-13:!5042.38N/01034.36E-Meshcom Steinb.-Hbg.#433.175 SF11 TEST/B=100/A=001640
20260208191131	DG0OPK-14>APRSMC,TCPIP*,qAR,DB0TAW-13:!5042.38N/01034.36E-Meshcom Steinb.-Hbg.#433.175 SF11 TEST/B=100/A=001640