APRS Packet Errors for DB0MZG-2 (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
20190220082957	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0DTR-10:!SysOp DK6VV OV Merzig Q04 2
20190220085821	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0DTR-10:!SysOp DK6VV OV Merzig Q04 2
20190220092644	DB0MZG-2>APSAAR,WIDE2-1,qAR,DL2WB-10:!SysOp DK6VV OV Merzig Q04 2
20190220095510	DB0MZG-2>APSAAR,WIDE2-1,qAR,DL2WB-10:!SysOp DK6VV OV Merzig Q04 2
20190220102332	DB0MZG-2>APSAAR,WIDE2-1,qAR,DF2OO-2:!SysOp DK6VV OV Merzig Q04 2
20190220105157	DB0MZG-2>APSAAR,WIDE2-1,qAR,DL2WB-10:!SysOp DK6VV OV Merzig Q04 2
20190220112019	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0UT-10:!SysOp DK6VV OV Merzig Q04 2
20190220114843	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0DTR-10:!SysOp DK6VV OV Merzig Q04 2
20190220121707	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0DTR-10:!SysOp DK6VV OV Merzig Q04 2
20190220124530	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0DTR-10:!SysOp DK6VV OV Merzig Q04 2
20190220131354	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0DTR-10:!SysOp DK6VV OV Merzig Q04 2
20190220134219	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0DTR-10:!SysOp DK6VV OV Merzig Q04 2
20190220141041	DB0MZG-2>APSAAR,WIDE2-1,qAR,DF2OO-2:!SysOp DK6VV OV Merzig Q04 2