APRS Packet Errors for SV1QEL (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
20250417161112	SV1QEL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1QEL-DP!0000.00N/240660960rRNG0034 IPSC2-GR-DMO2 MMDVM 431.0250 MHz
20250417164235	SV1QEL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1QEL-DP!0000.00N/240660960rRNG0034 IPSC2-GR-DMO2 MMDVM 431.0250 MHz
20250417171337	SV1QEL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1QEL-DP!0000.00N/240660960rRNG0034 IPSC2-GR-DMO2 MMDVM 431.0250 MHz
20250417174435	SV1QEL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1QEL-DP!0000.00N/240660960rRNG0034 IPSC2-GR-DMO2 MMDVM 431.0250 MHz
20250417181545	SV1QEL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1QEL-DP!0000.00N/240660960rRNG0034 IPSC2-GR-DMO2 MMDVM 431.0250 MHz
20250417184708	SV1QEL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1QEL-DP!0000.00N/240660960rRNG0034 IPSC2-GR-DMO2 MMDVM 431.0250 MHz
20250417191758	SV1QEL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1QEL-DP!0000.00N/240660960rRNG0034 IPSC2-GR-DMO2 MMDVM 431.0250 MHz
20250417194905	SV1QEL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1QEL-DP!0000.00N/240660960rRNG0034 IPSC2-GR-DMO2 MMDVM 431.0250 MHz
20250417202013	SV1QEL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1QEL-DP!0000.00N/240660960rRNG0034 IPSC2-GR-DMO2 MMDVM 431.0250 MHz
20250417205111	SV1QEL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1QEL-DP!0000.00N/240660960rRNG0034 IPSC2-GR-DMO2 MMDVM 431.0250 MHz