APRS Packet Errors for OZ4FTP-13 (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
20251031133207OZ4FTP-13>APVR30,TCPIP*,qAC,T2PANAMA:;IRLP-5116*311332z5638.00NI0958.00E0433500s IDLE
20251031134807OZ4FTP-13>APVR30,TCPIP*,qAC,T2CAEAST:;IRLP-5116*311348z5638.00NI0958.00E0433500s IDLE
20251031140007OZ4FTP-13>APVR30,TCPIP*,qAC,T2SYDNEY:;IRLP-5116*311400z5638.00NI0958.00E0433500s IDLE
20251031141606OZ4FTP-13>APVR30,TCPIP*,qAC,T2PANAMA:;IRLP-5116*311416z5638.00NI0958.00E0433500s IDLE
20251031143207OZ4FTP-13>APVR30,TCPIP*,qAC,T2CHILE:;IRLP-5116*311432z5638.00NI0958.00E0433500s IDLE
20251031144807OZ4FTP-13>APVR30,TCPIP*,qAC,T2CHILE:;IRLP-5116*311448z5638.00NI0958.00E0433500s IDLE
20251031151607OZ4FTP-13>APVR30,TCPIP*,qAC,T2PERTH:;IRLP-5116*311516z5638.00NI0958.00E0433500s IDLE
20251031153207OZ4FTP-13>APVR30,TCPIP*,qAC,T2SYDNEY:;IRLP-5116*311532z5638.00NI0958.00E0433500s IDLE
20251031161606OZ4FTP-13>APVR30,TCPIP*,qAC,T2PANAMA:;IRLP-5116*311616z5638.00NI0958.00E0433500s IDLE
20251031191607OZ4FTP-13>APVR30,TCPIP*,qAC,T2SYDNEY:;IRLP-5116*311916z5638.00NI0958.00E0433500s IDLE