APRS Packet Errors for VA5JC-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
20260208151417	VA5JC-10>APWW11,TCPIP*,qAC,T2BC:@151417h5208.07N/10635.03WlIGATE RCV ONLY
20260208154418	VA5JC-10>APWW11,TCPIP*,qAC,T2BC:@154417h5208.07N/10635.03WlIGATE RCV ONLY
20260208161418	VA5JC-10>APWW11,TCPIP*,qAC,T2BC:@161418h5208.07N/10635.03WlIGATE RCV ONLY
20260208164419	VA5JC-10>APWW11,TCPIP*,qAC,T2BC:@164418h5208.07N/10635.03WlIGATE RCV ONLY
20260208171419	VA5JC-10>APWW11,TCPIP*,qAC,T2BC:@171419h5208.07N/10635.03WlIGATE RCV ONLY
20260208174420	VA5JC-10>APWW11,TCPIP*,qAC,T2BC:@174420h5208.07N/10635.03WlIGATE RCV ONLY
20260208181421	VA5JC-10>APWW11,TCPIP*,qAC,T2BC:@181420h5208.07N/10635.03WlIGATE RCV ONLY
20260208184421	VA5JC-10>APWW11,TCPIP*,qAC,T2BC:@184421h5208.07N/10635.03WlIGATE RCV ONLY
20260208191422	VA5JC-10>APWW11,TCPIP*,qAC,T2BC:@191421h5208.07N/10635.03WlIGATE RCV ONLY
20260208194422	VA5JC-10>APWW11,TCPIP*,qAC,T2BC:@194421h5208.07N/10635.03WlIGATE RCV ONLY
20260208201422	VA5JC-10>APWW11,TCPIP*,qAC,T2BC:@201422h5208.07N/10635.03WlIGATE RCV ONLY
20260208204423	VA5JC-10>APWW11,TCPIP*,qAC,T2BC:@204422h5208.07N/10635.03WlIGATE RCV ONLY