APRS Packet Errors for DH9NFM-12 (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
20260818141052DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_180/00 g...t057r000p...P...h100b10108 WX-Rodach
20260818144207DH9NFM-12>APRS,qAU,DB0FOR-10:!5014.23N/01128.15E_090/00 g...t057r001p...P...h100b10107 WX-Rodach
20260818151321DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_000/00 g...t058r001p...P...h100b10106 WX-Rodach
20260818152346DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_090/00 g...t058r001p...P...h100b10105 WX-Rodach
20260818160525DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_000/00 g...t058r000p...P...h100b10103 WX-Rodach
20260818162615DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_000/00 g...t058r000p...P...h100b10103 WX-Rodach
20260818171819DH9NFM-12>APRS,qAO,DB7MM-2:!5014.23N/01128.15E_000/00 g...t058r000p...P...h100b10100 WX-Rodach
20260818172844DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_090/00 g...t059r000p...P...h100b10101 WX-Rodach
20260818190227DH9NFM-12>APRS,qAO,DB7MM-2:!5014.23N/01128.15E_090/00 g...t059r000p...P...h100b10104 WX-Rodach