APRS Packet Errors for DB0HWR-12 (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
20260208132000DB0HWR-12>APRSMC,TCPIP*,qAR,DD1WKS-12:!4933.74N/00647.03E-Meshcom GW/A=001683
20260208142036DB0HWR-12>APRSMC,TCPIP*,qAR,DD1WKS-12:!4933.74N/00647.03E-Meshcom GW/A=001683
20260208145046DB0HWR-12>APRSMC,TCPIP*,qAR,DD1WKS-12:!4933.74N/00647.03E-Meshcom GW/A=001683
20260208152101DB0HWR-12>APRSMC,TCPIP*,qAR,DD1WKS-12:!4933.74N/00647.03E-Meshcom GW/A=001683
20260208155117DB0HWR-12>APRSMC,TCPIP*,qAR,DD1WKS-12:!4933.74N/00647.03E-Meshcom GW/A=001683
20260208162132DB0HWR-12>APRSMC,TCPIP*,qAR,DD1WKS-12:!4933.74N/00647.03E-Meshcom GW/A=001683
20260208165147DB0HWR-12>APRSMC,TCPIP*,qAR,DD1WKS-12:!4933.74N/00647.03E-Meshcom GW/A=001683
20260208175217DB0HWR-12>APRSMC,TCPIP*,qAR,F1JMJ-11:!4933.74N/00647.03E-Meshcom GW/A=001683
20260208182233DB0HWR-12>APRSMC,TCPIP*,qAR,DL4VCM-12:!4933.74N/00647.03E-Meshcom GW/A=001683
20260208185247DB0HWR-12>APRSMC,TCPIP*,qAR,DD1WKS-12:!4933.74N/00647.03E-Meshcom GW/A=001683