APRS Packet Errors for KD4WLE-7 (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
20260215093125KD4WLE-7>APBPQ1,TCPIP*,qAC,T2DALLAS:;AREDNBPQ*111111z2862.11N/08082.35Wr%156 R15m
20260215100125KD4WLE-7>APBPQ1,TCPIP*,qAC,T2DALLAS:;AREDNBPQ*111111z2862.11N/08082.35Wr%156 R15m
20260215103125KD4WLE-7>APBPQ1,TCPIP*,qAC,T2DALLAS:;AREDNBPQ*111111z2862.11N/08082.35Wr%156 R15m
20260215110125KD4WLE-7>APBPQ1,TCPIP*,qAC,T2DALLAS:;AREDNBPQ*111111z2862.11N/08082.35Wr%156 R15m
20260215113125KD4WLE-7>APBPQ1,TCPIP*,qAC,T2DALLAS:;AREDNBPQ*111111z2862.11N/08082.35Wr%156 R15m
20260215120125KD4WLE-7>APBPQ1,TCPIP*,qAC,T2DALLAS:;AREDNBPQ*111111z2862.11N/08082.35Wr%156 R15m
20260215123125KD4WLE-7>APBPQ1,TCPIP*,qAC,T2DALLAS:;AREDNBPQ*111111z2862.11N/08082.35Wr%156 R15m
20260215130125KD4WLE-7>APBPQ1,TCPIP*,qAC,T2DALLAS:;AREDNBPQ*111111z2862.11N/08082.35Wr%156 R15m
20260215133125KD4WLE-7>APBPQ1,TCPIP*,qAC,T2DALLAS:;AREDNBPQ*111111z2862.11N/08082.35Wr%156 R15m
20260215140125KD4WLE-7>APBPQ1,TCPIP*,qAC,T2DALLAS:;AREDNBPQ*111111z2862.11N/08082.35Wr%156 R15m
20260215143125KD4WLE-7>APBPQ1,TCPIP*,qAC,T2DALLAS:;AREDNBPQ*111111z2862.11N/08082.35Wr%156 R15m
20260215150125KD4WLE-7>APBPQ1,TCPIP*,qAC,T2DALLAS:;AREDNBPQ*111111z2862.11N/08082.35Wr%156 R15m