APRS Packet Errors for OH1ZJ-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
20260209131244OH1ZJ-10>APLG01,TCPIP*,qAC,T2LAUSITZ:=6026.40NL02303.00E&LoRa iGATE & Digi, Info: github.com/lora-aprs/LoRa_APRS_iGate
20260209132730OH1ZJ-10>APLG01,TCPIP*,qAC,T2CSNGRAD:=6026.40NL02303.00E&LoRa iGATE & Digi, Info: github.com/lora-aprs/LoRa_APRS_iGate
20260209134746OH1ZJ-10>APLRG1,TCPIP*,qAC,T2SPAIN:=L0/{{T<{{a !GLoRa APRS
20260209140247OH1ZJ-10>APLRG1,TCPIP*,qAC,T2SPAIN:=L0/{{T<{{a !GLoRa APRS
20260209140841OH1ZJ-10>APLRG1,TCPIP*,qAC,T2CHILE:=L/v]hT>0ca !GLoRa APRS
20260209141015OH1ZJ-10>APLRG1,TCPIP*,qAC,T2CHILE:=L/v]hT>0ca !GLoRa APRS
20260209142515OH1ZJ-10>APLRG1,TCPIP*,qAC,T2CHILE:=L/v]hT>0ca !GLoRa APRS
20260209144015OH1ZJ-10>APLRG1,TCPIP*,qAC,T2CHILE:=L/v]hT>0ca !GLoRa APRS
20260209145515OH1ZJ-10>APLRG1,TCPIP*,qAC,T2CHILE:=L/v]hT>0ca !GLoRa APRS
20260209151015OH1ZJ-10>APLRG1,TCPIP*,qAC,T2CHILE:=L/v]hT>0ca !GLoRa APRS