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
20170921154955	DB0MZG-2>APSAAR,WIDE2-1,qAR,DC0VZ-10:!SysOp DK6VV OV Merzig Q04 2
20170921161818	DB0MZG-2>APSAAR,WIDE2-1,qAR,F5ZEE:!SysOp DK6VV OV Merzig Q04 2
20170921164643	DB0MZG-2>APSAAR,WIDE2-1,qAR,F5ZEE:!SysOp DK6VV OV Merzig Q04 2
20170921171505	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0DTR-10:!SysOp DK6VV OV Merzig Q04 2
20170921174330	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0UT-10:!SysOp DK6VV OV Merzig Q04 2
20170921181153	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0UT-10:!SysOp DK6VV OV Merzig Q04 2
20170921184017	DB0MZG-2>APSAAR,WIDE2-1,qAR,DC0VZ-10:!SysOp DK6VV OV Merzig Q04 2
20170921190840	DB0MZG-2>APSAAR,WIDE2-1,qAR,DC0VZ-10:!SysOp DK6VV OV Merzig Q04 2
20170921193705	DB0MZG-2>APSAAR,WIDE2-1,qAR,F5ZEE:!SysOp DK6VV OV Merzig Q04 2
20170921200528	DB0MZG-2>APSAAR,WIDE2-1,qAR,F5ZEE:!SysOp DK6VV OV Merzig Q04 2
20170921203352	DB0MZG-2>APSAAR,WIDE2-1,qAR,F5ZEE:!SysOp DK6VV OV Merzig Q04 2
20170921210217	DB0MZG-2>APSAAR,WIDE2-1,qAR,F5ZEE:!SysOp DK6VV OV Merzig Q04 2