APRS Packet Errors for OE6HLQ (last 24 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
20250913135352OE6HLQ>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE6HLQ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 430.7250 MHz
20250913142425OE6HLQ>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE6HLQ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 430.7250 MHz
20250913145457OE6HLQ>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE6HLQ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 430.7250 MHz
20250913152528OE6HLQ>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE6HLQ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 430.7250 MHz
20250913155559OE6HLQ>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE6HLQ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 430.7250 MHz
20250913162632OE6HLQ>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE6HLQ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 430.7250 MHz
20250913165705OE6HLQ>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE6HLQ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 430.7250 MHz
20250913172737OE6HLQ>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE6HLQ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 430.7250 MHz
20250913175810OE6HLQ>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE6HLQ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 430.7250 MHz
20250913182847OE6HLQ>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE6HLQ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 430.7250 MHz