APRS Packet Errors for JR6PUE-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
20260209103915	JR6PUE-10>APX217,TCPIP*,qAC,T2FUKUOKA:=3351.15NI13042.78E&PHG3388XASTIR I-GATE 431.04MHz
20260209110916	JR6PUE-10>APX217,TCPIP*,qAC,T2FUKUOKA:=3351.15NI13042.78E&PHG3388XASTIR I-GATE 431.04MHz
20260209113917	JR6PUE-10>APX217,TCPIP*,qAC,T2FUKUOKA:=3351.15NI13042.78E&PHG3388XASTIR I-GATE 431.04MHz
20260209120918	JR6PUE-10>APX217,TCPIP*,qAC,T2FUKUOKA:=3351.15NI13042.78E&PHG3388XASTIR I-GATE 431.04MHz
20260209123919	JR6PUE-10>APX217,TCPIP*,qAC,T2FUKUOKA:=3351.15NI13042.78E&PHG3388XASTIR I-GATE 431.04MHz
20260209130920	JR6PUE-10>APX217,TCPIP*,qAC,T2FUKUOKA:=3351.15NI13042.78E&PHG3388XASTIR I-GATE 431.04MHz
20260209133921	JR6PUE-10>APX217,TCPIP*,qAC,T2FUKUOKA:=3351.15NI13042.78E&PHG3388XASTIR I-GATE 431.04MHz
20260209140922	JR6PUE-10>APX217,TCPIP*,qAC,T2FUKUOKA:=3351.15NI13042.78E&PHG3388XASTIR I-GATE 431.04MHz
20260209143923	JR6PUE-10>APX217,TCPIP*,qAC,T2FUKUOKA:=3351.15NI13042.78E&PHG3388XASTIR I-GATE 431.04MHz
20260209150924	JR6PUE-10>APX217,TCPIP*,qAC,T2FUKUOKA:=3351.15NI13042.78E&PHG3388XASTIR I-GATE 431.04MHz
20260209153925	JR6PUE-10>APX217,TCPIP*,qAC,T2FUKUOKA:=3351.15NI13042.78E&PHG3388XASTIR I-GATE 431.04MHz
20260209160926	JR6PUE-10>APX217,TCPIP*,qAC,T2FUKUOKA:=3351.15NI13042.78E&PHG3388XASTIR I-GATE 431.04MHz