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
20261120121118DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_000/00 g...t041r000p...P...h100b10274 WX-Rodach
20261120140551DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_225/00 g...t040r004p...P...h100b10264 WX-Rodach
20261120142641DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_000/00 g...t040r000p...P...h100b10265 WX-Rodach
20261120143706DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_000/00 g...t040r002p...P...h100b10266 WX-Rodach
20261120144730DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_225/00 g...t040r003p...P...h100b10266 WX-Rodach
20261120145755DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_000/00 g...t040r004p...P...h100b10268 WX-Rodach
20261120154959DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_000/00 g...t040r001p...P...h100b10272 WX-Rodach
20261120165228DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_045/00 g...t040r000p...P...h100b10284 WX-Rodach
20261120172343DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_225/00 g...t040r003p...P...h100b10289 WX-Rodach
20261120173407DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_000/00 g...t040r000p...P...h100b10290 WX-Rodach