APRS Packet Errors for F4FEB-LO (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
20260208131647F4FEB-LO>APLRG1,TCPIP*,qAC,T2PRT:!L6R/XP.p{a G Igate LoRa APRS Batt=4.16V
20260208134648F4FEB-LO>APLRG1,TCPIP*,qAC,T2PRT:!L6R/XP.p{a G Igate LoRa APRS Batt=4.17V
20260208141648F4FEB-LO>APLRG1,TCPIP*,qAC,T2PRT:!L6R/XP.p{a G Igate LoRa APRS Batt=4.17V
20260208144648F4FEB-LO>APLRG1,TCPIP*,qAC,T2PRT:!L6R/XP.p{a G Igate LoRa APRS Batt=4.16V
20260208151648F4FEB-LO>APLRG1,TCPIP*,qAC,T2PRT:!L6R/XP.p{a G Igate LoRa APRS Batt=4.16V
20260208154648F4FEB-LO>APLRG1,TCPIP*,qAC,T2PRT:!L6R/XP.p{a G Igate LoRa APRS Batt=4.16V
20260208161648F4FEB-LO>APLRG1,TCPIP*,qAC,T2PRT:!L6R/XP.p{a G Igate LoRa APRS Batt=4.16V
20260208164648F4FEB-LO>APLRG1,TCPIP*,qAC,T2PRT:!L6R/XP.p{a G Igate LoRa APRS Batt=4.14V
20260208171605F4FEB-LO>APLRG1,TCPIP*,qAC,T2FINLAND:!L6R/XP.p{a G Igate LoRa APRS Batt=4.13V
20260208174606F4FEB-LO>APLRG1,TCPIP*,qAC,T2FINLAND:!L6R/XP.p{a G Igate LoRa APRS Batt=4.12V
20260208181607F4FEB-LO>APLRG1,TCPIP*,qAC,T2FINLAND:!L6R/XP.p{a G Igate LoRa APRS Batt=4.16V
20260208184607F4FEB-LO>APLRG1,TCPIP*,qAC,T2FINLAND:!L6R/XP.p{a G Igate LoRa APRS Batt=4.15V