APRS Packet Errors for M7MOY-10 (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
20260209122243M7MOY-10>APDW16,TCPIP*,qAC,T2CSNGRAD:!5159.58NS00058.55W#PHG2030M7MOY APRS Buckingham UK
20260209125243M7MOY-10>APDW16,TCPIP*,qAC,T2CSNGRAD:!5159.58NS00058.55W#PHG2030M7MOY APRS Buckingham UK
20260209132243M7MOY-10>APDW16,TCPIP*,qAC,T2CSNGRAD:!5159.58NS00058.55W#PHG2030M7MOY APRS Buckingham UK
20260209135243M7MOY-10>APDW16,TCPIP*,qAC,T2CSNGRAD:!5159.58NS00058.55W#PHG2030M7MOY APRS Buckingham UK
20260209142243M7MOY-10>APDW16,TCPIP*,qAC,T2CSNGRAD:!5159.58NS00058.55W#PHG2030M7MOY APRS Buckingham UK
20260209145243M7MOY-10>APDW16,TCPIP*,qAC,T2CSNGRAD:!5159.58NS00058.55W#PHG2030M7MOY APRS Buckingham UK
20260209152243M7MOY-10>APDW16,TCPIP*,qAC,T2CSNGRAD:!5159.58NS00058.55W#PHG2030M7MOY APRS Buckingham UK
20260209155243M7MOY-10>APDW16,TCPIP*,qAC,T2CSNGRAD:!5159.58NS00058.55W#PHG2030M7MOY APRS Buckingham UK
20260209162243M7MOY-10>APDW16,TCPIP*,qAC,T2CSNGRAD:!5159.58NS00058.55W#PHG2030M7MOY APRS Buckingham UK
20260209165243M7MOY-10>APDW16,TCPIP*,qAC,T2CSNGRAD:!5159.58NS00058.55W#PHG2030M7MOY APRS Buckingham UK
20260209172243M7MOY-10>APDW16,TCPIP*,qAC,T2CSNGRAD:!5159.58NS00058.55W#PHG2030M7MOY APRS Buckingham UK
20260209175243M7MOY-10>APDW16,TCPIP*,qAC,T2CSNGRAD:!5159.58NS00058.55W#PHG2030M7MOY APRS Buckingham UK