APRS Packet Errors for BG7MHE-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
20260208134438	BG7MHE-10>APDW17,TCPIP*,qAC,T2CS:!2304.68N11319.75E-/A=000098 RTL-SDR Blog V4 144.640MHz
20260208141438	BG7MHE-10>APDW17,TCPIP*,qAC,T2CS:!2304.68N11319.75E-/A=000098 RTL-SDR Blog V4 144.640MHz
20260208144438	BG7MHE-10>APDW17,TCPIP*,qAC,T2CS:!2304.68N11319.75E-/A=000098 RTL-SDR Blog V4 144.640MHz
20260208151438	BG7MHE-10>APDW17,TCPIP*,qAC,T2CS:!2304.68N11319.75E-/A=000098 RTL-SDR Blog V4 144.640MHz
20260208154438	BG7MHE-10>APDW17,TCPIP*,qAC,T2CS:!2304.68N11319.75E-/A=000098 RTL-SDR Blog V4 144.640MHz
20260208161438	BG7MHE-10>APDW17,TCPIP*,qAC,T2CS:!2304.68N11319.75E-/A=000098 RTL-SDR Blog V4 144.640MHz
20260208164438	BG7MHE-10>APDW17,TCPIP*,qAC,T2CS:!2304.68N11319.75E-/A=000098 RTL-SDR Blog V4 144.640MHz
20260208171438	BG7MHE-10>APDW17,TCPIP*,qAC,T2CS:!2304.68N11319.75E-/A=000098 RTL-SDR Blog V4 144.640MHz
20260208174438	BG7MHE-10>APDW17,TCPIP*,qAC,T2CS:!2304.68N11319.75E-/A=000098 RTL-SDR Blog V4 144.640MHz
20260208181438	BG7MHE-10>APDW17,TCPIP*,qAC,T2CS:!2304.68N11319.75E-/A=000098 RTL-SDR Blog V4 144.640MHz
20260208184438	BG7MHE-10>APDW17,TCPIP*,qAC,T2CS:!2304.68N11319.75E-/A=000098 RTL-SDR Blog V4 144.640MHz
20260208191438	BG7MHE-10>APDW17,TCPIP*,qAC,T2CS:!2304.68N11319.75E-/A=000098 RTL-SDR Blog V4 144.640MHz