APRS Packet Errors for DO3SYM-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
20260209143257	DO3SYM-10>AP4R10,TCPIP*,qAC,T2NUERNBG:!4930.35NI01130.72E&PHG2100 APRS4R IGATE
20260209150257	DO3SYM-10>AP4R10,TCPIP*,qAC,T2NUERNBG:!4930.35NI01130.72E&PHG2100 APRS4R IGATE
20260209153257	DO3SYM-10>AP4R10,TCPIP*,qAC,T2NUERNBG:!4930.35NI01130.72E&PHG2100 APRS4R IGATE
20260209160257	DO3SYM-10>AP4R10,TCPIP*,qAC,T2NUERNBG:!4930.35NI01130.72E&PHG2100 APRS4R IGATE
20260209163257	DO3SYM-10>AP4R10,TCPIP*,qAC,T2NUERNBG:!4930.35NI01130.72E&PHG2100 APRS4R IGATE
20260209170257	DO3SYM-10>AP4R10,TCPIP*,qAC,T2NUERNBG:!4930.35NI01130.72E&PHG2100 APRS4R IGATE
20260209173257	DO3SYM-10>AP4R10,TCPIP*,qAC,T2NUERNBG:!4930.35NI01130.72E&PHG2100 APRS4R IGATE
20260209180257	DO3SYM-10>AP4R10,TCPIP*,qAC,T2NUERNBG:!4930.35NI01130.72E&PHG2100 APRS4R IGATE
20260209183257	DO3SYM-10>AP4R10,TCPIP*,qAC,T2NUERNBG:!4930.35NI01130.72E&PHG2100 APRS4R IGATE
20260209190257	DO3SYM-10>AP4R10,TCPIP*,qAC,T2NUERNBG:!4930.35NI01130.72E&PHG2100 APRS4R IGATE
20260209193257	DO3SYM-10>AP4R10,TCPIP*,qAC,T2NUERNBG:!4930.35NI01130.72E&PHG2100 APRS4R IGATE
20260209200257	DO3SYM-10>AP4R10,TCPIP*,qAC,T2NUERNBG:!4930.35NI01130.72E&PHG2100 APRS4R IGATE