APRS Packet Errors for W9PVR-12 (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
20180618055335W9PVR-12>BEACON,qAR,W0NE-1:;146.910xy*111111z4318.90N/09024.6.58WrT131 R35m Net Su9PM
20180618093334W9PVR-12>BEACON,qAR,W0NE-1:;146.910xy*111111z4318.90N/09024.6.58WrT131 R35m Net Su9PM
20180618095334W9PVR-12>BEACON,qAR,W0NE-1:;146.910xy*111111z4318.90N/09024.6.58WrT131 R35m Net Su9PM
20180618103334W9PVR-12>BEACON,qAR,W0NE-1:;146.910xy*111111z4318.90N/09024.6.58WrT131 R35m Net Su9PM
20180618105334W9PVR-12>BEACON,qAR,W0NE-1:;146.910xy*111111z4318.90N/09024.6.58WrT131 R35m Net Su9PM
20180618121334W9PVR-12>BEACON,qAR,W0NE-1:;146.910xy*111111z4318.90N/09024.6.58WrT131 R35m Net Su9PM
20180618131334W9PVR-12>BEACON,qAR,W0NE-1:;146.910xy*111111z4318.90N/09024.6.58WrT131 R35m Net Su9PM
20180618133334W9PVR-12>BEACON,qAR,W0NE-1:;146.910xy*111111z4318.90N/09024.6.58WrT131 R35m Net Su9PM
20180618141334W9PVR-12>BEACON,qAR,W0NE-1:;146.910xy*111111z4318.90N/09024.6.58WrT131 R35m Net Su9PM
20180618143334W9PVR-12>BEACON,qAR,W0NE-1:;146.910xy*111111z4318.90N/09024.6.58WrT131 R35m Net Su9PM
20180618145335W9PVR-12>BEACON,qAR,W0NE-1:;146.910xy*111111z4318.90N/09024.6.58WrT131 R35m Net Su9PM
20180618151334W9PVR-12>BEACON,qAR,W0NE-1:;146.910xy*111111z4318.90N/09024.6.58WrT131 R35m Net Su9PM