APRS Packet Errors for LU2WBA-4 (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
20190219092354LU2WBA-4>APBPQ1,TCPIP*,qAC,CX2SA-S1:;444.80BPQ*111111z4552.50S/006731.63Wr%156 R15m
20190219095743LU2WBA-4>APBPQ1,TCPIP*,qAC,CX2SA-S1:;444.80BPQ*111111z4552.50S/006731.63Wr%156 R15m
20190219103131LU2WBA-4>APBPQ1,TCPIP*,qAC,CX2SA-S1:;444.80BPQ*111111z4552.50S/006731.63Wr%156 R15m
20190219110517LU2WBA-4>APBPQ1,TCPIP*,qAC,CX2SA-S1:;444.80BPQ*111111z4552.50S/006731.63Wr%156 R15m
20190219113908LU2WBA-4>APBPQ1,TCPIP*,qAC,CX2SA-S1:;444.80BPQ*111111z4552.50S/006731.63Wr%156 R15m
20190219121257LU2WBA-4>APBPQ1,TCPIP*,qAC,CX2SA-S1:;444.80BPQ*111111z4552.50S/006731.63Wr%156 R15m
20190219124635LU2WBA-4>APBPQ1,TCPIP*,qAC,CX2SA-S1:;444.80BPQ*111111z4552.50S/006731.63Wr%156 R15m
20190219132029LU2WBA-4>APBPQ1,TCPIP*,qAC,CX2SA-S1:;444.80BPQ*111111z4552.50S/006731.63Wr%156 R15m
20190219135418LU2WBA-4>APBPQ1,TCPIP*,qAC,CX2SA-S1:;444.80BPQ*111111z4552.50S/006731.63Wr%156 R15m
20190219142808LU2WBA-4>APBPQ1,TCPIP*,qAC,CX2SA-S1:;444.80BPQ*111111z4552.50S/006731.63Wr%156 R15m
20190219150157LU2WBA-4>APBPQ1,TCPIP*,qAC,CX2SA-S1:;444.80BPQ*111111z4552.50S/006731.63Wr%156 R15m