APRS Packet Errors for DRAKE (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
20261101180154DRAKE>BEACON,qAR,W7VW-10:;144.390DP*111111z4218.18/12009.26Wr144.390MHz Drake Peak
20261101181154DRAKE>BEACON,qAR,W7VW-10:;144.390DP*111111z4218.18/12009.26Wr144.390MHz Drake Peak
20261101181654DRAKE>BEACON,qAR,W7VW-10:;144.390DP*111111z4218.18/12009.26Wr144.390MHz Drake Peak
20261101182654DRAKE>BEACON,qAR,W7VW-10:;144.390DP*111111z4218.18/12009.26Wr144.390MHz Drake Peak
20261101190154DRAKE>BEACON,qAR,W7VW-10:;144.390DP*111111z4218.18/12009.26Wr144.390MHz Drake Peak
20261101191654DRAKE>BEACON,qAR,W7VW-10:;144.390DP*111111z4218.18/12009.26Wr144.390MHz Drake Peak
20261101192154DRAKE>BEACON,qAR,W7VW-10:;144.390DP*111111z4218.18/12009.26Wr144.390MHz Drake Peak
20261101193654DRAKE>BEACON,qAR,W7VW-10:;144.390DP*111111z4218.18/12009.26Wr144.390MHz Drake Peak
20261101202655DRAKE>BEACON,qAR,W7VW-10:;144.390DP*111111z4218.18/12009.26Wr144.390MHz Drake Peak
20261101203654DRAKE>BEACON,qAR,W7VW-10:;144.390DP*111111z4218.18/12009.26Wr144.390MHz Drake Peak
20261101210154DRAKE>BEACON,qAR,W7VW-10:;144.390DP*111111z4218.18/12009.26Wr144.390MHz Drake Peak
20261101214154DRAKE>BEACON,qAR,W7VW-10:;144.390DP*111111z4218.18/12009.26Wr144.390MHz Drake Peak
20261101224154DRAKE>BEACON,qAR,W7VW-10:;144.390DP*111111z4218.18/12009.26Wr144.390MHz Drake Peak