A total of 89 recevied packets have been found for station/object VK4XK-DP between 07/04/2025 10:11:45 PM+00:00 and 07/07/2025 10:11:45 PM+00:00.
Request took 0.007 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 89 packets.
[>] 07/07/2025 7:32:42 PM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/07/2025 6:55:37 PM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/07/2025 6:17:52 PM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/07/2025 5:40:42 PM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/07/2025 5:03:32 PM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/07/2025 4:26:29 PM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/07/2025 3:49:29 PM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/07/2025 3:12:19 PM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/07/2025 2:35:02 PM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/07/2025 1:57:58 PM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/07/2025 1:20:36 PM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/07/2025 12:43:13 PM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/07/2025 12:05:13 PM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/07/2025 11:27:16 AM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/07/2025 10:49:16 AM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/07/2025 10:11:07 AM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/07/2025 9:33:02 AM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/07/2025 8:55:06 AM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/07/2025 8:17:06 AM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/07/2025 7:39:00 AM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 07/07/2025 7:00: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 7:39:49 PM+00:00:
VK4XK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)VK4XK-DP!2328.98S/15019.76ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
[>] 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
* 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.