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
20260329171606DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_000/00 g...t037r000p...P...h83b10223 WX-Rodach
20260329183923DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_135/00 g...t035r000p...P...h94b10219 WX-Rodach
20260329192102DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_000/00 g...t035r000p...P...h97b10214 WX-Rodach
20260329194152DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_000/00 g...t034r000p...P...h100b10214 WX-Rodach
20260329200241DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_000/00 g...t034r000p...P...h100b10214 WX-Rodach
20260329201306DH9NFM-12>APRS,qAO,DB0NU-10:!5014.23N/01128.15E_045/00 g...t034r000p...P...h100b10215 WX-Rodach
20260329202331DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_000/00 g...t034r000p...P...h100b10214 WX-Rodach
20260329203356DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_.../00 g...t034r000p...P...h100b10212 WX-Rodach
20260329205445DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_090/00 g...t034r000p...P...h100b10211 WX-Rodach
20260329211535DH9NFM-12>APRS,qAO,DG9NGK-1:!5014.23N/01128.15E_000/00 g...t034r000p...P...h100b10210 WX-Rodach
20260329214650DH9NFM-12>APRS,qAO,DB0NH-1:!5014.23N/01128.15E_090/00 g...t033r000p...P...h100b10205 WX-Rodach