APRS Packet Errors for OE1GKS (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
20260804110703OE1GKS>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE1GKS-DP!0000.00N/000-0.00ErRNG0034 IPSC2-OE-DMO MMDVM 430.1000 MHz
20260804113740OE1GKS>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE1GKS-DP!0000.00N/000-0.00ErRNG0034 IPSC2-OE-DMO MMDVM 430.1000 MHz
20260804120815OE1GKS>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE1GKS-DP!0000.00N/000-0.00ErRNG0034 IPSC2-OE-DMO MMDVM 430.1000 MHz
20260804123850OE1GKS>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE1GKS-DP!0000.00N/000-0.00ErRNG0034 IPSC2-OE-DMO MMDVM 430.1000 MHz
20260804130925OE1GKS>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE1GKS-DP!0000.00N/000-0.00ErRNG0034 IPSC2-OE-DMO MMDVM 430.1000 MHz
20260804134001OE1GKS>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE1GKS-DP!0000.00N/000-0.00ErRNG0034 IPSC2-OE-DMO MMDVM 430.1000 MHz
20260804141038OE1GKS>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE1GKS-DP!0000.00N/000-0.00ErRNG0034 IPSC2-OE-DMO MMDVM 430.1000 MHz
20260804144111OE1GKS>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE1GKS-DP!0000.00N/000-0.00ErRNG0034 IPSC2-OE-DMO MMDVM 430.1000 MHz
20260804151145OE1GKS>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE1GKS-DP!0000.00N/000-0.00ErRNG0034 IPSC2-OE-DMO MMDVM 430.1000 MHz
20260804154222OE1GKS>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE1GKS-DP!0000.00N/000-0.00ErRNG0034 IPSC2-OE-DMO MMDVM 430.1000 MHz