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
20260321060337DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_045/00 g...t036r000p...P...h100b10148 WX-Rodach
20260321061402DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_045/00 g...t037r000p...P...h100b10149 WX-Rodach
20260321062426DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_000/00 g...t038r000p...P...h100b10149 WX-Rodach
20260321063451DH9NFM-12>APRS,qAO,DL1NUX-1:!5014.23N/01128.15E_045/00 g...t039r000p...P...h100b10149 WX-Rodach
20260321064516DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_000/00 g...t039r000p...P...h100b10149 WX-Rodach
20260321065541DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_180/00 g...t040r000p...P...h100b10149 WX-Rodach
20260321070606DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_045/00 g...t040r000p...P...h100b10150 WX-Rodach
20260321080834DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_000/00 g...t043r000p...P...h100b10148 WX-Rodach
20260321083949DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_135/00 g...t046r000p...P...h100b10148 WX-Rodach
20260321085014DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_135/00 g...t047r000p...P...h100b10147 WX-Rodach