APRS Packet Errors for F5ZFY-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
20260209090432F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260209091652F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260209092849F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260209094242F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260209095636F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260209100837F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260209102118F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260209103617F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260209105042F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260209110427F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260209111643F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260209112912F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260209114250F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260209115626F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260209121102F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260209122358F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260209123807F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260209125029F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260209130417F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260209131637F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260209132940F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260209134340F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260209135657F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260209141011F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260209142207F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260209143412F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260209144850F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260209150302F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater