A total of 104 recevied packets have been found for station/object EA2RE-DP between 06/02/2025 5:18:18 PM+00:00 and 06/05/2025 5:18:18 PM+00:00.
Request took 0.011 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 104 packets.
[>] 06/05/2025 5:06:26 PM+00:00:
EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 06/05/2025 4:35:45 PM+00:00:
EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 06/05/2025 4:04:58 PM+00:00:
EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 06/05/2025 3:34:10 PM+00:00:
EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 06/05/2025 3:03:22 PM+00:00:
EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 06/05/2025 2:32:40 PM+00:00:
EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 06/05/2025 2:01:57 PM+00:00:
EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 06/05/2025 1:31:12 PM+00:00:
EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 06/05/2025 1:00:30 PM+00:00:
EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 06/05/2025 12:29:47 PM+00:00:
EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 06/05/2025 11:59:04 AM+00:00:
EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 06/05/2025 11:28:23 AM+00:00:
EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 06/05/2025 10:57:42 AM+00:00:
EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 06/05/2025 10:27:02 AM+00:00:
EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 06/05/2025 9:25:44 AM+00:00:
EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 06/05/2025 8:55:02 AM+00:00:
EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 06/05/2025 8:24:26 AM+00:00:
EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 06/05/2025 7:53:51 AM+00:00:
EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 06/05/2025 7:23:14 AM+00:00:
EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 06/05/2025 6:52:37 AM+00:00:
EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 06/05/2025 12:14:55 AM+00:00:
EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 06/04/2025 11:44:17 PM+00:00:
EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 06/04/2025 11:13:42 PM+00:00:
EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 06/04/2025 10:43:02 PM+00:00:
EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!4316.26N/00257.48WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
[>] 06/04/2025 10:12:21 PM+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.