APRS Packet Errors for EA1IRT-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
20260208152532EA1IRT-10>APLOX1,WIDE1-1,qAO,EB1GOD-10:!L8M08Lb%!a XLoRa_Aprs_iGate in63lm P=4.21V
20260208155538EA1IRT-10>APLOX1,TCPIP*,qAC,T2UK:!L8M08Lb%!a XLoRa_Aprs_iGate in63lm P=4.21V
20260208162546EA1IRT-10>APLOX1,WIDE1-1,qAO,EB1GOD-10:!L8M08Lb%!a XLoRa_Aprs_iGate in63lm P=4.20V
20260208165551EA1IRT-10>APLOX1,WIDE1-1,qAO,EB1GOD-10:!L8M08Lb%!a XLoRa_Aprs_iGate in63lm P=4.20V
20260208172557EA1IRT-10>APLOX1,TCPIP*,qAC,T2UK:!L8M08Lb%!a XLoRa_Aprs_iGate in63lm P=4.20V
20260208175601EA1IRT-10>APLOX1,TCPIP*,qAC,T2UK:!L8M08Lb%!a XLoRa_Aprs_iGate in63lm P=4.20V
20260208182605EA1IRT-10>APLOX1,WIDE1-1,qAO,EB1GOD-10:!L8M08Lb%!a XLoRa_Aprs_iGate in63lm P=4.20V
20260208185612EA1IRT-10>APLOX1,WIDE1-1,qAO,EB1GOD-10:!L8M08Lb%!a XLoRa_Aprs_iGate in63lm P=4.21V
20260208192621EA1IRT-10>APLOX1,TCPIP*,qAC,T2UK:!L8M08Lb%!a XLoRa_Aprs_iGate in63lm P=4.20V
20260208195630EA1IRT-10>APLOX1,TCPIP*,qAC,T2UK:!L8M08Lb%!a XLoRa_Aprs_iGate in63lm P=4.20V
20260208202644EA1IRT-10>APLOX1,TCPIP*,qAC,T2UK:!L8M08Lb%!a XLoRa_Aprs_iGate in63lm P=4.20V
20260208205649EA1IRT-10>APLOX1,TCPIP*,qAC,T2UK:!L8M08Lb%!a XLoRa_Aprs_iGate in63lm P=4.20V