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
20261002173252	DB0MZG-2>APSAAR,WIDE2-1,qAR,F8EBY-2:!SysOp DK6VV OV Merzig Q04 2
20261002180115	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0DTR-10:!SysOp DK6VV OV Merzig Q04 2
20261002182939	DB0MZG-2>APSAAR,WIDE2-1,qAR,F8EBY-2:!SysOp DK6VV OV Merzig Q04 2
20261002185804	DB0MZG-2>APSAAR,WIDE2-1,qAR,F8EBY-2:!SysOp DK6VV OV Merzig Q04 2
20261002192626	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0DTR-10:!SysOp DK6VV OV Merzig Q04 2
20261002195450	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0UT-10:!SysOp DK6VV OV Merzig Q04 2
20261002202313	DB0MZG-2>APSAAR,WIDE2-1,qAR,F8EBY-2:!SysOp DK6VV OV Merzig Q04 2
20261002205138	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0UT-10:!SysOp DK6VV OV Merzig Q04 2
20261002212001	DB0MZG-2>APSAAR,WIDE2-1,qAR,LX0WX-13:!SysOp DK6VV OV Merzig Q04 2
20261002214825	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0DTR-10:!SysOp DK6VV OV Merzig Q04 2
20261002221649	DB0MZG-2>APSAAR,WIDE2-1,qAR,F8EBY-2:!SysOp DK6VV OV Merzig Q04 2
20261002224511	DB0MZG-2>APSAAR,WIDE2-1,qAR,DB0SAB-2:!SysOp DK6VV OV Merzig Q04 2
20261002231336	DB0MZG-2>APSAAR,WIDE2-1,qAR,F8EBY-2:!SysOp DK6VV OV Merzig Q04 2