APRS Packet Errors for SR2INO (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
20260209144410SR2INO>APRX29,TCPIP*,qAC,T2PERTH:!5247.60NI01814.98E#Digi & Igate 2m
20260209151408SR2INO>APRX29,TCPIP*,qAC,T2PERTH:!5247.60NI01814.98E#Digi & Igate 2m
20260209154323SR2INO>APRX29,TCPIP*,qAC,T2PERTH:!5247.60NI01814.98E#Digi & Igate 2m
20260209160823SR2INO>APRX29,TCPIP*,qAC,T2PERTH:!5247.60NI01814.98E#Digi & Igate 2m
20260209163412SR2INO>APRX29,TCPIP*,qAC,T2PERTH:!5247.60NI01814.98E#Digi & Igate 2m
20260209170308SR2INO>APRX29,TCPIP*,qAC,T2PERTH:!5247.60NI01814.98E#Digi & Igate 2m
20260209173108SR2INO>APRX29,TCPIP*,qAC,T2PERTH:!5247.60NI01814.98E#Digi & Igate 2m
20260209180028SR2INO>APRX29,TCPIP*,qAC,T2PERTH:!5247.60NI01814.98E#Digi & Igate 2m
20260209182828SR2INO>APRX29,TCPIP*,qAC,T2PERTH:!5247.60NI01814.98E#Digi & Igate 2m
20260209185648SR2INO>APRX29,TCPIP*,qAC,T2PERTH:!5247.60NI01814.98E#Digi & Igate 2m
20260209192634SR2INO>APRX29,TCPIP*,qAC,T2PERTH:!5247.60NI01814.98E#Digi & Igate 2m
20260209195053SR2INO>APRX29,TCPIP*,qAC,T2PERTH:!5247.60NI01814.98E#Digi & Igate 2m
20260209201603SR2INO>APRX29,TCPIP*,qAC,T2PERTH:!5247.60NI01814.98E#Digi & Igate 2m