APRS Packet Errors for PA0RNH-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
20260209120809PA0RNH-10>APSN01,TCPIP*,qAC,T2CAEAST:=5246.12N#00505.76E2CSN iGate
20260209123813PA0RNH-10>APSN01,TCPIP*,qAC,T2MCI:=5246.13N#00505.74E2CSN iGate
20260209130814PA0RNH-10>APSN01,TCPIP*,qAC,T2MCI:=5246.13N#00505.77E2CSN iGate
20260209133816PA0RNH-10>APSN01,TCPIP*,qAC,T2CAEAST:=5246.14N#00505.74E2CSN iGate
20260209140818PA0RNH-10>APSN01,TCPIP*,qAC,T2CAEAST:=5246.13N#00505.75E2CSN iGate
20260209143820PA0RNH-10>APSN01,TCPIP*,qAC,T2TEXAS:=5246.14N#00505.74E2CSN iGate
20260209150821PA0RNH-10>APSN01,TCPIP*,qAC,T2TEXAS:=5246.14N#00505.74E2CSN iGate
20260209153823PA0RNH-10>APSN01,TCPIP*,qAC,T2USANW:=5246.14N#00505.75E2CSN iGate
20260209160824PA0RNH-10>APSN01,TCPIP*,qAC,T2USANW:=5246.15N#00505.74E2CSN iGate
20260209163826PA0RNH-10>APSN01,TCPIP*,qAC,T2ALBERTA:=5246.15N#00505.74E2CSN iGate
20260209170827PA0RNH-10>APSN01,TCPIP*,qAC,T2ALBERTA:=5246.14N#00505.75E2CSN iGate
20260209173829PA0RNH-10>APSN01,TCPIP*,qAC,T2ALBERTA:=5246.15N#00505.74E2CSN iGate