APRS Packet Errors for IR3CA-2 (last 24 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
20180816183331IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180816211205IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180816221701IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180817010230IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122d@
20180817023708IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180817041231IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180817041710IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180817053222IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180817055214IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180817060714IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180817073222IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180817110053IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180817123111IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180817131607IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180817142105IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180817145603IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180817155059IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180817161606IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180817171103IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180817172602IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122