APRS Packet Errors for W4TIY-4 (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
20201201153010W4TIY-4>BEACON,qAO,WX4BK-13:;146.895+*111111z3350.70N/8457.42WrT077 R45m Mg2ndTh
20201201160020W4TIY-4>BEACON,qAO,WX4BK-13:;146.895+*111111z3350.70N/8457.42WrT077 R45m Mg2ndTh
20201201163004W4TIY-4>BEACON,qAO,WX4BK-13:;146.895+*111111z3350.70N/8457.42WrT077 R45m Mg2ndTh
20201201170015W4TIY-4>BEACON,qAR,N4NE-2:;146.895+*111111z3350.70N/8457.42WrT077 R45m Mg2ndTh
20201201173005W4TIY-4>BEACON,qAR,N4NE-2:;146.895+*111111z3350.70N/8457.42WrT077 R45m Mg2ndTh
20201201180010W4TIY-4>BEACON,qAO,WX4BK-13:;146.895+*111111z3350.70N/8457.42WrT077 R45m Mg2ndTh
20201201183006W4TIY-4>BEACON,qAO,WX4BK-13:;146.895+*111111z3350.70N/8457.42WrT077 R45m Mg2ndTh
20201201190009W4TIY-4>BEACON,qAR,KB4RCO-10:;146.895+*111111z3350.70N/8457.42WrT077 R45m Mg2ndTh
20201201193001W4TIY-4>BEACON,qAO,WX4BK-13:;146.895+*111111z3350.70N/8457.42WrT077 R45m Mg2ndTh
20201201200018W4TIY-4>BEACON,qAO,WX4BK-13:;146.895+*111111z3350.70N/8457.42WrT077 R45m Mg2ndTh
20201201203001W4TIY-4>BEACON,qAO,WX4BK-13:;146.895+*111111z3350.70N/8457.42WrT077 R45m Mg2ndTh
20201201210011W4TIY-4>BEACON,qAO,WX4BK-13:;146.895+*111111z3350.70N/8457.42WrT077 R45m Mg2ndTh