APRS Packet Errors for N3COW (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
20190216073842N3COW>APBM1S,TCPIP*,qAS,N3FE-15:@160738z412253.41N/794159.77E-MMDVM ZUMspot 433.5000/433.5000 CC1
20190216080903N3COW>APBM1S,TCPIP*,qAS,N3FE-15:@160809z412253.41N/794159.77E-MMDVM ZUMspot 433.5000/433.5000 CC1
20190216084032N3COW>APBM1S,TCPIP*,qAS,N3FE-15:@160840z412253.41N/794159.77E-MMDVM ZUMspot 433.5000/433.5000 CC1
20190216090632N3COW>APBM1S,TCPIP*,qAS,N3FE-15:@160906z412253.41N/794159.77E-MMDVM ZUMspot 433.5000/433.5000 CC1
20190216093834N3COW>APBM1S,TCPIP*,qAS,N3FE-15:@160938z412253.41N/794159.77E-MMDVM ZUMspot 433.5000/433.5000 CC1
20190216111607N3COW>APBM1S,TCPIP*,qAS,N3FE-15:@161116z412253.41N/794159.77E-MMDVM ZUMspot 433.5000/433.5000 CC1
20190216114629N3COW>APBM1S,TCPIP*,qAS,N3FE-15:@161146z412253.41N/794159.77E-MMDVM ZUMspot 433.5000/433.5000 CC1
20190216121757N3COW>APBM1S,TCPIP*,qAS,N3FE-15:@161217z412253.41N/794159.77E-MMDVM ZUMspot 433.5000/433.5000 CC1
20190216124821N3COW>APBM1S,TCPIP*,qAS,N3FE-15:@161248z412253.41N/794159.77E-MMDVM ZUMspot 433.5000/433.5000 CC1
20190216131850N3COW>APBM1S,TCPIP*,qAS,N3FE-15:@161318z412253.41N/794159.77E-MMDVM ZUMspot 433.5000/433.5000 CC1