APRS Packet Errors for JR0ZFI-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
20260209110141	JR0ZFI-10>APX218,TCPIP*,qAC,T2FUKUOKA:=3614.70NI13753.33E&PHG1000xastir & picoAPRS
20260209113142	JR0ZFI-10>APX218,TCPIP*,qAC,T2FUKUOKA:=3614.70NI13753.33E&PHG1000xastir & picoAPRS
20260209120143	JR0ZFI-10>APX218,TCPIP*,qAC,T2FUKUOKA:=3614.70NI13753.33E&PHG1000xastir & picoAPRS
20260209123144	JR0ZFI-10>APX218,TCPIP*,qAC,T2FUKUOKA:=3614.70NI13753.33E&PHG1000xastir & picoAPRS
20260209130145	JR0ZFI-10>APX218,TCPIP*,qAC,T2FUKUOKA:=3614.70NI13753.33E&PHG1000xastir & picoAPRS
20260209133146	JR0ZFI-10>APX218,TCPIP*,qAC,T2FUKUOKA:=3614.70NI13753.33E&PHG1000xastir & picoAPRS
20260209140147	JR0ZFI-10>APX218,TCPIP*,qAC,T2FUKUOKA:=3614.70NI13753.33E&PHG1000xastir & picoAPRS
20260209143148	JR0ZFI-10>APX218,TCPIP*,qAC,T2FUKUOKA:=3614.70NI13753.33E&PHG1000xastir & picoAPRS
20260209150149	JR0ZFI-10>APX218,TCPIP*,qAC,T2FUKUOKA:=3614.70NI13753.33E&PHG1000xastir & picoAPRS
20260209153150	JR0ZFI-10>APX218,TCPIP*,qAC,T2FUKUOKA:=3614.70NI13753.33E&PHG1000xastir & picoAPRS
20260209160151	JR0ZFI-10>APX218,TCPIP*,qAC,T2FUKUOKA:=3614.70NI13753.33E&PHG1000xastir & picoAPRS
20260209163152	JR0ZFI-10>APX218,TCPIP*,qAC,T2FUKUOKA:=3614.70NI13753.33E&PHG1000xastir & picoAPRS