APRS Packet Errors for VE4DRC (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
20260208131620VE4DRC>APX220,TCPIP*,qAC,SECOND:=4949.50N/09704.21Wx
20260208134621VE4DRC>APX220,TCPIP*,qAC,SECOND:=4949.50N/09704.21Wx
20260208141622VE4DRC>APX220,TCPIP*,qAC,SECOND:=4949.50N/09704.21Wx
20260208144623VE4DRC>APX220,TCPIP*,qAC,SECOND:=4949.50N/09704.21Wx
20260208151624VE4DRC>APX220,TCPIP*,qAC,SECOND:=4949.50N/09704.21Wx
20260208154625VE4DRC>APX220,TCPIP*,qAC,SECOND:=4949.50N/09704.21Wx
20260208161626VE4DRC>APX220,TCPIP*,qAC,SECOND:=4949.50N/09704.21Wx
20260208164627VE4DRC>APX220,TCPIP*,qAC,SECOND:=4949.50N/09704.21Wx
20260208171628VE4DRC>APX220,TCPIP*,qAC,SECOND:=4949.50N/09704.21Wx
20260208174629VE4DRC>APX220,TCPIP*,qAC,SECOND:=4949.50N/09704.21Wx
20260208181630VE4DRC>APX220,TCPIP*,qAC,SECOND:=4949.50N/09704.21Wx
20260208184631VE4DRC>APX220,TCPIP*,qAC,SECOND:=4949.50N/09704.21Wx