A total of 106 recevied packets have been found for station/object EA2RE-DP between 07/04/2025 7:13:15 PM+00:00 and 07/07/2025 7:13:15 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 106 packets.
[>] 07/07/2025 6:58:44 PM+00:00:
EA2RE>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 07/07/2025 6:28:09 PM+00:00:
EA2RE>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 07/07/2025 5:57:34 PM+00:00:
EA2RE>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 07/07/2025 5:27:01 PM+00:00:
EA2RE>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 07/07/2025 4:56:27 PM+00:00:
EA2RE>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 07/07/2025 4:25:53 PM+00:00:
EA2RE>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 07/07/2025 3:55:19 PM+00:00:
EA2RE>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 07/07/2025 3:24:45 PM+00:00:
EA2RE>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 07/07/2025 2:54:11 PM+00:00:
EA2RE>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 07/07/2025 2:23:38 PM+00:00:
EA2RE>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 07/07/2025 1:53:03 PM+00:00:
EA2RE>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 07/07/2025 1:22:33 PM+00:00:
EA2RE>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 07/07/2025 12:52:02 PM+00:00:
EA2RE>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 07/07/2025 12:21:33 PM+00:00:
EA2RE>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 07/07/2025 11:51:04 AM+00:00:
EA2RE>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 07/07/2025 11:20:36 AM+00:00:
EA2RE>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 07/07/2025 10:50:04 AM+00:00:
EA2RE>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 07/07/2025 10:19:30 AM+00:00:
EA2RE>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 07/07/2025 9:48:59 AM+00:00:
EA2RE>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 07/07/2025 9:18:29 AM+00:00:
EA2RE>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 07/07/2025 8:47:59 AM+00:00:
EA2RE>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 07/07/2025 8:17:30 AM+00:00:
EA2RE>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 07/07/2025 7:47:01 AM+00:00:
EA2RE>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 07/07/2025 7:16:32 AM+00:00:
EA2RE>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 07/07/2025 6:46:03 AM+00:00:
EA2RE>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 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.