APRS Packet Errors for DL1NJK (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
20260209115131DL1NJK>APRX29,DB0WOT,WIDE1*,WIDE2-1,qAR,DB0FS-10:!5312.33NR00933.92E&Home station @EDHU 1.2degC 98% cloudy
20260209143205DL1NJK>APRX29,DB0WOT,WIDE1*,WIDE2-1,qAR,DB0HFT-10:!5312.33NR00933.92E&Home station @EDHU 1.3degC 95% cloudy
20260209150235DL1NJK>APRX29,DB0WOT,WIDE1*,WIDE2-1,qAR,DB0FS-10:!5312.33NR00933.92E&Home station @EDHU 1.0degC 96% cloudy
20260209153044DL1NJK>APRX29,DB0WOT,WIDE1*,WIDE2-1,qAR,DB0HFT-10:!5312.33NR00933.92E&Home station @EDHU 0.9degC 97% cloudy
20260209153050DL1NJK>APRX29,DB0WOT,WIDE1,DB0OL-10*,qAR,DB0PDF-10:!5312.33NR00933.92E&Home station @EDHU 0.9degC 97% cloudy`
20260209155205DL1NJK>APRX29,DB0WOT,WIDE1*,WIDE2-1,qAR,DB0FS-10:!5312.33NR00933.92E&Home station @EDHU 0.7degC 98% cloudy
20260209155208DL1NJK>APRX29,DB0WOT,WIDE1,DB0OL-10*,qAR,DB0PDF-10:!5312.33NR00933.92E&Home station @EDHU 0.7degC 98% cloudy™ô
20260209155624DL1NJK>APRX29,DB0WOT,WIDE1*,WIDE2-1,qAR,DB0FS-10:!5312.33NR00933.92E&Home station @EDHU 0.7degC 98% cloudy