A total of 92 recevied packets have been found for station/object WP4GT-DP between 06/16/2025 10:48:56 PM+00:00 and 06/19/2025 10:48:56 PM+00:00.
Request took 0.009 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.
[>] 06/19/2025 10:47:55 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 06/19/2025 10:17:17 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 06/19/2025 9:46:37 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 06/19/2025 9:15:58 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 06/19/2025 8:45:22 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 06/19/2025 8:14:46 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 06/19/2025 7:44:09 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 06/19/2025 7:13:30 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 06/19/2025 6:42:52 PM+00:00:
WP4GT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 06/19/2025 6:12:10 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 06/19/2025 5:41:30 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 06/19/2025 5:10:47 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 06/19/2025 4:40:09 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 06/19/2025 4:09:30 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 06/19/2025 3:38:51 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 06/19/2025 3:08:13 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 06/19/2025 2:37:34 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 06/19/2025 2:06:56 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 06/19/2025 1:36:15 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 06/19/2025 1:05:34 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 06/19/2025 12:34:52 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 06/19/2025 12:04:14 PM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 06/19/2025 11:33:34 AM+00:00:
WP4GT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 06/19/2025 11:02:55 AM+00:00:
WP4GT>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)WP4GT-DP!4144.00N/05023.99WrRNG0034 IPSC2-EA-Hotspot MMDVM 224.9400 MHz
[>] 06/19/2025 10:32:15 AM+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.