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
20251018015407DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_045/00 g...t043r000p...P...h100b10220 WX-Rodach
20251018022521DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_180/00 g...t042r000p...P...h100b10221 WX-Rodach
20251018023546DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_045/00 g...t042r000p...P...h100b10221 WX-Rodach
20251018024611DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_090/00 g...t042r001p...P...h100b10222 WX-Rodach
20251018025636DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_045/00 g...t042r001p...P...h100b10222 WX-Rodach
20251018030700DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_045/00 g...t041r001p...P...h100b10224 WX-Rodach
20251018032750DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_090/00 g...t040r000p...P...h100b10226 WX-Rodach
20251018044044DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_135/00 g...t038r000p...P...h100b10229 WX-Rodach
20251018054313DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_000/00 g...t037r000p...P...h100b10234 WX-Rodach
20251018064541DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_045/00 g...t038r000p...P...h100b10241 WX-Rodach
20251018065606DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_045/00 g...t039r000p...P...h100b10243 WX-Rodach