APRS Packet Errors for VE2ONR-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
20260208163035	VE2ONR-10>APWW11,TCPIP*,qAC,T2CHILE:@163034h4552.28N/07404.78WlPHG5240 73 de Fred!
20260208170035	VE2ONR-10>APWW11,TCPIP*,qAC,T2CHILE:@170034h4552.28N/07404.78WlPHG5240 73 de Fred!
20260208173035	VE2ONR-10>APWW11,TCPIP*,qAC,T2CHILE:@173034h4552.28N/07404.78WlPHG5240 73 de Fred!
20260208180035	VE2ONR-10>APWW11,TCPIP*,qAC,T2CHILE:@180034h4552.28N/07404.78WlPHG5240 73 de Fred!
20260208183035	VE2ONR-10>APWW11,TCPIP*,qAC,T2CHILE:@183034h4552.28N/07404.78WlPHG5240 73 de Fred!
20260208190035	VE2ONR-10>APWW11,TCPIP*,qAC,T2CHILE:@190034h4552.28N/07404.78WlPHG5240 73 de Fred!
20260208193035	VE2ONR-10>APWW11,TCPIP*,qAC,T2CHILE:@193033h4552.28N/07404.78WlPHG5240 73 de Fred!
20260208200035	VE2ONR-10>APWW11,TCPIP*,qAC,T2CHILE:@200033h4552.28N/07404.78WlPHG5240 73 de Fred!
20260208203035	VE2ONR-10>APWW11,TCPIP*,qAC,T2CHILE:@203033h4552.28N/07404.78WlPHG5240 73 de Fred!
20260208210035	VE2ONR-10>APWW11,TCPIP*,qAC,T2CHILE:@210033h4552.28N/07404.78WlPHG5240 73 de Fred!
20260208213034	VE2ONR-10>APWW11,TCPIP*,qAC,T2CHILE:@213033h4552.28N/07404.78WlPHG5240 73 de Fred!
20260208220034	VE2ONR-10>APWW11,TCPIP*,qAC,T2CHILE:@220033h4552.28N/07404.78WlPHG5240 73 de Fred!