A total of 42 recevied packets have been found for station/object VK3DB-DP between 07/22/2025 6:03:55 PM+00:00 and 07/25/2025 6:03:55 PM+00:00.
Request took 0.005 seconds to find in our database.
Packet history is available for up to 3 days. Sign up for a free account to view 30 up to days history. Use [>] to decode with our packet packet decoder tool.
Displaying 1 - 25 of 42 packets.
[>] 07/25/2025 5:31:41 PM+00:00:
VK3DB>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 07/25/2025 4:53:39 PM+00:00:
VK3DB>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 07/25/2025 4:15:17 PM+00:00:
VK3DB>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 07/25/2025 3:37:24 PM+00:00:
VK3DB>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 07/25/2025 2:59:35 PM+00:00:
VK3DB>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 07/25/2025 2:21:26 PM+00:00:
VK3DB>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 07/25/2025 1:43:26 PM+00:00:
VK3DB>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 07/25/2025 1:05:41 PM+00:00:
VK3DB>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 07/25/2025 12:27:26 PM+00:00:
VK3DB>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 07/25/2025 11:49:22 AM+00:00:
VK3DB>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 07/25/2025 11:11:04 AM+00:00:
VK3DB>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 07/25/2025 10:32:18 AM+00:00:
VK3DB>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 07/25/2025 9:53:42 AM+00:00:
VK3DB>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 07/25/2025 9:13:53 AM+00:00:
VK3DB>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 07/25/2025 8:34:48 AM+00:00:
VK3DB>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 07/25/2025 7:55:02 AM+00:00:
VK3DB>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 07/25/2025 7:16:21 AM+00:00:
VK3DB>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 07/25/2025 6:37:49 AM+00:00:
VK3DB>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 07/25/2025 5:59:17 AM+00:00:
VK3DB>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 07/25/2025 5:20:38 AM+00:00:
VK3DB>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 07/25/2025 4:03:42 AM+00:00:
VK3DB>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 07/24/2025 11:37:04 PM+00:00:
VK3DB>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 07/24/2025 10:59:24 PM+00:00:
VK3DB>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 07/24/2025 10:21:47 PM+00:00:
VK3DB>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 07/24/2025 9:43:45 PM+00:00:
VK3DB>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
* If you compare the raw packets with similar data from other websites it may differ (especially the path), the reason is that we are not collecting packets from the same APRS-IS servers. Each APRS-IS server performes duplicate filtering, and which packet that is considered to be a duplicate may differ depending on which APRS-IS server you receive your data from.