APRS Packet Errors for SV2JQG (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
20260701183614	SV2JQG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV2JQG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 439.8000 MHz
20260701190713	SV2JQG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV2JQG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 439.8000 MHz
20260701193758	SV2JQG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV2JQG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 439.8000 MHz
20260701200839	SV2JQG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV2JQG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 439.8000 MHz
20260701203935	SV2JQG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV2JQG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 439.8000 MHz
20260701211029	SV2JQG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV2JQG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 439.8000 MHz
20260701214127	SV2JQG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV2JQG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 439.8000 MHz
20260701221236	SV2JQG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV2JQG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 439.8000 MHz
20260701224330	SV2JQG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV2JQG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 439.8000 MHz
20260701231440	SV2JQG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV2JQG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 439.8000 MHz