APRS Packet Errors for ON2ON-16 (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
20260208201056ON2ON-16>APLRG1,TCPIP*,qAC,T2ERFURT:=L4TM*OY3X_ !G.../...g...t066h43b10088Igate Last firmware 2026 Jan - SX1278
20260208205056ON2ON-16>APLRG1,TCPIP*,qAC,T2ERFURT:=L4TM*OY3X_ !G.../...g...t065h42b10087Igate Last firmware 2026 Jan - SX1278
20260208213056ON2ON-16>APLRG1,TCPIP*,qAC,T2ERFURT:=L4TM*OY3X_ !G.../...g...t066h42b10086Igate Last firmware 2026 Jan - SX1278
20260208221056ON2ON-16>APLRG1,TCPIP*,qAC,T2ERFURT:=L4TM*OY3X_ !G.../...g...t065h41b10085Igate Last firmware 2026 Jan - SX1278
20260208225056ON2ON-16>APLRG1,TCPIP*,qAC,T2ERFURT:=L4TM*OY3X_ !G.../...g...t065h41b10084Igate Last firmware 2026 Jan - SX1278
20260209001056ON2ON-16>APLRG1,TCPIP*,qAC,T2ERFURT:=L4TM*OY3X_ !G.../...g...t065h42b10080Igate Last firmware 2026 Jan - SX1278
20260209005056ON2ON-16>APLRG1,TCPIP*,qAC,T2ERFURT:=L4TM*OY3X_ !G.../...g...t065h43b10077Igate Last firmware 2026 Jan - SX1278
20260209013056ON2ON-16>APLRG1,TCPIP*,qAC,T2ERFURT:=L4TM*OY3X_ !G.../...g...t065h43b10075Igate Last firmware 2026 Jan - SX1278