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
20180620070736	DB0MZG-2>APSAAR,WIDE2-1,qAR,F5ZEE:!SysOp DK6VV OV Merzig Q04 2
20180620073601	DB0MZG-2>APSAAR,WIDE2-1,qAR,F5ZEE:!SysOp DK6VV OV Merzig Q04 2
20180620080425	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0VKL-10:!SysOp DK6VV OV Merzig Q04 2
20180620083249	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0VKL-10:!SysOp DK6VV OV Merzig Q04 2
20180620090111	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0VKL-10:!SysOp DK6VV OV Merzig Q04 2
20180620092938	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0VKL-10:!SysOp DK6VV OV Merzig Q04 2
20180620095759	DB0MZG-2>APSAAR,WIDE2-1,qAR,F5ZEE:!SysOp DK6VV OV Merzig Q04 2
20180620095833	DB0MZG-2>APSAAR,F5ZEE*,qAR,HB9F-10:!SysOp DK6VV OV Merzig Q04 2
20180620102623	DB0MZG-2>APSAAR,WIDE2-1,qAR,F5ZEE:!SysOp DK6VV OV Merzig Q04 2
20180620105446	DB0MZG-2>APSAAR,WIDE2-1,qAR,F5ZEE:!SysOp DK6VV OV Merzig Q04 2
20180620112310	DB0MZG-2>APSAAR,WIDE2-1,qAR,F5ZEE:!SysOp DK6VV OV Merzig Q04 2
20180620115134	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0VKL-10:!SysOp DK6VV OV Merzig Q04 2
20180620121957	DB0MZG-2>APSAAR,WIDE2-1,qAR,F5ZEE:!SysOp DK6VV OV Merzig Q04 2
20180620124821	DB0MZG-2>APSAAR,WIDE2-1,qAR,F5ZEE:!SysOp DK6VV OV Merzig Q04 2