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
20251215200921	SV4NXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4NXE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.0000 MHz
20251215204008	SV4NXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4NXE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.0000 MHz
20251215211056	SV4NXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4NXE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.0000 MHz
20251215214152	SV4NXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4NXE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.0000 MHz
20251215221312	SV4NXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4NXE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.0000 MHz
20251215224434	SV4NXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4NXE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.0000 MHz
20251215231553	SV4NXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4NXE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.0000 MHz
20251215234722	SV4NXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4NXE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.0000 MHz
20251216001828	SV4NXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4NXE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.0000 MHz
20251216004947	SV4NXE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4NXE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.0000 MHz