APRS Packet Errors for N7CTM (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
20181119175124N7CTM>APBM1S,TCPIP*,qAS,N2NUO-9:@191751z1000000.00N/1000000.00E-openSPOT 446.2500/446.2500 CC7
20181119181127N7CTM>APBM1S,TCPIP*,qAS,N2NUO-9:@191811z1000000.00N/1000000.00E-openSPOT 446.2500/446.2500 CC7
20181119185135N7CTM>APBM1S,TCPIP*,qAS,N2NUO-9:@191851z1000000.00N/1000000.00E-openSPOT 446.2500/446.2500 CC7
20181119191146N7CTM>APBM1S,TCPIP*,qAS,N2NUO-9:@191911z1000000.00N/1000000.00E-openSPOT 446.2500/446.2500 CC7
20181119195211N7CTM>APBM1S,TCPIP*,qAS,N2NUO-9:@191952z1000000.00N/1000000.00E-openSPOT 446.2500/446.2500 CC7
20181119205149N7CTM>APBM1S,TCPIP*,qAS,N2NUO-9:@192051z1000000.00N/1000000.00E-openSPOT 446.2500/446.2500 CC7
20181119211152N7CTM>APBM1S,TCPIP*,qAS,N2NUO-9:@192111z1000000.00N/1000000.00E-openSPOT 446.2500/446.2500 CC7
20181119215146N7CTM>APBM1S,TCPIP*,qAS,N2NUO-9:@192151z1000000.00N/1000000.00E-openSPOT 446.2500/446.2500 CC7
20181119221143N7CTM>APBM1S,TCPIP*,qAS,N2NUO-9:@192211z1000000.00N/1000000.00E-openSPOT 446.2500/446.2500 CC7
20181119225114N7CTM>APBM1S,TCPIP*,qAS,N2NUO-9:@192251z1000000.00N/1000000.00E-openSPOT 446.2500/446.2500 CC7
20181119231114N7CTM>APBM1S,TCPIP*,qAS,N2NUO-9:@192311z1000000.00N/1000000.00E-openSPOT 446.2500/446.2500 CC7