APRS Packet Errors for VE2ONR-1 (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
20260209161357	VE2ONR-1>APWW11,TCPIP*,qAC,T2CSNGRAD:@161356h4552.28N/07404.78W#PHG5240 73 de Fred!
20260209164358	VE2ONR-1>APWW11,TCPIP*,qAC,T2CSNGRAD:@164357h4552.28N/07404.78W#PHG5240 73 de Fred!
20260209171359	VE2ONR-1>APWW11,TCPIP*,qAC,T2CSNGRAD:@171358h4552.28N/07404.78W#PHG5240 73 de Fred!
20260209174359	VE2ONR-1>APWW11,TCPIP*,qAC,T2CSNGRAD:@174358h4552.28N/07404.78W#PHG5240 73 de Fred!
20260209181400	VE2ONR-1>APWW11,TCPIP*,qAC,T2CSNGRAD:@181358h4552.28N/07404.78W#PHG5240 73 de Fred!
20260209184400	VE2ONR-1>APWW11,TCPIP*,qAC,T2CSNGRAD:@184359h4552.28N/07404.78W#PHG5240 73 de Fred!
20260209191401	VE2ONR-1>APWW11,TCPIP*,qAC,T2CSNGRAD:@191359h4552.28N/07404.78W#PHG5240 73 de Fred!
20260209194401	VE2ONR-1>APWW11,TCPIP*,qAC,T2CSNGRAD:@194400h4552.28N/07404.78W#PHG5240 73 de Fred!
20260209201401	VE2ONR-1>APWW11,TCPIP*,qAC,T2CSNGRAD:@201400h4552.28N/07404.78W#PHG5240 73 de Fred!
20260209204402	VE2ONR-1>APWW11,TCPIP*,qAC,T2CSNGRAD:@204400h4552.28N/07404.78W#PHG5240 73 de Fred!
20260209211403	VE2ONR-1>APWW11,TCPIP*,qAC,T2CSNGRAD:@211401h4552.28N/07404.78W#PHG5240 73 de Fred!
20260209214403	VE2ONR-1>APWW11,TCPIP*,qAC,T2CSNGRAD:@214402h4552.28N/07404.78W#PHG5240 73 de Fred!