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
20241114004707DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_000/00 g...t035r000p...P...h100b10254 WX-Rodach
20241114010757DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_000/00 g...t035r000p...P...h100b10252 WX-Rodach
20241114012847DH9NFM-12>APRS,qAO,DB7MM-2:!5014.23N/01128.15E_000/00 g...t035r000p...P...h100b10249 WX-Rodach
20241114013912DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_000/00 g...t035r000p...P...h100b10248 WX-Rodach
20241114022051DH9NFM-12>APRS,qAO,DB7MM-2:!5014.23N/01128.15E_090/00 g...t035r000p...P...h100b10245 WX-Rodach
20241114023116DH9NFM-12>APRS,qAO,DB7MM-2:!5014.23N/01128.15E_000/00 g...t035r000p...P...h100b10244 WX-Rodach
20241114030230DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_270/00 g...t035r000p...P...h100b10241 WX-Rodach
20241114032320DH9NFM-12>APRS,qAO,DB7MM-2:!5014.23N/01128.15E_000/00 g...t035r000p...P...h100b10240 WX-Rodach
20241114035434DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_.../00 g...t035r000p...P...h100b10239 WX-Rodach
20241114050728DH9NFM-12>APRS,qAO,DB7MM-2:!5014.23N/01128.15E_000/00 g...t035r000p...P...h100b10239 WX-Rodach
20241114054907DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_000/00 g...t035r000p...P...h100b10239 WX-Rodach