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
20180426000452	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0VKL-10:!SysOp DK6VV OV Merzig Q04 2
20180426003316	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0VKL-10:!SysOp DK6VV OV Merzig Q04 2
20180426010139	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0VKL-10:!SysOp DK6VV OV Merzig Q04 2
20180426013003	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0VKL-10:!SysOp DK6VV OV Merzig Q04 2
20180426015827	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0VKL-10:!SysOp DK6VV OV Merzig Q04 2
20180426022649	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0VKL-10:!SysOp DK6VV OV Merzig Q04 2
20180426025515	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0VKL-10:!SysOp DK6VV OV Merzig Q04 2
20180426025605	DB0MZG-2>APSAAR,F5ZEE*,qAS,DO5DHA-10:!SysOp DK6VV OV Merzig Q04 2
20180426032337	DB0MZG-2>APSAAR,WIDE2-1,qAR,F5ZEE:!SysOp DK6VV OV Merzig Q04 2
20180426035201	DB0MZG-2>APSAAR,WIDE2-1,qAR,F5ZEE:!SysOp DK6VV OV Merzig Q04 2
20180426042025	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0VKL-10:!SysOp DK6VV OV Merzig Q04 2
20180426044848	DB0MZG-2>APSAAR,WIDE2-1,qAR,F5ZEE:!SysOp DK6VV OV Merzig Q04 2
20180426051713	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0VKL-10:!SysOp DK6VV OV Merzig Q04 2
20180426054536	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0VKL-10:!SysOp DK6VV OV Merzig Q04 2