APRS Packet Errors for SV5SSS (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
20251214090619	SV5SSS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV5SSS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.8000 MHz
20251214093707	SV5SSS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV5SSS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.8000 MHz
20251214100756	SV5SSS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV5SSS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.8000 MHz
20251214103843	SV5SSS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV5SSS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.8000 MHz
20251214110931	SV5SSS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV5SSS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.8000 MHz
20251214114019	SV5SSS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV5SSS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.8000 MHz
20251214121107	SV5SSS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV5SSS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.8000 MHz
20251214134337	SV5SSS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV5SSS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.8000 MHz
20251214141426	SV5SSS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV5SSS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.8000 MHz
20251214144514	SV5SSS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV5SSS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.8000 MHz