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
20260208162747F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260208163945F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260208165157F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260208170637F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260208172000F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260208173212F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260208174640F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260208180000F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260208181220F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260208182613F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260208183942F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260208185440F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260208190822F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260208192128F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260208193332F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260208194807F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260208200237F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260208201627F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260208202937F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260208204307F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260208205624F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260208211117F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260208212343F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260208213647F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260208215117F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260208220532F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater
20260208221957F5ZFY-3>APRX29,TCPIP*,qAC,T2SYDNEY:!4912.58NI00158.23E#Vexin / TX-iGate + Digipeater