APRS Packet Errors for VE2RLU (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
20260209132157	VE2RLU>APWW11,TCPIP*,qAC,T2SPAIN:@132155h4657.61N/07144.65Wr147.285 + TONE 100
20260209135158	VE2RLU>APWW11,TCPIP*,qAC,T2SPAIN:@135156h4657.61N/07144.65Wr147.285 + TONE 100
20260209142159	VE2RLU>APWW11,TCPIP*,qAC,T2SPAIN:@142157h4657.61N/07144.65Wr147.285 + TONE 100
20260209145159	VE2RLU>APWW11,TCPIP*,qAC,T2SPAIN:@145158h4657.61N/07144.65Wr147.285 + TONE 100
20260209152200	VE2RLU>APWW11,TCPIP*,qAC,T2SPAIN:@152158h4657.61N/07144.65Wr147.285 + TONE 100
20260209155200	VE2RLU>APWW11,TCPIP*,qAC,T2SPAIN:@155158h4657.61N/07144.65Wr147.285 + TONE 100
20260209162201	VE2RLU>APWW11,TCPIP*,qAC,T2SPAIN:@162159h4657.61N/07144.65Wr147.285 + TONE 100
20260209165201	VE2RLU>APWW11,TCPIP*,qAC,T2SPAIN:@165159h4657.61N/07144.65Wr147.285 + TONE 100
20260209172202	VE2RLU>APWW11,TCPIP*,qAC,T2SPAIN:@172200h4657.61N/07144.65Wr147.285 + TONE 100
20260209175202	VE2RLU>APWW11,TCPIP*,qAC,T2SPAIN:@175200h4657.61N/07144.65Wr147.285 + TONE 100
20260209182203	VE2RLU>APWW11,TCPIP*,qAC,T2SPAIN:@182201h4657.61N/07144.65Wr147.285 + TONE 100
20260209185203	VE2RLU>APWW11,TCPIP*,qAC,T2SPAIN:@185201h4657.61N/07144.65Wr147.285 + TONE 100