APRS Packet Errors for SV7TRK (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
20251219131650	SV7TRK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV7TRK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.0250 MHz
20251219134758	SV7TRK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV7TRK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.0250 MHz
20251219141851	SV7TRK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV7TRK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.0250 MHz
20251219145012	SV7TRK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV7TRK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.0250 MHz
20251219152056	SV7TRK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV7TRK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.0250 MHz
20251219155155	SV7TRK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV7TRK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.0250 MHz
20251219172459	SV7TRK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV7TRK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.0250 MHz
20251219175556	SV7TRK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV7TRK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.0250 MHz
20251219182409	SV7TRK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV7TRK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 438.0250 MHz
20251219185415	SV7TRK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV7TRK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 438.0250 MHz