APRS Packet Errors for OE5GNB (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
20250807002310OE5GNB>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE5GNB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 435.0000 MHz
20250807005339OE5GNB>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE5GNB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 435.0000 MHz
20250807012409OE5GNB>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE5GNB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 435.0000 MHz
20250807015438OE5GNB>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE5GNB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 435.0000 MHz
20250807022508OE5GNB>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE5GNB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 435.0000 MHz
20250807025538OE5GNB>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE5GNB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 435.0000 MHz
20250807032608OE5GNB>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE5GNB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 435.0000 MHz
20250807035637OE5GNB>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE5GNB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 435.0000 MHz
20250807042706OE5GNB>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE5GNB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 435.0000 MHz
20250807045736OE5GNB>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE5GNB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 435.0000 MHz