A total of 57 recevied packets have been found for station/object WP4GT-DP between 07/24/2025 1:08:12 AM+00:00 and 07/27/2025 1:08:12 AM+00:00.
Request took 0.004 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 57 packets.
[>] 07/27/2025 12:56:48 AM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 07/27/2025 12:26:21 AM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 07/26/2025 11:55:54 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 07/26/2025 11:25:27 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 07/26/2025 10:55:00 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 07/26/2025 10:24:33 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 07/26/2025 9:54:06 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 07/26/2025 9:23:39 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 07/26/2025 8:53:12 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 07/26/2025 8:22:45 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 07/26/2025 7:52:14 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 07/26/2025 7:21:44 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 07/26/2025 6:51:16 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 07/26/2025 6:20:47 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 07/25/2025 11:32:47 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 07/25/2025 11:02:20 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 07/25/2025 10:31:52 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 07/25/2025 10:01:24 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 07/25/2025 9:30:54 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 07/25/2025 9:00:24 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 07/25/2025 8:29:55 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 07/25/2025 7:59:25 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 07/25/2025 7:28:54 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 07/25/2025 6:58:23 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 07/25/2025 6:27:53 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 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.