APRS Packet Errors for SV3SMG (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
20250531235506	SV3SMG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV3SMG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 144.8250 MHz
20250601002601	SV3SMG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV3SMG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 144.8250 MHz
20250601012750	SV3SMG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV3SMG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 144.8250 MHz
20250601022938	SV3SMG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV3SMG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 144.8250 MHz
20250601030105	SV3SMG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV3SMG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 144.8250 MHz
20250601033234	SV3SMG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV3SMG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 144.8250 MHz
20250601040324	SV3SMG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV3SMG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 144.8250 MHz
20250601043436	SV3SMG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV3SMG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 144.8250 MHz
20250601050605	SV3SMG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV3SMG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 144.8250 MHz
20250601053717	SV3SMG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV3SMG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 144.8250 MHz