APRS Packet Errors for VE4TOM-3 (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
20170428233842VE4TOM-3>APNU19,qAR,VE4DDW:;145.19-*111111z4911.14N/09756.65T127.3R30K VE4VRG
20170429002849VE4TOM-3>APNU19,qAR,VE4DDW:;145.19-*111111z4911.14N/09756.65T127.3R30K VE4VRG
20170429004532VE4TOM-3>APNU19,qAR,VE4DDW:;145.19-*111111z4911.14N/09756.65T127.3R30K VE4VRG
20170429010217VE4TOM-3>APNU19,qAR,VE4DDW:;145.19-*111111z4911.14N/09756.65T127.3R30K VE4VRG
20170429020907VE4TOM-3>APNU19,qAR,VE4DDW:;145.19-*111111z4911.14N/09756.65T127.3R30K VE4VRG
20170429031600VE4TOM-3>APNU19,qAR,VE4DDW:;145.19-*111111z4911.14N/09756.65T127.3R30K VE4VRG
20170429033242VE4TOM-3>APNU19,qAR,VE4DDW:;145.19-*111111z4911.14N/09756.65T127.3R30K VE4VRG
20170429034925VE4TOM-3>APNU19,qAR,VE4DDW:;145.19-*111111z4911.14N/09756.65T127.3R30K VE4VRG
20170429040607VE4TOM-3>APNU19,qAR,VE4DDW:;145.19-*111111z4911.14N/09756.65T127.3R30K VE4VRG
20170429042251VE4TOM-3>APNU19,qAR,VE4DDW:;145.19-*111111z4911.14N/09756.65T127.3R30K VE4VRG
20170429043935VE4TOM-3>APNU19,qAR,VE4DDW:;145.19-*111111z4911.14N/09756.65T127.3R30K VE4VRG
20170429045617VE4TOM-3>APNU19,qAR,VE4DDW:;145.19-*111111z4911.14N/09756.65T127.3R30K VE4VRG
20170429051259VE4TOM-3>APNU19,qAR,VE4DDW:;145.19-*111111z4911.14N/09756.65T127.3R30K VE4VRG