APRS Packet Errors for EA2BKH-1 (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
20190717130824EA2BKH-1>APBPQ1,TCPIP*,qAC,T2FFL:;144.800BPQ*111111z4141.15N/00052.30Wr%156 R15m
20190717134113EA2BKH-1>APBPQ1,TCPIP*,qAC,T2FFL:;144.800BPQ*111111z4141.15N/00052.30Wr%156 R15m
20190717141402EA2BKH-1>APBPQ1,TCPIP*,qAC,T2FFL:;144.800BPQ*111111z4141.15N/00052.30Wr%156 R15m
20190717144651EA2BKH-1>APBPQ1,TCPIP*,qAC,T2FFL:;144.800BPQ*111111z4141.15N/00052.30Wr%156 R15m
20190717151940EA2BKH-1>APBPQ1,TCPIP*,qAC,T2FFL:;144.800BPQ*111111z4141.15N/00052.30Wr%156 R15m
20190717155229EA2BKH-1>APBPQ1,TCPIP*,qAC,T2FFL:;144.800BPQ*111111z4141.15N/00052.30Wr%156 R15m
20190717162518EA2BKH-1>APBPQ1,TCPIP*,qAC,T2FFL:;144.800BPQ*111111z4141.15N/00052.30Wr%156 R15m
20190717165807EA2BKH-1>APBPQ1,TCPIP*,qAC,T2FFL:;144.800BPQ*111111z4141.15N/00052.30Wr%156 R15m
20190717173056EA2BKH-1>APBPQ1,TCPIP*,qAC,T2FFL:;144.800BPQ*111111z4141.15N/00052.30Wr%156 R15m
20190717180345EA2BKH-1>APBPQ1,TCPIP*,qAC,T2FFL:;144.800BPQ*111111z4141.15N/00052.30Wr%156 R15m
20190717183634EA2BKH-1>APBPQ1,TCPIP*,qAC,T2FFL:;144.800BPQ*111111z4141.15N/00052.30Wr%156 R15m