APRS Packet Errors for N6ROR-10 (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
20200217090904N6ROR-10>APN383,qAR,KD6DCN-5:!3304.98ns11636.31w
20200217093904N6ROR-10>APN383,qAR,KD6DCN-5:!3304.98ns11636.31w
20200217100904N6ROR-10>APN383,qAR,KD6DCN-5:!3304.98ns11636.31w
20200217103904N6ROR-10>APN383,qAR,KD6DCN-5:!3304.98ns11636.31w
20200217113904N6ROR-10>APN383,qAR,KD6DCN-5:!3304.98ns11636.31w
20200217120904N6ROR-10>APN383,qAR,KD6DCN-5:!3304.98ns11636.31w
20200217130904N6ROR-10>APN383,qAR,KD6DCN-5:!3304.98ns11636.31w
20200217133904N6ROR-10>APN383,qAR,KD6DCN-5:!3304.98ns11636.31w
20200217140904N6ROR-10>APN383,qAR,KD6DCN-5:!3304.98ns11636.31w