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
20261112100903DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_000/00 g...t047r001p...P...h100b09844 WX-Rodach
20261112110107DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_045/00 g...t047r001p...P...h100b09840 WX-Rodach
20261112112156DH9NFM-12>APRS,qAO,DL1NUX-1:!5014.23N/01128.15E_000/00 g...t047r001p...P...h100b09838 WX-Rodach
20261112115311DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_000/00 g...t047r000p...P...h100b09837 WX-Rodach
20261112121400DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_180/00 g...t047r000p...P...h100b09835 WX-Rodach
20261112130604DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_045/00 g...t041r002p...P...h100b09843 WX-Rodach
20261112133719DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_180/00 g...t039r000p...P...h100b09848 WX-Rodach
20261112134744DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_045/00 g...t039r000p...P...h100b09850 WX-Rodach
20261112154216DH9NFM-12>APRS,qAO,DL1NUX-1:!5014.23N/01128.15E_225/00 g...t035r000p...P...h100b09881 WX-Rodach