APRS Packet Errors for OE3CIN-4 (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
20260208131739	OE3CIN-4>APRSGW,TCPIP*,qAR,OE3CIN-4:!4835.71N/01627.90E#MeshCom 4.0/B=075/A=000755
20260208134759	OE3CIN-4>APRSGW,TCPIP*,qAR,OE3CIN-4:!4835.71N/01627.90E#MeshCom 4.0/B=074/A=000755
20260208141820	OE3CIN-4>APRSGW,TCPIP*,qAR,OE3CIN-4:!4835.71N/01627.90E#MeshCom 4.0/B=074/A=000755
20260208144840	OE3CIN-4>APRSGW,TCPIP*,qAR,OE3CIN-4:!4835.71N/01627.90E#MeshCom 4.0/B=072/A=000755
20260208151900	OE3CIN-4>APRSGW,TCPIP*,qAR,OE3CIN-4:!4835.71N/01627.90E#MeshCom 4.0/B=074/A=000755
20260208154921	OE3CIN-4>APRSGW,TCPIP*,qAR,OE3CIN-4:!4835.71N/01627.90E#MeshCom 4.0/B=075/A=000755
20260208161941	OE3CIN-4>APRSGW,TCPIP*,qAR,OE3CIN-4:!4835.71N/01627.90E#MeshCom 4.0/B=077/A=000755
20260208165001	OE3CIN-4>APRSGW,TCPIP*,qAR,OE3CIN-4:!4835.71N/01627.90E#MeshCom 4.0/B=079/A=000755
20260208172022	OE3CIN-4>APRSGW,TCPIP*,qAR,OE3CIN-4:!4835.71N/01627.90E#MeshCom 4.0/B=079/A=000755
20260208175042	OE3CIN-4>APRSGW,TCPIP*,qAR,OE3CIN-4:!4835.71N/01627.90E#MeshCom 4.0/B=079/A=000755
20260208182102	OE3CIN-4>APRSGW,TCPIP*,qAR,OE3CIN-4:!4835.71N/01627.90E#MeshCom 4.0/B=078/A=000755
20260208185122	OE3CIN-4>APRSGW,TCPIP*,qAR,OE3CIN-4:!4835.71N/01627.90E#MeshCom 4.0/B=079/A=000755