APRS Packet Errors for SY1DWP (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
20250331231523SY1DWP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SY1DWP-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.5500 MHz
20250331234601SY1DWP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SY1DWP-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.5500 MHz
20250401001638SY1DWP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SY1DWP-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.5500 MHz
20250401004715SY1DWP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SY1DWP-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.5500 MHz
20250401011753SY1DWP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SY1DWP-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.5500 MHz
20250401014830SY1DWP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SY1DWP-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.5500 MHz
20250401021906SY1DWP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SY1DWP-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.5500 MHz
20250401024942SY1DWP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SY1DWP-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.5500 MHz
20250401032019SY1DWP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SY1DWP-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.5500 MHz
20250401035055SY1DWP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SY1DWP-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.5500 MHz