APRS Packet Errors for M0ILY-N (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
20190217145310M0ILY-N>APDG03,TCPIP*,qAC,T2BELGIUM:!0206.05ND53486300.00E&/A=000000440 MMDVM Voice 435.20000MHz +0.0000MHz, M0ILY_Pi-Star
20190217151310M0ILY-N>APDG03,TCPIP*,qAC,T2BELGIUM:!0206.05ND53486300.00E&/A=000000440 MMDVM Voice 435.20000MHz +0.0000MHz, M0ILY_Pi-Star
20190217153310M0ILY-N>APDG03,TCPIP*,qAC,T2BELGIUM:!0206.05ND53486300.00E&/A=000000440 MMDVM Voice 435.20000MHz +0.0000MHz, M0ILY_Pi-Star
20190217155310M0ILY-N>APDG03,TCPIP*,qAC,T2BELGIUM:!0206.05ND53486300.00E&/A=000000440 MMDVM Voice 435.20000MHz +0.0000MHz, M0ILY_Pi-Star
20190217161310M0ILY-N>APDG03,TCPIP*,qAC,T2BELGIUM:!0206.05ND53486300.00E&/A=000000440 MMDVM Voice 435.20000MHz +0.0000MHz, M0ILY_Pi-Star
20190217163320M0ILY-N>APDG03,TCPIP*,qAC,T2BELGIUM:!0206.05ND53486300.00E&/A=000000440 MMDVM Voice 435.20000MHz +0.0000MHz, M0ILY_Pi-Star
20190217165320M0ILY-N>APDG03,TCPIP*,qAC,T2BELGIUM:!0206.05ND53486300.00E&/A=000000440 MMDVM Voice 435.20000MHz +0.0000MHz, M0ILY_Pi-Star
20190217171320M0ILY-N>APDG03,TCPIP*,qAC,T2BELGIUM:!0206.05ND53486300.00E&/A=000000440 MMDVM Voice 435.20000MHz +0.0000MHz, M0ILY_Pi-Star
20190217173320M0ILY-N>APDG03,TCPIP*,qAC,T2BELGIUM:!0206.05ND53486300.00E&/A=000000440 MMDVM Voice 435.20000MHz +0.0000MHz, M0ILY_Pi-Star
20190217175320M0ILY-N>APDG03,TCPIP*,qAC,T2BELGIUM:!0206.05ND53486300.00E&/A=000000440 MMDVM Voice 435.20000MHz +0.0000MHz, M0ILY_Pi-Star
20190217181320M0ILY-N>APDG03,TCPIP*,qAC,T2BELGIUM:!0206.05ND53486300.00E&/A=000000440 MMDVM Voice 435.20000MHz +0.0000MHz, M0ILY_Pi-Star
20190217183320M0ILY-N>APDG03,TCPIP*,qAC,T2BELGIUM:!0206.05ND53486300.00E&/A=000000440 MMDVM Voice 435.20000MHz +0.0000MHz, M0ILY_Pi-Star
20190217185320M0ILY-N>APDG03,TCPIP*,qAC,T2BELGIUM:!0206.05ND53486300.00E&/A=000000440 MMDVM Voice 435.20000MHz +0.0000MHz, M0ILY_Pi-Star
20190217191320M0ILY-N>APDG03,TCPIP*,qAC,T2BELGIUM:!0206.05ND53486300.00E&/A=000000440 MMDVM Voice 435.20000MHz +0.0000MHz, M0ILY_Pi-Star
20190217193330M0ILY-N>APDG03,TCPIP*,qAC,T2BELGIUM:!0206.05ND53486300.00E&/A=000000440 MMDVM Voice 435.20000MHz +0.0000MHz, M0ILY_Pi-Star
20190217195330M0ILY-N>APDG03,TCPIP*,qAC,T2BELGIUM:!0206.05ND53486300.00E&/A=000000440 MMDVM Voice 435.20000MHz +0.0000MHz, M0ILY_Pi-Star
20190217201330M0ILY-N>APDG03,TCPIP*,qAC,T2BELGIUM:!0206.05ND53486300.00E&/A=000000440 MMDVM Voice 435.20000MHz +0.0000MHz, M0ILY_Pi-Star
20190217203330M0ILY-N>APDG03,TCPIP*,qAC,T2BELGIUM:!0206.05ND53486300.00E&/A=000000440 MMDVM Voice 435.20000MHz +0.0000MHz, M0ILY_Pi-Star