APRS Packet Errors for UA1ZBE-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
20260208133442UA1ZBE-10>APLG01,TCPIP*,qAC,T2SPB:=6725.85NL03227.21E&LoRa iGATE & Digi, 433.775MHz
20260208171122UA1ZBE-10>APLG01,TCPIP*,qAC,T2SPB:=6725.85NL03227.21E&LoRa iGATE & Digi, 433.775MHz
20260208172622UA1ZBE-10>APLG01,TCPIP*,qAC,T2APATITY:=6725.85NL03227.21E&LoRa iGATE & Digi, 433.775MHz
20260208174122UA1ZBE-10>APLG01,TCPIP*,qAC,T2SPB:=6725.85NL03227.21E&LoRa iGATE & Digi, 433.775MHz
20260208175623UA1ZBE-10>APLG01,TCPIP*,qAC,T2APATITY:=6725.85NL03227.21E&LoRa iGATE & Digi, 433.775MHz
20260208181123UA1ZBE-10>APLG01,TCPIP*,qAC,T2SPB:=6725.85NL03227.21E&LoRa iGATE & Digi, 433.775MHz
20260208182624UA1ZBE-10>APLG01,TCPIP*,qAC,T2APATITY:=6725.85NL03227.21E&LoRa iGATE & Digi, 433.775MHz
20260208184125UA1ZBE-10>APLG01,TCPIP*,qAC,T2APATITY:=6725.85NL03227.21E&LoRa iGATE & Digi, 433.775MHz
20260208185625UA1ZBE-10>APLG01,TCPIP*,qAC,T2SPB:=6725.85NL03227.21E&LoRa iGATE & Digi, 433.775MHz
20260208191126UA1ZBE-10>APLG01,TCPIP*,qAC,T2SPB:=6725.85NL03227.21E&LoRa iGATE & Digi, 433.775MHz