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
20181214143009	DB0MZG-2>APSAAR,WIDE2-1,qAR,F5ZEE:!SysOp DK6VV OV Merzig Q04 2
20181214145833	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0DTR-10:!SysOp DK6VV OV Merzig Q04 2
20181214152656	DB0MZG-2>APSAAR,WIDE2-1,qAR,F5ZEE:!SysOp DK6VV OV Merzig Q04 2
20181214155521	DB0MZG-2>APSAAR,WIDE2-1,qAR,F5ZEE:!SysOp DK6VV OV Merzig Q04 2
20181214162343	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0DTR-10:!SysOp DK6VV OV Merzig Q04 2
20181214165207	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0DTR-10:!SysOp DK6VV OV Merzig Q04 2
20181214172031	DB0MZG-2>APSAAR,WIDE2-1,qAR,F5ZEE:!SysOp DK6VV OV Merzig Q04 2
20181214174856	DB0MZG-2>APSAAR,WIDE2-1,qAR,F5ZEE:!SysOp DK6VV OV Merzig Q04 2
20181214181718	DB0MZG-2>APSAAR,WIDE2-1,qAR,F5ZEE:!SysOp DK6VV OV Merzig Q04 2
20181214184542	DB0MZG-2>APSAAR,DB0HWR-5,WIDE2*,qAR,DO0YA-4:!SysOp DK6VV OV Merzig Q04 2
20181214191406	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0DTR-10:!SysOp DK6VV OV Merzig Q04 2
20181214194229	DB0MZG-2>APSAAR,WIDE2-1,qAR,DF2OO-2:!SysOp DK6VV OV Merzig Q04 2
20181214201054	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0DTR-10:!SysOp DK6VV OV Merzig Q04 2