A total of 123 recevied packets have been found for station/object EA4GEM-DP between 07/03/2025 11:06:15 PM+00:00 and 07/06/2025 11:06:15 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 123 packets.
[>] 07/06/2025 10:44:56 PM+00:00:
EA4GEM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4GEM-DP!4800.00N/01600.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4125 MHz
[>] 07/06/2025 10:14:23 PM+00:00:
EA4GEM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4GEM-DP!4800.00N/01600.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4125 MHz
[>] 07/06/2025 9:43:19 PM+00:00:
EA4GEM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4GEM-DP!4800.00N/01600.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4125 MHz
[>] 07/06/2025 9:12:41 PM+00:00:
EA4GEM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4GEM-DP!4800.00N/01600.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4125 MHz
[>] 07/06/2025 8:41:47 PM+00:00:
EA4GEM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4GEM-DP!4800.00N/01600.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4125 MHz
[>] 07/06/2025 8:10:52 PM+00:00:
EA4GEM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4GEM-DP!4800.00N/01600.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4125 MHz
[>] 07/06/2025 7:40:10 PM+00:00:
EA4GEM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4GEM-DP!4800.00N/01600.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4125 MHz
[>] 07/06/2025 7:08:56 PM+00:00:
EA4GEM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4GEM-DP!4800.00N/01600.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4125 MHz
[>] 07/06/2025 6:37:57 PM+00:00:
EA4GEM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4GEM-DP!4800.00N/01600.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4125 MHz
[>] 07/06/2025 6:07:14 PM+00:00:
EA4GEM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4GEM-DP!4800.00N/01600.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4125 MHz
[>] 07/06/2025 5:36:18 PM+00:00:
EA4GEM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4GEM-DP!4800.00N/01600.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4125 MHz
[>] 07/06/2025 5:05:23 PM+00:00:
EA4GEM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4GEM-DP!4800.00N/01600.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4125 MHz
[>] 07/06/2025 4:34:32 PM+00:00:
EA4GEM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4GEM-DP!4800.00N/01600.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4125 MHz
[>] 07/06/2025 4:03:43 PM+00:00:
EA4GEM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4GEM-DP!4800.00N/01600.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4125 MHz
[>] 07/06/2025 3:32:56 PM+00:00:
EA4GEM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4GEM-DP!4800.00N/01600.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4125 MHz
[>] 07/06/2025 3:01:59 PM+00:00:
EA4GEM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4GEM-DP!4800.00N/01600.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4125 MHz
[>] 07/06/2025 2:31:02 PM+00:00:
EA4GEM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4GEM-DP!4800.00N/01600.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4125 MHz
[>] 07/06/2025 2:00:23 PM+00:00:
EA4GEM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4GEM-DP!4800.00N/01600.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4125 MHz
[>] 07/06/2025 1:29:43 PM+00:00:
EA4GEM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4GEM-DP!4800.00N/01600.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4125 MHz
[>] 07/06/2025 12:58:59 PM+00:00:
EA4GEM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4GEM-DP!4800.00N/01600.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4125 MHz
[>] 07/06/2025 12:27:55 PM+00:00:
EA4GEM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4GEM-DP!4800.00N/01600.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4125 MHz
[>] 07/06/2025 11:57:12 AM+00:00:
EA4GEM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4GEM-DP!4800.00N/01600.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4125 MHz
[>] 07/06/2025 11:26:20 AM+00:00:
EA4GEM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4GEM-DP!4800.00N/01600.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4125 MHz
[>] 07/06/2025 10:55:42 AM+00:00:
EA4GEM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4GEM-DP!4800.00N/01600.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4125 MHz
[>] 07/06/2025 10:24:52 AM+00:00:
EA4GEM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4GEM-DP!4800.00N/01600.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4125 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.