APRS Packet Errors for EA2BKH-6 (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
20251205201717EA2BKH-6>APBPQ1,TCPIP*,qAC,T2UK:;144.800BPQ*111111z4141.15N/00052.30Wr%156 R15m
20251205204717EA2BKH-6>APBPQ1,TCPIP*,qAC,T2UK:;144.800BPQ*111111z4141.15N/00052.30Wr%156 R15m
20251205211717EA2BKH-6>APBPQ1,TCPIP*,qAC,T2UK:;144.800BPQ*111111z4141.15N/00052.30Wr%156 R15m
20251205214717EA2BKH-6>APBPQ1,TCPIP*,qAC,T2UK:;144.800BPQ*111111z4141.15N/00052.30Wr%156 R15m
20251205221717EA2BKH-6>APBPQ1,TCPIP*,qAC,T2UK:;144.800BPQ*111111z4141.15N/00052.30Wr%156 R15m
20251205224717EA2BKH-6>APBPQ1,TCPIP*,qAC,T2UK:;144.800BPQ*111111z4141.15N/00052.30Wr%156 R15m
20251205231717EA2BKH-6>APBPQ1,TCPIP*,qAC,T2UK:;144.800BPQ*111111z4141.15N/00052.30Wr%156 R15m
20251205234717EA2BKH-6>APBPQ1,TCPIP*,qAC,T2UK:;144.800BPQ*111111z4141.15N/00052.30Wr%156 R15m
20251206001717EA2BKH-6>APBPQ1,TCPIP*,qAC,T2UK:;144.800BPQ*111111z4141.15N/00052.30Wr%156 R15m
20251206004717EA2BKH-6>APBPQ1,TCPIP*,qAC,T2UK:;144.800BPQ*111111z4141.15N/00052.30Wr%156 R15m
20251206011717EA2BKH-6>APBPQ1,TCPIP*,qAC,T2UK:;144.800BPQ*111111z4141.15N/00052.30Wr%156 R15m
20251206014717EA2BKH-6>APBPQ1,TCPIP*,qAC,T2UK:;144.800BPQ*111111z4141.15N/00052.30Wr%156 R15m