APRS Packet Errors for BH9DKQ-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
20260208133916BH9DKQ-10>AP51WG,TCPIP*,qAC,T2TOKYO:!3456.50N/10935.61ErPuCheng @144.640M
20260208134917BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208135917BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208140917BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208141918BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208142918BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208143919BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208144919BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208145919BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208150920BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208151920BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208152921BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208153921BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208154921BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208155922BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208160922BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208161922BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208162922BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208163923BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208164923BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208165923BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208170924BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208171924BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208172924BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208173925BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208174925BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208175925BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208180925BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208181926BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208182926BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208183927BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208184927BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208185927BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208190927BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M
20260208191927BH9DKQ-10>AP51WG,TCPIP*,qAC,T2HAKATA:!3456.50N/10935.61ErPuCheng @144.640M