APRS Packet Errors for 7M3SKC-10 (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
20260209110852	7M3SKC-10>BEACON,TCPIP*,qAC,FIFTH:!4029.58N/14125.51E&73. IGATE2 App.
20260209113852	7M3SKC-10>BEACON,TCPIP*,qAC,FIFTH:!4029.58N/14125.51E&73. IGATE2 App.
20260209120852	7M3SKC-10>BEACON,TCPIP*,qAC,FIFTH:!4029.58N/14125.51E&73. IGATE2 App.
20260209123853	7M3SKC-10>BEACON,TCPIP*,qAC,FIFTH:!4029.58N/14125.51E&73. IGATE2 App.
20260209130853	7M3SKC-10>BEACON,TCPIP*,qAC,FIFTH:!4029.58N/14125.51E&73. IGATE2 App.
20260209133853	7M3SKC-10>BEACON,TCPIP*,qAC,FIFTH:!4029.58N/14125.51E&73. IGATE2 App.
20260209140854	7M3SKC-10>BEACON,TCPIP*,qAC,FIFTH:!4029.58N/14125.51E&73. IGATE2 App.
20260209143854	7M3SKC-10>BEACON,TCPIP*,qAC,FIFTH:!4029.58N/14125.51E&73. IGATE2 App.
20260209150854	7M3SKC-10>BEACON,TCPIP*,qAC,FIFTH:!4029.58N/14125.51E&73. IGATE2 App.
20260209153855	7M3SKC-10>BEACON,TCPIP*,qAC,FIFTH:!4029.58N/14125.51E&73. IGATE2 App.
20260209160855	7M3SKC-10>BEACON,TCPIP*,qAC,FIFTH:!4029.58N/14125.51E&73. IGATE2 App.
20260209163856	7M3SKC-10>BEACON,TCPIP*,qAC,FIFTH:!4029.58N/14125.51E&73. IGATE2 App.