APRS Packet Errors for N0JBE-2 (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
20260208150021N0JBE-2>APDR17,TCPIP*,qAC,T2SYDNEY:=4307.54N/09312.14Wo Fill in digi/igate
20260208153521N0JBE-2>APDR17,TCPIP*,qAC,T2SYDNEY:=4307.54N/09312.14Wo Fill in digi/igate
20260208160347N0JBE-2>APDR17,TCPIP*,qAC,T2SYDNEY:=4307.54N/09312.14Wo Fill in digi/igate
20260208162456N0JBE-2>APDR17,TCPIP*,qAC,T2SYDNEY:=4307.54N/09312.14Wo Fill in digi/igate
20260208165222N0JBE-2>APDR17,TCPIP*,qAC,T2SYDNEY:=4307.54N/09312.14Wo Fill in digi/igate
20260208171935N0JBE-2>APDR17,TCPIP*,qAC,T2SYDNEY:=4307.54N/09312.14Wo Fill in digi/igate
20260208182334N0JBE-2>APDR17,TCPIP*,qAC,T2SYDNEY:=4307.54N/09312.14Wo Fill in digi/igate
20260208202405N0JBE-2>APDR17,TCPIP*,qAC,T2SYDNEY:=4307.54N/09312.14Wo Fill in digi/igate
20260208204747N0JBE-2>APDR17,TCPIP*,qAC,T2SYDNEY:=4307.54N/09312.14Wo Fill in digi/igate