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
20261019092526DH9NFM-12>APRS,qAU,DB0FOR-10:!5014.23N/01128.15E_135/00 g...t042r000p...P...h100b10261 WX-Rodach
20261019095640DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_135/00 g...t042r000p...P...h100b10263 WX-Rodach
20261019105909DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_000/00 g...t042r000p...P...h100b10260 WX-Rodach
20261019111959DH9NFM-12>APRS,qAO,DL1NUX-1:!5014.23N/01128.15E_135/00 g...t042r000p...P...h100b10258 WX-Rodach
20261019121203DH9NFM-12>APRS,qAO,DL1NUX-1:!5014.23N/01128.15E_000/00 g...t042r000p...P...h100b10256 WX-Rodach
20261019132456DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_000/00 g...t043r000p...P...h100b10257 WX-Rodach
20261019133521DH9NFM-12>APRS,qAO,DL1NUX-1:!5014.23N/01128.15E_135/00 g...t043r000p...P...h100b10257 WX-Rodach
20261019134546DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_045/00 g...t043r000p...P...h100b10257 WX-Rodach
20261019142725DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_000/00 g...t044r000p...P...h100b10254 WX-Rodach