APRS Packet Errors for SV4NXE (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
20260611023258	SV4NXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4NXE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.0000 MHz
20260611030356	SV4NXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4NXE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.0000 MHz
20260611033454	SV4NXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4NXE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.0000 MHz
20260611040551	SV4NXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4NXE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.0000 MHz
20260611043636	SV4NXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4NXE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.0000 MHz
20260611050748	SV4NXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4NXE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.0000 MHz
20260611053903	SV4NXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4NXE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.0000 MHz
20260611061003	SV4NXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4NXE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.0000 MHz
20260611071154	SV4NXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4NXE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.0000 MHz
20260611081325	SV4NXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4NXE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.0000 MHz