APRS Packet Errors for DH9NFM-12 (last 24 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
20261024122835	DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_000/00 g...t039r000p...P...h100b10170 WX-Rodach
20261024125949	DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_045/00 g...t039r000p...P...h100b10169 WX-Rodach
20261024133103	DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_000/00 g...t039r000p...P...h100b10167 WX-Rodach
20261024140218	DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_090/00 g...t040r000p...P...h100b10166 WX-Rodach
20261024151512	DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_180/00 g...t041r000p...P...h100b10158 WX-Rodach