APRS Packet Errors for SV4JYD (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
20250325003945SV4JYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 439.9875 MHz
20250325003945SV4JYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 144.8500 MHz
20250325011025SV4JYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 144.8500 MHz
20250325011025SV4JYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 439.9875 MHz
20250325014105SV4JYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 144.8500 MHz
20250325014105SV4JYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 439.9875 MHz
20250325021145SV4JYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 144.8500 MHz
20250325021145SV4JYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 439.9875 MHz
20250325024225SV4JYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 144.8500 MHz
20250325024225SV4JYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 439.9875 MHz
20250325031304SV4JYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 144.8500 MHz
20250325031304SV4JYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 439.9875 MHz
20250325034344SV4JYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 144.8500 MHz
20250325034344SV4JYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 439.9875 MHz
20250325041423SV4JYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 144.8500 MHz
20250325041423SV4JYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 439.9875 MHz
20250325044503SV4JYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 144.8500 MHz
20250325044503SV4JYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 439.9875 MHz
20250325051543SV4JYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 144.8500 MHz
20250325051543SV4JYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 439.9875 MHz
20250325054622SV4JYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 144.8500 MHz
20250325054622SV4JYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 439.9875 MHz
20250325061704SV4JYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 144.8500 MHz
20250325061704SV4JYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 439.9875 MHz