APRS Packet Errors for BADGER (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
20200920181920BADGER>BEACON,qAR,AE7MK-15:;144.390s*111111z4735.06NS12008.01W WEN BADGER MTN
20200920182919BADGER>BEACON,qAR,AE7MK-15:;144.390s*111111z4735.06NS12008.01W WEN BADGER MTN
20200920183924BADGER>BEACON,qAR,AE7MK-15:;144.390s*111111z4735.06NS12008.01W WEN BADGER MTN
20200920184922BADGER>BEACON,qAR,AE7MK-15:;144.390s*111111z4735.06NS12008.01W WEN BADGER MTN
20200920185919BADGER>BEACON,qAR,AE7MK-15:;144.390s*111111z4735.06NS12008.01W WEN BADGER MTN
20200920191921BADGER>BEACON,qAR,AE7MK-15:;144.390s*111111z4735.06NS12008.01W WEN BADGER MTN
20200920192920BADGER>BEACON,qAO,CRYSTL:;144.390s*111111z4735.06NS12008.01W WEN BADGER MTN
20200920202919BADGER>BEACON,qAO,CRYSTL:;144.390s*111111z4735.06NS12008.01W WEN BADGER MTN
20200920224920BADGER>BEACON,qAR,AE7MK-15:;144.390s*111111z4735.06NS12008.01W WEN BADGER MTN