APRS Packet Errors for KB3TEM (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
20260220051748	KB3TEM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KB3TEM-DP!3800.00N/095-0.00WrRNG0034 IPSC2-QUADNET MMDVM 444.0000@+5.0 MHz
20260220054808	KB3TEM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KB3TEM-DP!3800.00N/095-0.00WrRNG0034 IPSC2-QUADNET MMDVM 444.0000@+5.0 MHz
20260220061826	KB3TEM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KB3TEM-DP!3800.00N/095-0.00WrRNG0034 IPSC2-QUADNET MMDVM 444.0000@+5.0 MHz
20260220064846	KB3TEM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KB3TEM-DP!3800.00N/095-0.00WrRNG0034 IPSC2-QUADNET MMDVM 444.0000@+5.0 MHz
20260220071905	KB3TEM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KB3TEM-DP!3800.00N/095-0.00WrRNG0034 IPSC2-QUADNET MMDVM 444.0000@+5.0 MHz
20260220074925	KB3TEM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KB3TEM-DP!3800.00N/095-0.00WrRNG0034 IPSC2-QUADNET MMDVM 444.0000@+5.0 MHz
20260220081943	KB3TEM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KB3TEM-DP!3800.00N/095-0.00WrRNG0034 IPSC2-QUADNET MMDVM 444.0000@+5.0 MHz
20260220085007	KB3TEM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KB3TEM-DP!3800.00N/095-0.00WrRNG0034 IPSC2-QUADNET MMDVM 444.0000@+5.0 MHz
20260220092022	KB3TEM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KB3TEM-DP!3800.00N/095-0.00WrRNG0034 IPSC2-QUADNET MMDVM 444.0000@+5.0 MHz