APRS Packet Errors for SV4FFB-DP (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
20260209131328SV4FFB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4FFB-DP!3922.73N/02245.11ErRNG0034 IPSC2-GR-DMO MMDVM 439.9625 MHz
20260209131328SV4FFB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4FFB-DP!3922.72N/02245.12ErRNG0034 IPSC2-GR-DMO MMDVM 439.9875 MHz
20260209134359SV4FFB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4FFB-DP!3922.73N/02245.11ErRNG0034 IPSC2-GR-DMO MMDVM 439.9625 MHz
20260209134359SV4FFB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4FFB-DP!3922.72N/02245.12ErRNG0034 IPSC2-GR-DMO MMDVM 439.9875 MHz
20260209141451SV4FFB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4FFB-DP!3922.73N/02245.11ErRNG0034 IPSC2-GR-DMO MMDVM 439.9625 MHz
20260209141451SV4FFB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4FFB-DP!3922.72N/02245.12ErRNG0034 IPSC2-GR-DMO MMDVM 439.9875 MHz
20260209144522SV4FFB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4FFB-DP!3922.73N/02245.11ErRNG0034 IPSC2-GR-DMO MMDVM 439.9625 MHz
20260209144522SV4FFB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4FFB-DP!3922.72N/02245.12ErRNG0034 IPSC2-GR-DMO MMDVM 439.9875 MHz
20260209151554SV4FFB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4FFB-DP!3922.73N/02245.11ErRNG0034 IPSC2-GR-DMO MMDVM 439.9625 MHz
20260209151554SV4FFB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4FFB-DP!3922.72N/02245.12ErRNG0034 IPSC2-GR-DMO MMDVM 439.9875 MHz
20260209154626SV4FFB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4FFB-DP!3922.73N/02245.11ErRNG0034 IPSC2-GR-DMO MMDVM 439.9625 MHz
20260209154626SV4FFB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4FFB-DP!3922.72N/02245.12ErRNG0034 IPSC2-GR-DMO MMDVM 439.9875 MHz
20260209161658SV4FFB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4FFB-DP!3922.73N/02245.11ErRNG0034 IPSC2-GR-DMO MMDVM 439.9625 MHz
20260209161658SV4FFB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4FFB-DP!3922.72N/02245.12ErRNG0034 IPSC2-GR-DMO MMDVM 439.9875 MHz
20260209164730SV4FFB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4FFB-DP!3922.73N/02245.11ErRNG0034 IPSC2-GR-DMO MMDVM 439.9625 MHz
20260209164730SV4FFB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4FFB-DP!3922.72N/02245.12ErRNG0034 IPSC2-GR-DMO MMDVM 439.9875 MHz
20260209171802SV4FFB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4FFB-DP!3922.73N/02245.11ErRNG0034 IPSC2-GR-DMO MMDVM 439.9625 MHz
20260209171802SV4FFB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4FFB-DP!3922.72N/02245.12ErRNG0034 IPSC2-GR-DMO MMDVM 439.9875 MHz
20260209174834SV4FFB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4FFB-DP!3922.73N/02245.11ErRNG0034 IPSC2-GR-DMO MMDVM 439.9625 MHz
20260209174835SV4FFB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4FFB-DP!3922.72N/02245.12ErRNG0034 IPSC2-GR-DMO MMDVM 439.9875 MHz
20260209181907SV4FFB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4FFB-DP!3922.73N/02245.11ErRNG0034 IPSC2-GR-DMO MMDVM 439.9625 MHz
20260209181907SV4FFB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4FFB-DP!3922.72N/02245.12ErRNG0034 IPSC2-GR-DMO MMDVM 439.9875 MHz
20260209184929SV4FFB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4FFB-DP!3922.73N/02245.11ErRNG0034 IPSC2-GR-DMO MMDVM 439.9625 MHz
20260209184929SV4FFB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4FFB-DP!3922.72N/02245.12ErRNG0034 IPSC2-GR-DMO MMDVM 439.9875 MHz