APRS Packet Errors for OH1CO-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
20260208133744	OH1CO-3>APWW11,TCPIP*,qAC,T2PERTH:@133744h6026.82N/02221.91ElAPRS-IS for Win32
20260208140745	OH1CO-3>APWW11,TCPIP*,qAC,T2PERTH:@140744h6026.82N/02221.91ElAPRS-IS for Win32
20260208143745	OH1CO-3>APWW11,TCPIP*,qAC,T2PERTH:@143744h6026.82N/02221.91ElAPRS-IS for Win32
20260208150745	OH1CO-3>APWW11,TCPIP*,qAC,T2PERTH:@150744h6026.82N/02221.91ElAPRS-IS for Win32
20260208153745	OH1CO-3>APWW11,TCPIP*,qAC,T2PERTH:@153744h6026.82N/02221.91ElAPRS-IS for Win32
20260208160745	OH1CO-3>APWW11,TCPIP*,qAC,T2PERTH:@160744h6026.82N/02221.91ElAPRS-IS for Win32
20260208163745	OH1CO-3>APWW11,TCPIP*,qAC,T2PERTH:@163745h6026.82N/02221.91ElAPRS-IS for Win32
20260208170745	OH1CO-3>APWW11,TCPIP*,qAC,T2PERTH:@170745h6026.82N/02221.91ElAPRS-IS for Win32
20260208173746	OH1CO-3>APWW11,TCPIP*,qAC,T2PERTH:@173746h6026.82N/02221.91ElAPRS-IS for Win32
20260208180746	OH1CO-3>APWW11,TCPIP*,qAC,T2PERTH:@180746h6026.82N/02221.91ElAPRS-IS for Win32
20260208183746	OH1CO-3>APWW11,TCPIP*,qAC,T2PERTH:@183746h6026.82N/02221.91ElAPRS-IS for Win32
20260208190746	OH1CO-3>APWW11,TCPIP*,qAC,T2PERTH:@190746h6026.82N/02221.91ElAPRS-IS for Win32