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
20240518053840DH9NFM-12>APRS,qAO,DB7MM-2:!5014.23N/01128.15E_180/00 g...t048r000p...P...h100b07170 WX-Rodach
20240518062019DH9NFM-12>APRS,qAO,DB7MM-2:!5014.23N/01128.15E_090/00 g...t049r000p...P...h100b07173 WX-Rodach
20240518063044DH9NFM-12>APRS,qAO,DB0WK-10:!5014.23N/01128.15E_.../00 g...t049r000p...P...h100b07175 WX-Rodach
20240518063044DH9NFM-12>APRS,qAR,DG2NES-15:!5014.23N/01128.15E_.../00 g...t049r000p...P...h100b07175 WX-Rodach
20240518065134DH9NFM-12>APRS,qAO,DB7MM-2:!5014.23N/01128.15E_000/00 g...t049r001p...P...h100b07175 WX-Rodach
20240518070158DH9NFM-12>APRS,qAO,DB7MM-2:!5014.23N/01128.15E_000/00 g...t050r001p...P...h100b07180 WX-Rodach
20240518071223DH9NFM-12>APRS,qAO,DB7MM-2:!5014.23N/01128.15E_000/00 g...t050r001p...P...h100b07183 WX-Rodach