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
20261002172335DH9NFM-12>APRS,qAO,DB7MM-2:!5014.23N/01128.15E_000/00 g...t054r000p...P...h100b10299 WX-Rodach
20261002174424DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_045/00 g...t054r000p...P...h100b10299 WX-Rodach
20261002184653DH9NFM-12>APRS,qAO,DB7MM-2:!5014.23N/01128.15E_000/00 g...t054r000p...P...h100b10298 WX-Rodach
20261002195947DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_090/00 g...t054r000p...P...h100b10297 WX-Rodach
20261002202037DH9NFM-12>APRS,qAO,DB7MM-2:!5014.23N/01128.15E_180/00 g...t054r000p...P...h100b10296 WX-Rodach
20261002203101DH9NFM-12>APRS,qAO,DB7MM-2:!5014.23N/01128.15E_.../00 g...t054r000p...P...h100b10296 WX-Rodach
20261002205151DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_090/00 g...t054r000p...P...h100b10296 WX-Rodach
20261002212306DH9NFM-12>APRS,qAO,DB7MM-2:!5014.23N/01128.15E_045/00 g...t054r000p...P...h100b10296 WX-Rodach
20261002221509DH9NFM-12>APRS,qAO,DB7MM-2:!5014.23N/01128.15E_000/00 g...t054r000p...P...h100b10295 WX-Rodach
20261002222534DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_000/00 g...t054r000p...P...h100b10296 WX-Rodach