APRS Packet Errors for KD5QZD-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
20190120180207KD5QZD-1>APBPQ1,qAR,KK5CM-3:;147.03NO*111111z2957.13N/09004.25Wr147.030MHz T114 +060 R30m
20190120183458KD5QZD-1>APBPQ1,qAR,KK5CM-3:;147.03NO*111111z2957.13N/09004.25Wr147.030MHz T114 +060 R30m
20190120190748KD5QZD-1>APBPQ1,qAR,KK5CM-3:;147.03NO*111111z2957.13N/09004.25Wr147.030MHz T114 +060 R30m
20190120194038KD5QZD-1>APBPQ1,qAR,W4NDF:;147.03NO*111111z2957.13N/09004.25Wr147.030MHz T114 +060 R30m
20190120201329KD5QZD-1>APBPQ1,qAR,KK5CM-3:;147.03NO*111111z2957.13N/09004.25Wr147.030MHz T114 +060 R30m
20190120204621KD5QZD-1>APBPQ1,qAR,KK5CM-3:;147.03NO*111111z2957.13N/09004.25Wr147.030MHz T114 +060 R30m
20190120211911KD5QZD-1>APBPQ1,qAR,KK5CM-3:;147.03NO*111111z2957.13N/09004.25Wr147.030MHz T114 +060 R30m
20190120215202KD5QZD-1>APBPQ1,qAR,KK5CM-3:;147.03NO*111111z2957.13N/09004.25Wr147.030MHz T114 +060 R30m
20190120222452KD5QZD-1>APBPQ1,qAR,W4NDF:;147.03NO*111111z2957.13N/09004.25Wr147.030MHz T114 +060 R30m
20190120225742KD5QZD-1>APBPQ1,qAR,KK5CM-3:;147.03NO*111111z2957.13N/09004.25Wr147.030MHz T114 +060 R30m
20190120233033KD5QZD-1>APBPQ1,qAR,W4NDF:;147.03NO*111111z2957.13N/09004.25Wr147.030MHz T114 +060 R30m