APRS Packet Errors for NC8OS (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
20180820111056NC8OS>APBM1S,TCPIP*,qAS,N3FE-15:@201110z413755.20N/821246.17W-PHG0600openSPOT 441.4450/441.4450 CC1
20180820114029NC8OS>APBM1S,TCPIP*,qAS,N3FE-15:@201140z413755.20N/821246.17W-PHG0600openSPOT 441.4450/441.4450 CC1
20180820121031NC8OS>APBM1S,TCPIP*,qAS,N3FE-15:@201210z413755.20N/821246.17W-PHG0600openSPOT 441.4450/441.4450 CC1
20180820124046NC8OS>APBM1S,TCPIP*,qAS,N3FE-15:@201240z413755.20N/821246.17W-PHG0600openSPOT 441.4450/441.4450 CC1
20180820131126NC8OS>APBM1S,TCPIP*,qAS,N3FE-15:@201311z413755.20N/821246.17W-PHG0600openSPOT 441.4450/441.4450 CC1
20180820134042NC8OS>APBM1S,TCPIP*,qAS,N3FE-15:@201340z413755.20N/821246.17W-PHG0600openSPOT 441.4450/441.4450 CC1
20180820144103NC8OS>APBM1S,TCPIP*,qAS,N3FE-15:@201441z413755.20N/821246.17W-PHG0600openSPOT 441.4450/441.4450 CC1
20180820151038NC8OS>APBM1S,TCPIP*,qAS,N3FE-15:@201510z413755.20N/821246.17W-PHG0600openSPOT 441.4450/441.4450 CC1
20180820154059NC8OS>APBM1S,TCPIP*,qAS,N3FE-15:@201540z413755.20N/821246.17W-PHG0600openSPOT 441.4450/441.4450 CC1
20180820161050NC8OS>APBM1S,TCPIP*,qAS,N3FE-15:@201610z413755.20N/821246.17W-PHG0600openSPOT 441.4450/441.4450 CC1
20180820164050NC8OS>APBM1S,TCPIP*,qAS,N3FE-15:@201640z413755.20N/821246.17W-PHG0600openSPOT 441.4450/441.4450 CC1