APRS Packet Errors for OE4EXE-1 (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
20260208134317	OE4EXE-1>APRSGW,TCPIP*,qAR,OE4EXE-1:!4742.50N/01654.64E-MeshCom GW 1/A=000551
20260208141332	OE4EXE-1>APRSGW,TCPIP*,qAR,OE4EXE-1:!4742.50N/01654.64E-MeshCom GW 1/A=000551
20260208144347	OE4EXE-1>APRSGW,TCPIP*,qAR,OE4EXE-1:!4742.50N/01654.64E-MeshCom GW 1/A=000551
20260208151402	OE4EXE-1>APRSGW,TCPIP*,qAR,OE4EXE-1:!4742.50N/01654.64E-MeshCom GW 1/A=000551
20260208154417	OE4EXE-1>APRSGW,TCPIP*,qAR,OE4EXE-1:!4742.50N/01654.64E-MeshCom GW 1/A=000551
20260208161432	OE4EXE-1>APRSGW,TCPIP*,qAR,OE4EXE-1:!4742.50N/01654.64E-MeshCom GW 1/A=000551
20260208164450	OE4EXE-1>APRSGW,TCPIP*,qAR,OE4EXE-1:!4742.50N/01654.64E-MeshCom GW 1/A=000551
20260208171505	OE4EXE-1>APRSGW,TCPIP*,qAR,OE4EXE-1:!4742.50N/01654.64E-MeshCom GW 1/A=000551
20260208174517	OE4EXE-1>APRSGW,TCPIP*,qAR,OE4EXE-1:!4742.50N/01654.64E-MeshCom GW 1/A=000551
20260208181532	OE4EXE-1>APRSGW,TCPIP*,qAR,OE4EXE-1:!4742.50N/01654.64E-MeshCom GW 1/A=000551
20260208184547	OE4EXE-1>APRSGW,TCPIP*,qAR,OE4EXE-1:!4742.50N/01654.64E-MeshCom GW 1/A=000551