APRS Packet Errors for G1GXB-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
20170720170000G1GXB-4>FBB,qAR,G1GXB-1:!5095.50N/0012.03W Bishops Waltham SOTON5 Node
20170720175511G1GXB-4>FBB,qAR,G1GXB-1:!5095.50N/0012.03W Bishops Waltham SOTON5 Node
20170720185011G1GXB-4>FBB,qAR,G1GXB-1:!5095.50N/0012.03W Bishops Waltham SOTON5 Node
20170720194521G1GXB-4>FBB,qAR,G1GXB-1:!5095.50N/0012.03W Bishops Waltham SOTON5 Node
20170720204021G1GXB-4>FBB,qAR,G1GXB-1:!5095.50N/0012.03W Bishops Waltham SOTON5 Node
20170720213522G1GXB-4>FBB,qAR,G1GXB-1:!5095.50N/0012.03W Bishops Waltham SOTON5 Node
20170720223032G1GXB-4>FBB,qAR,G1GXB-1:!5095.50N/0012.03W Bishops Waltham SOTON5 Node