APRS Packet Errors for CT7ABA-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
20260208145350CT7ABA-2>APRSGW,TCPIP*,qAR,CT7ABA-2:!4007.88N/00726.08Wv#CT7ABA-1/B=100/A=001873
20260208152405CT7ABA-2>APRSGW,TCPIP*,qAR,CT7ABA-2:!4007.88N/00726.09Wv#CT7ABA-1/B=100/A=001857
20260208155420CT7ABA-2>APRSGW,TCPIP*,qAR,CT7ABA-2:!4007.88N/00726.09Wv#CT7ABA-1/B=100/A=001877
20260208162438CT7ABA-2>APRSGW,TCPIP*,qAR,CT7ABA-2:!4007.88N/00726.08Wv#CT7ABA-1/B=100/A=001854
20260208165453CT7ABA-2>APRSGW,TCPIP*,qAR,CT7ABA-2:!4007.88N/00726.08Wv#CT7ABA-1/B=100/A=001877
20260208172508CT7ABA-2>APRSGW,TCPIP*,qAR,CT7ABA-2:!4007.88N/00726.08Wv#CT7ABA-1/B=100/A=001870
20260208175524CT7ABA-2>APRSGW,TCPIP*,qAR,CT7ABA-2:!4007.88N/00726.08Wv#CT7ABA-1/B=100/A=001877
20260208182543CT7ABA-2>APRSGW,TCPIP*,qAR,CT7ABA-2:!4007.88N/00726.08Wv#CT7ABA-1/B=100/A=001867
20260208185558CT7ABA-2>APRSGW,TCPIP*,qAR,CT7ABA-2:!4007.88N/00726.08Wv#CT7ABA-1/B=100/A=001877
20260208192613CT7ABA-2>APRSGW,TCPIP*,qAR,CT7ABA-2:!4007.88N/00726.08Wv#CT7ABA-1/B=100/A=001906
20260208195633CT7ABA-2>APRSGW,TCPIP*,qAR,CT7ABA-2:!4007.88N/00726.08Wv#CT7ABA-1/B=100/A=001867
20260208202648CT7ABA-2>APRSGW,TCPIP*,qAR,CT7ABA-2:!4007.88N/00726.08Wv#CT7ABA-1/B=100/A=001864