APRS Packet Errors for G0RAS-5 (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
20260208150207G0RAS-5>APWW10,TCPIP*,qAC,T2SYDNEY:@150206h5145.52N/00102.20W-Home
20260208153206G0RAS-5>APWW10,TCPIP*,qAC,T2SYDNEY:@153205h5145.52N/00102.20W-Home
20260208160205G0RAS-5>APWW10,TCPIP*,qAC,T2SYDNEY:@160204h5145.52N/00102.20W-Home
20260208163204G0RAS-5>APWW10,TCPIP*,qAC,T2SYDNEY:@163203h5145.52N/00102.20W-Home
20260208170203G0RAS-5>APWW10,TCPIP*,qAC,T2SYDNEY:@170202h5145.52N/00102.20W-Home
20260208173202G0RAS-5>APWW10,TCPIP*,qAC,T2SYDNEY:@173200h5145.52N/00102.20W-Home
20260208180201G0RAS-5>APWW10,TCPIP*,qAC,T2SYDNEY:@180159h5145.52N/00102.20W-Home
20260208183200G0RAS-5>APWW10,TCPIP*,qAC,T2SYDNEY:@183158h5145.52N/00102.20W-Home
20260208190158G0RAS-5>APWW10,TCPIP*,qAC,T2SYDNEY:@190157h5145.52N/00102.20W-Home
20260208193157G0RAS-5>APWW10,TCPIP*,qAC,T2SYDNEY:@193156h5145.52N/00102.20W-Home
20260208200156G0RAS-5>APWW10,TCPIP*,qAC,T2SYDNEY:@200155h5145.52N/00102.20W-Home
20260208203155G0RAS-5>APWW10,TCPIP*,qAC,T2SYDNEY:@203153h5145.52N/00102.20W-Home