APRS Packet Errors for I4VBO-2 (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
20260208181539	I4VBO-2>APLRG1,TCPIP*,qAC,T2PANAMA:!L7{z>Pzpa GIGate LoRa Borgotaro (PR)
20260208184539	I4VBO-2>APLRG1,TCPIP*,qAC,T2PANAMA:!L7{z>Pzpa GIGate LoRa Borgotaro (PR)
20260208191539	I4VBO-2>APLRG1,TCPIP*,qAC,T2PANAMA:!L7{z>Pzpa GIGate LoRa Borgotaro (PR)
20260208194539	I4VBO-2>APLRG1,TCPIP*,qAC,T2PANAMA:!L7{z>Pzpa GIGate LoRa Borgotaro (PR)
20260208201539	I4VBO-2>APLRG1,TCPIP*,qAC,T2PANAMA:!L7{z>Pzpa GIGate LoRa Borgotaro (PR)
20260208204539	I4VBO-2>APLRG1,TCPIP*,qAC,T2PANAMA:!L7{z>Pzpa GIGate LoRa Borgotaro (PR)
20260208211539	I4VBO-2>APLRG1,TCPIP*,qAC,T2PANAMA:!L7{z>Pzpa GIGate LoRa Borgotaro (PR)
20260208214539	I4VBO-2>APLRG1,TCPIP*,qAC,T2PANAMA:!L7{z>Pzpa GIGate LoRa Borgotaro (PR)
20260208221540	I4VBO-2>APLRG1,TCPIP*,qAC,T2PANAMA:!L7{z>Pzpa GIGate LoRa Borgotaro (PR)
20260208224540	I4VBO-2>APLRG1,TCPIP*,qAC,T2PANAMA:!L7{z>Pzpa GIGate LoRa Borgotaro (PR)
20260208231540	I4VBO-2>APLRG1,TCPIP*,qAC,T2PANAMA:!L7{z>Pzpa GIGate LoRa Borgotaro (PR)
20260208234540	I4VBO-2>APLRG1,TCPIP*,qAC,T2PANAMA:!L7{z>Pzpa GIGate LoRa Borgotaro (PR)