APRS Packet Errors for K5KLO-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
20260209110214K5KLO-10>APDW18,TCPIP*,qAC,T2CAEAST:!3350.85NT08417.67W&PHG5120 NE ATL 1-hop TX-iGate
20260209113215K5KLO-10>APDW18,WIDE1-1,WIDE2-1,qAO,KR4CEK-10:!3350.85NT08417.67W&PHG5120 NE ATL 1-hop TX-iGate
20260209120214K5KLO-10>APDW18,TCPIP*,qAC,T2CAEAST:!3350.85NT08417.67W&PHG5120 NE ATL 1-hop TX-iGate
20260209130214K5KLO-10>APDW18,TCPIP*,qAC,T2CAEAST:!3350.85NT08417.67W&PHG5120 NE ATL 1-hop TX-iGate
20260209133215K5KLO-10>APDW18,WIDE1-1,WIDE2-1,qAO,KR4CEK-10:!3350.85NT08417.67W&PHG5120 NE ATL 1-hop TX-iGate
20260209140214K5KLO-10>APDW18,TCPIP*,qAC,T2CAEAST:!3350.85NT08417.67W&PHG5120 NE ATL 1-hop TX-iGate
20260209143215K5KLO-10>APDW18,WIDE1-1,WIDE2-1,qAO,KR4CEK-10:!3350.85NT08417.67W&PHG5120 NE ATL 1-hop TX-iGate
20260209150214K5KLO-10>APDW18,TCPIP*,qAC,T2CAEAST:!3350.85NT08417.67W&PHG5120 NE ATL 1-hop TX-iGate
20260209153215K5KLO-10>APDW18,WIDE1-1,WIDE2-1,qAO,KR4CEK-10:!3350.85NT08417.67W&PHG5120 NE ATL 1-hop TX-iGate
20260209160214K5KLO-10>APDW18,TCPIP*,qAC,T2CAEAST:!3350.85NT08417.67W&PHG5120 NE ATL 1-hop TX-iGate
20260209163215K5KLO-10>APDW18,WIDE1-1,WIDE2-1,qAO,KR4CEK-10:!3350.85NT08417.67W&PHG5120 NE ATL 1-hop TX-iGate