APRS Packet Errors for W9RCG-2 (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
20260208133210W9RCG-2>APDW17,TCPIP*,qAC,SECOND:!4307.10N/08807.17W#PHG5560
20260208140210W9RCG-2>APDW17,TCPIP*,qAC,SECOND:!4307.10N/08807.17W#PHG5560
20260208140242W9RCG-2>APDW17,N9LKH-1,WIDE1,KD9UWG-1,WIDE2*,qAR,W9CQO-1:!4307.10N/08807.17W#PHG5560
20260208143211W9RCG-2>APDW17,TCPIP*,qAC,SECOND:!4307.10N/08807.17W#PHG5560
20260208150211W9RCG-2>APDW17,TCPIP*,qAC,SECOND:!4307.10N/08807.17W#PHG5560
20260208150312W9RCG-2>APDW17,N9LKH-1,WIDE1*,WIDE2-1,qAR,W9CQO-1:!4307.10N/08807.17W#PHG5560
20260208153211W9RCG-2>APDW17,TCPIP*,qAC,SECOND:!4307.10N/08807.17W#PHG5560
20260208160211W9RCG-2>APDW17,TCPIP*,qAC,SECOND:!4307.10N/08807.17W#PHG5560
20260208163210W9RCG-2>APDW17,TCPIP*,qAC,SECOND:!4307.10N/08807.17W#PHG5560
20260208170209W9RCG-2>APDW17,TCPIP*,qAC,SECOND:!4307.10N/08807.17W#PHG5560
20260208173209W9RCG-2>APDW17,TCPIP*,qAC,SECOND:!4307.10N/08807.17W#PHG5560
20260208180209W9RCG-2>APDW17,TCPIP*,qAC,SECOND:!4307.10N/08807.17W#PHG5560
20260208180242W9RCG-2>APDW17,KD9UWG-1,WIDE1*,WIDE2-1,qAR,W9CQO-1:!4307.10N/08807.17W#PHG5560
20260208183209W9RCG-2>APDW17,TCPIP*,qAC,SECOND:!4307.10N/08807.17W#PHG5560
20260208190209W9RCG-2>APDW17,TCPIP*,qAC,SECOND:!4307.10N/08807.17W#PHG5560