APRS Packet Errors for DA0RH (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
20260209091210DB0ROD>APMI01,qAR,DB0HFT-10:;DA0RH *090912z5221.93N/00944.66E-Region Hannover via DB0ROD
20260209094212DB0ROD>APMI01,qAR,DM0DOS-10:;DA0RH *090942z5221.93N/00944.66E-Region Hannover via DB0ROD
20260209101214DB0ROD>APMI01,qAR,DL2MF-10:;DA0RH *091012z5221.93N/00944.66E-Region Hannover via DB0ROD
20260209104215DB0ROD>APMI01,qAR,DB0HFT-10:;DA0RH *091042z5221.93N/00944.66E-Region Hannover via DB0ROD
20260209111217DB0ROD>APMI01,qAR,DL2MF-10:;DA0RH *091112z5221.93N/00944.66E-Region Hannover via DB0ROD
20260209114219DB0ROD>APMI01,qAR,DL2MF-10:;DA0RH *091142z5221.93N/00944.66E-Region Hannover via DB0ROD
20260209121221DB0ROD>APMI01,qAR,DB0HFT-10:;DA0RH *091212z5221.93N/00944.66E-Region Hannover via DB0ROD
20260209124224DB0ROD>APMI01,qAR,DB0OE:;DA0RH *091242z5221.93N/00944.66E-Region Hannover via DB0ROD
20260209131224DB0ROD>APMI01,qAR,DL2MF-10:;DA0RH *091312z5221.93N/00944.66E-Region Hannover via DB0ROD
20260209134226DB0ROD>APMI01,qAR,DB0HFT-10:;DA0RH *091342z5221.93N/00944.66E-Region Hannover via DB0ROD
20260209141227DB0ROD>APMI01,qAR,DB0HFT-10:;DA0RH *091412z5221.93N/00944.66E-Region Hannover via DB0ROD
20260209144229DB0ROD>APMI01,qAR,DL2MF-10:;DA0RH *091442z5221.93N/00944.66E-Region Hannover via DB0ROD