APRS Packet Errors for OE5ERN-12 (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
20260209105727	OE5ERN-12>APRSGW,TCPIP*,qAR,OE5ERN-12:!4820.29NG01417.77E#MeshCom GW/B=097/A=000860
20260209112742	OE5ERN-12>APRSGW,TCPIP*,qAR,OE5ERN-12:!4820.29NG01417.77E#MeshCom GW/B=097/A=000860
20260209115757	OE5ERN-12>APRSGW,TCPIP*,qAR,OE5ERN-12:!4820.29NG01417.77E#MeshCom GW/B=097/A=000860
20260209122812	OE5ERN-12>APRSGW,TCPIP*,qAR,OE5ERN-12:!4820.29NG01417.77E#MeshCom GW/B=097/A=000860
20260209125830	OE5ERN-12>APRSGW,TCPIP*,qAR,OE5ERN-12:!4820.29NG01417.77E#MeshCom GW/B=097/A=000860
20260209132845	OE5ERN-12>APRSGW,TCPIP*,qAR,OE5ERN-12:!4820.29NG01417.77E#MeshCom GW/B=097/A=000860
20260209135900	OE5ERN-12>APRSGW,TCPIP*,qAR,OE5ERN-12:!4820.29NG01417.77E#MeshCom GW/B=097/A=000860
20260209142915	OE5ERN-12>APRSGW,TCPIP*,qAR,OE5ERN-12:!4820.29NG01417.77E#MeshCom GW/B=097/A=000860
20260209145931	OE5ERN-12>APRSGW,TCPIP*,qAR,OE5ERN-12:!4820.29NG01417.77E#MeshCom GW/B=097/A=000860
20260209152947	OE5ERN-12>APRSGW,TCPIP*,qAR,OE5ERN-12:!4820.29NG01417.77E#MeshCom GW/B=097/A=000860
20260209160002	OE5ERN-12>APRSGW,TCPIP*,qAR,OE5ERN-12:!4820.29NG01417.77E#MeshCom GW/B=097/A=000860
20260209163017	OE5ERN-12>APRSGW,TCPIP*,qAR,OE5ERN-12:!4820.29NG01417.77E#MeshCom GW/B=097/A=000860