A total of 92 recevied packets have been found for station/object VK4XK-DP between 07/03/2025 7:11:26 PM+00:00 and 07/06/2025 7:11:26 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 92 packets.
[>] 07/06/2025 7:02:47 PM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/06/2025 6:25:09 PM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/06/2025 5:48:10 PM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/06/2025 5:11:16 PM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/06/2025 4:34:24 PM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/06/2025 3:57:28 PM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/06/2025 3:20:30 PM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/06/2025 2:43:28 PM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/06/2025 2:06:11 PM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/06/2025 1:29:10 PM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/06/2025 12:51:30 PM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/06/2025 12:14:04 PM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/06/2025 11:35:50 AM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/06/2025 10:57:08 AM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/06/2025 10:18:35 AM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/06/2025 9:40:32 AM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/06/2025 9:01:35 AM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/06/2025 8:23:34 AM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/06/2025 7:45:07 AM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/06/2025 7:06:27 AM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/06/2025 6:28:13 AM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/06/2025 5:50:20 AM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/06/2025 5:12:37 AM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/06/2025 4:34:23 AM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/06/2025 3:56:34 AM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 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.