APRS Packet Errors for JE6JVD-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
20260209094336JE6JVD-10>APX219,TCPIP*,qAC,T2FUKUOKA:=3347.78NI13043.92E&PHG3230XASTIR IGATE 144.66MHz 1200bps
20260209101337JE6JVD-10>APX219,TCPIP*,qAC,T2FUKUOKA:=3347.78NI13043.92E&PHG3230XASTIR IGATE 144.66MHz 1200bps
20260209104338JE6JVD-10>APX219,TCPIP*,qAC,T2FUKUOKA:=3347.78NI13043.92E&PHG3230XASTIR IGATE 144.66MHz 1200bps
20260209111339JE6JVD-10>APX219,TCPIP*,qAC,T2FUKUOKA:=3347.78NI13043.92E&PHG3230XASTIR IGATE 144.66MHz 1200bps
20260209114340JE6JVD-10>APX219,TCPIP*,qAC,T2FUKUOKA:=3347.78NI13043.92E&PHG3230XASTIR IGATE 144.66MHz 1200bps
20260209121341JE6JVD-10>APX219,TCPIP*,qAC,T2FUKUOKA:=3347.78NI13043.92E&PHG3230XASTIR IGATE 144.66MHz 1200bps
20260209124342JE6JVD-10>APX219,TCPIP*,qAC,T2FUKUOKA:=3347.78NI13043.92E&PHG3230XASTIR IGATE 144.66MHz 1200bps
20260209132801JE6JVD-10>APX219,TCPIP*,qAC,T2FUKUOKA:=3347.78NI13043.92E&PHG3230XASTIR IGATE 144.66MHz 1200bps
20260209135801JE6JVD-10>APX219,TCPIP*,qAC,T2FUKUOKA:=3347.78NI13043.92E&PHG3230XASTIR IGATE 144.66MHz 1200bps
20260209142802JE6JVD-10>APX219,TCPIP*,qAC,T2FUKUOKA:=3347.78NI13043.92E&PHG3230XASTIR IGATE 144.66MHz 1200bps
20260209145803JE6JVD-10>APX219,TCPIP*,qAC,T2FUKUOKA:=3347.78NI13043.92E&PHG3230XASTIR IGATE 144.66MHz 1200bps