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
20250403191402DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_270/00 g...t050r000p...P...h79b10220 WX-Rodach
20250403194516DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_045/00 g...t050r000p...P...h81b10220 WX-Rodach
20250403203719DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_045/00 g...t049r000p...P...h82b10218 WX-Rodach
20250403205808DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_045/00 g...t048r000p...P...h83b10218 WX-Rodach
20250403210833DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_045/00 g...t048r000p...P...h82b10218 WX-Rodach
20250403212922DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_045/00 g...t050r000p...P...h76b10219 WX-Rodach
20250403213947DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_135/00 g...t050r000p...P...h74b10219 WX-Rodach
20250403220036DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_135/00 g...t050r000p...P...h73b10218 WX-Rodach
20250403222125DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_135/00 g...t050r000p...P...h70b10218 WX-Rodach
20250403223150DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_135/00 g...t050r000p...P...h69b10218 WX-Rodach
20250403230304DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_135/00 g...t050r000p...P...h67b10217 WX-Rodach