A total of 49 recevied packets have been found for station/object VK3DB-DP between 06/16/2025 7:12:30 AM+00:00 and 06/19/2025 7:12:30 AM+00:00.
Request took 0.003 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 49 packets.
[>] 06/19/2025 6:47:42 AM+00:00:
VK3DB>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 06/19/2025 6:09:59 AM+00:00:
VK3DB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 06/19/2025 5:31:54 AM+00:00:
VK3DB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 06/19/2025 4:54:07 AM+00:00:
VK3DB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 06/19/2025 4:16:02 AM+00:00:
VK3DB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 06/19/2025 3:38:14 AM+00:00:
VK3DB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 06/19/2025 3:00:43 AM+00:00:
VK3DB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 06/19/2025 2:23:09 AM+00:00:
VK3DB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 06/19/2025 1:45:34 AM+00:00:
VK3DB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 06/19/2025 1:05:32 AM+00:00:
VK3DB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 06/19/2025 12:26:57 AM+00:00:
VK3DB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 06/18/2025 11:49:32 PM+00:00:
VK3DB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 06/18/2025 11:12:17 PM+00:00:
VK3DB>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 06/18/2025 10:34:27 PM+00:00:
VK3DB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 06/18/2025 9:57:02 PM+00:00:
VK3DB>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 06/18/2025 9:19:56 PM+00:00:
VK3DB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 06/18/2025 8:42:45 PM+00:00:
VK3DB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 06/18/2025 8:04:42 PM+00:00:
VK3DB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 06/18/2025 7:25:51 PM+00:00:
VK3DB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 06/18/2025 6:47:57 PM+00:00:
VK3DB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 06/18/2025 6:10:20 PM+00:00:
VK3DB>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 06/18/2025 5:32:49 PM+00:00:
VK3DB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 06/18/2025 4:55:11 PM+00:00:
VK3DB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 06/18/2025 4:17:47 PM+00:00:
VK3DB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3DB-DP!3810.25S/14616.06ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
[>] 06/18/2025 3:40:27 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.