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
20260417112552DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_045/00 g...t061r000p...P...h79b10210 WX-Rodach
20260417113616DH9NFM-12>APRS,qAO,DL1NUX-1:!5014.23N/01128.15E_180/00 g...t064r000p...P...h73b10209 WX-Rodach
20260417121755DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_000/00 g...t065r000p...P...h66b10207 WX-Rodach
20260417142251DH9NFM-12>APRS,qAU,DB0FOR-10:!5014.23N/01128.15E_135/00 g...t064r000p...P...h66b10198 WX-Rodach
20260417143315DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_045/00 g...t065r000p...P...h65b10198 WX-Rodach
20260417144340DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_045/00 g...t064r000p...P...h67b10197 WX-Rodach
20260417145405DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_000/00 g...t063r000p...P...h67b10197 WX-Rodach
20260417150429DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_000/00 g...t063r000p...P...h70b10197 WX-Rodach
20260417164836DH9NFM-12>APRS,qAO,DB7MM-2:!5014.23N/01128.15E_000/00 g...t062r000p...P...h71b10196 WX-Rodach