APRS Packet Errors for SV1JSX (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
20260405070348	SV1JSX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1JSX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.8500 MHz
20260405073452	SV1JSX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1JSX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.8500 MHz
20260405080553	SV1JSX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1JSX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.8500 MHz
20260405083656	SV1JSX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1JSX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.8500 MHz
20260405090757	SV1JSX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1JSX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.8500 MHz
20260405093844	SV1JSX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1JSX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.8500 MHz
20260405100943	SV1JSX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1JSX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.8500 MHz
20260405104043	SV1JSX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1JSX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.8500 MHz
20260405114238	SV1JSX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1JSX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.8500 MHz
20260405121325	SV1JSX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1JSX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.8500 MHz