APRS Packet Errors for M0VFC (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
20260208125707M0VFC>APLRG1,TCPIP*,qAC,T2FRANCE:!L4&kfNPhya GCottenham iGate
20260208132707M0VFC>APLRG1,TCPIP*,qAC,T2FRANCE:!L4&kfNPhya GCottenham iGate
20260208132738M0VFC>APLRG1,G8MLA-10*,qAR,M7VJL-10:!L4&kfNPhya GCottenham iGate
20260208135707M0VFC>APLRG1,TCPIP*,qAC,T2FRANCE:!L4&kfNPhya GCottenham iGate
20260208142707M0VFC>APLRG1,TCPIP*,qAC,T2FRANCE:!L4&kfNPhya GCottenham iGate
20260208145707M0VFC>APLRG1,TCPIP*,qAC,T2FRANCE:!L4&kfNPhya GCottenham iGate
20260208152707M0VFC>APLRG1,TCPIP*,qAC,T2FRANCE:!L4&kfNPhya GCottenham iGate
20260208155707M0VFC>APLRG1,TCPIP*,qAC,T2FRANCE:!L4&kfNPhya GCottenham iGate
20260208162707M0VFC>APLRG1,TCPIP*,qAC,T2FRANCE:!L4&kfNPhya GCottenham iGate
20260208165707M0VFC>APLRG1,TCPIP*,qAC,T2FRANCE:!L4&kfNPhya GCottenham iGate
20260208172707M0VFC>APLRG1,TCPIP*,qAC,T2FRANCE:!L4&kfNPhya GCottenham iGate
20260208175708M0VFC>APLRG1,TCPIP*,qAC,T2FRANCE:!L4&kfNPhya GCottenham iGate
20260208182708M0VFC>APLRG1,TCPIP*,qAC,T2FRANCE:!L4&kfNPhya GCottenham iGate