APRS Packet Errors for JE4YKJ-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
20260208151713JE4YKJ-10>APU25N,TCPIP*,qAC,T2HAKATA:=I=9Ejoab<& BI-Gate yamaguchi-City MINAMI
20260208154712JE4YKJ-10>APU25N,TCPIP*,qAC,T2HAKATA:=I=9Ejoab<& BI-Gate yamaguchi-City MINAMI
20260208161713JE4YKJ-10>APU25N,TCPIP*,qAC,T2HAKATA:=I=9Ejoab<& BI-Gate yamaguchi-City MINAMI
20260208164712JE4YKJ-10>APU25N,TCPIP*,qAC,T2HAKATA:=I=9Ejoab<& BI-Gate yamaguchi-City MINAMI
20260208171712JE4YKJ-10>APU25N,TCPIP*,qAC,T2HAKATA:=I=9Ejoab<& BI-Gate yamaguchi-City MINAMI
20260208174713JE4YKJ-10>APU25N,TCPIP*,qAC,T2HAKATA:=I=9Ejoab<& BI-Gate yamaguchi-City MINAMI
20260208181712JE4YKJ-10>APU25N,TCPIP*,qAC,T2HAKATA:=I=9Ejoab<& BI-Gate yamaguchi-City MINAMI
20260208184712JE4YKJ-10>APU25N,TCPIP*,qAC,T2HAKATA:=I=9Ejoab<& BI-Gate yamaguchi-City MINAMI
20260208191712JE4YKJ-10>APU25N,TCPIP*,qAC,T2HAKATA:=I=9Ejoab<& BI-Gate yamaguchi-City MINAMI
20260208194713JE4YKJ-10>APU25N,TCPIP*,qAC,T2HAKATA:=I=9Ejoab<& BI-Gate yamaguchi-City MINAMI
20260208201711JE4YKJ-10>APU25N,TCPIP*,qAC,T2HAKATA:=I=9Ejoab<& BI-Gate yamaguchi-City MINAMI
20260208204713JE4YKJ-10>APU25N,TCPIP*,qAC,T2HAKATA:=I=9Ejoab<& BI-Gate yamaguchi-City MINAMI