APRS Packet Errors for DB0GRZ (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
20180618170806DB0GRZ>APNU19,OK0DJ-1*,WIDE2-2,qAR,OK0DJ-1:!5109.67N/01456.73# *Goerlitz* OV S08
20180618173806DB0GRZ>APNU19,OK0DJ-1*,WIDE2-2,qAR,OK0DJ-1:!5109.67N/01456.73# *Goerlitz* OV S08
20180618180807DB0GRZ>APNU19,OK0DJ-1*,WIDE2-2,qAR,OK0DJ-1:!5109.67N/01456.73# *Goerlitz* OV S08
20180618183807DB0GRZ>APNU19,OK0DJ-1*,WIDE2-2,qAR,OK0DJ-1:!5109.67N/01456.73# *Goerlitz* OV S08
20180618190824DB0GRZ>APNU19,DB0SPB,WIDE1,DB0SPN,DB0LDS,WIDE2*,qAR,DB0ZOD:!5109.67N/01456.73# *Goerlitz* OV S08
20180618193810DB0GRZ>APNU19,DB0SPB,WIDE1,OK0DJ-1*,WIDE2-1,qAR,OK0DJ-1:!5109.67N/01456.73# *Goerlitz* OV S08
20180618203809DB0GRZ>APNU19,OK0DJ-1*,WIDE2-2,qAR,OK0DJ-1:!5109.67N/01456.73# *Goerlitz* OV S08
20180618210810DB0GRZ>APNU19,OK0DJ-1*,WIDE2-2,qAR,OK0DJ-1,T2CZECH:!5109.67N/01456.73# *Goerlitz* OV S08
20180618212102DB0GRZ>APNU19,OK0DJ-1*,WIDE2-2,qAR,OK1LOL-1:!5109.67N/01456.73# *Goerlitz* OV S08
20180618213810DB0GRZ>APNU19,OK0DJ-1*,WIDE2-2,qAR,OK0DJ-1:!5109.67N/01456.73# *Goerlitz* OV S08
20180618220812DB0GRZ>APNU19,DB0SPB,WIDE1,OK0DJ-1*,WIDE2-1,qAR,OK0DJ-1:!5109.67N/01456.73# *Goerlitz* OV S08
20180618223813DB0GRZ>APNU19,DB0SPB,WIDE1,OK0BBK-2*,WIDE2-1,qAR,OK1LOL-1:!5109.67N/01456.73# *Goerlitz* OV S08