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
20180422175947	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0VKL-10:!SysOp DK6VV OV Merzig Q04 2
20180422182810	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0VKL-10:!SysOp DK6VV OV Merzig Q04 2
20180422185635	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0VKL-10:!SysOp DK6VV OV Merzig Q04 2
20180422192459	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0VKL-10:!SysOp DK6VV OV Merzig Q04 2
20180422195322	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0VKL-10:!SysOp DK6VV OV Merzig Q04 2
20180422202145	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0VKL-10:!SysOp DK6VV OV Merzig Q04 2
20180422202219	DB0MZG-2>APSAAR,F5ZEE*,qAR,DL2WB-10:!SysOp DK6VV OV Merzig Q04 2
20180422205010	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0VKL-10:!SysOp DK6VV OV Merzig Q04 2
20180422211833	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0VKL-10:!SysOp DK6VV OV Merzig Q04 2
20180422214657	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0VKL-10:!SysOp DK6VV OV Merzig Q04 2
20180422221520	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0VKL-10:!SysOp DK6VV OV Merzig Q04 2
20180422224344	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0VKL-10:!SysOp DK6VV OV Merzig Q04 2
20180422231208	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0VKL-10:!SysOp DK6VV OV Merzig Q04 2