APRS Packet Errors for BH6MKM-11 (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
20260209105233BH6MKM-11>APE32A,TCPIP*,qAC,T2HAKATA:!3422.67N/11344.94EyPHG3060APRS 434.640MHz 1200bps
20260209112233BH6MKM-11>APE32A,TCPIP*,qAC,T2HAKATA:!3422.67N/11344.94EyPHG3060APRS 434.640MHz 1200bps
20260209115233BH6MKM-11>APE32A,TCPIP*,qAC,T2HAKATA:!3422.67N/11344.94EyPHG3060APRS 434.640MHz 1200bps
20260209122233BH6MKM-11>APE32A,TCPIP*,qAC,T2HAKATA:!3422.67N/11344.94EyPHG3060APRS 434.640MHz 1200bps
20260209125233BH6MKM-11>APE32A,TCPIP*,qAC,T2HAKATA:!3422.67N/11344.94EyPHG3060APRS 434.640MHz 1200bps
20260209132233BH6MKM-11>APE32A,TCPIP*,qAC,T2HAKATA:!3422.67N/11344.94EyPHG3060APRS 434.640MHz 1200bps
20260209135235BH6MKM-11>APE32A,TCPIP*,qAC,T2HAKATA:!3422.67N/11344.94EyPHG3060APRS 434.640MHz 1200bps
20260209142233BH6MKM-11>APE32A,TCPIP*,qAC,T2HAKATA:!3422.67N/11344.94EyPHG3060APRS 434.640MHz 1200bps
20260209145233BH6MKM-11>APE32A,TCPIP*,qAC,T2HAKATA:!3422.67N/11344.94EyPHG3060APRS 434.640MHz 1200bps
20260209152233BH6MKM-11>APE32A,TCPIP*,qAC,T2HAKATA:!3422.67N/11344.94EyPHG3060APRS 434.640MHz 1200bps
20260209155233BH6MKM-11>APE32A,TCPIP*,qAC,T2HAKATA:!3422.67N/11344.94EyPHG3060APRS 434.640MHz 1200bps
20260209162233BH6MKM-11>APE32A,TCPIP*,qAC,T2HAKATA:!3422.67N/11344.94EyPHG3060APRS 434.640MHz 1200bps