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
20251015072545DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_045/00 g...t047r000p...P...h100b10242 WX-Rodach
20251015073610DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_045/00 g...t047r000p...P...h100b10242 WX-Rodach
20251015080724DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_045/00 g...t049r000p...P...h100b10242 WX-Rodach
20251015083839DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_000/00 g...t049r000p...P...h100b10243 WX-Rodach
20251015094107DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_045/00 g...t051r000p...P...h100b10244 WX-Rodach
20251015100157DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_000/00 g...t051r000p...P...h100b10244 WX-Rodach
20251015101222DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_045/00 g...t051r000p...P...h100b10244 WX-Rodach
20251015120655DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_045/00 g...t052r000p...P...h100b10238 WX-Rodach
20251015121720DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_045/00 g...t051r000p...P...h100b10238 WX-Rodach
20251015124834DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_045/00 g...t050r000p...P...h100b10237 WX-Rodach
20251015125859DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_000/00 g...t050r000p...P...h100b10237 WX-Rodach