A total of 141 recevied packets have been found for station/object EA4PS-DP between 06/02/2025 11:24:38 AM+00:00 and 06/05/2025 11:24:38 AM+00:00.
Request took 0.006 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 141 packets.
[>] 06/05/2025 11:17:44 AM+00:00:
EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/00349.31WrRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
[>] 06/05/2025 10:47:04 AM+00:00:
EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/00349.31WrRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
[>] 06/05/2025 10:16:23 AM+00:00:
EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/00349.31WrRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
[>] 06/05/2025 9:45:41 AM+00:00:
EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/00349.31WrRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
[>] 06/05/2025 9:14:59 AM+00:00:
EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/00349.31WrRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
[>] 06/05/2025 8:44:12 AM+00:00:
EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/00349.31WrRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
[>] 06/05/2025 8:13:33 AM+00:00:
EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/00349.31WrRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
[>] 06/05/2025 7:42:42 AM+00:00:
EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/00349.31WrRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
[>] 06/05/2025 7:11:41 AM+00:00:
EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/00349.31WrRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
[>] 06/05/2025 6:41:06 AM+00:00:
EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/00349.31WrRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
[>] 06/05/2025 6:10:27 AM+00:00:
EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/00349.31WrRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
[>] 06/05/2025 5:39:48 AM+00:00:
EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/00349.31WrRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
[>] 06/05/2025 5:09:00 AM+00:00:
EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/00349.31WrRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
[>] 06/05/2025 4:38:29 AM+00:00:
EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/00349.31WrRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
[>] 06/05/2025 4:07:57 AM+00:00:
EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/00349.31WrRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
[>] 06/05/2025 3:37:16 AM+00:00:
EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/00349.31WrRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
[>] 06/05/2025 3:06:45 AM+00:00:
EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/00349.31WrRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
[>] 06/05/2025 2:35:40 AM+00:00:
EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/00349.31WrRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
[>] 06/05/2025 2:04:55 AM+00:00:
EA4PS>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/00349.31WrRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
[>] 06/05/2025 1:34:00 AM+00:00:
EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/00349.31WrRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
[>] 06/05/2025 1:03:13 AM+00:00:
EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/00349.31WrRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
[>] 06/05/2025 12:32:34 AM+00:00:
EA4PS>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/00349.31WrRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
[>] 06/05/2025 12:01:48 AM+00:00:
EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/00349.31WrRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
[>] 06/04/2025 11:31:09 PM+00:00:
EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/00349.31WrRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
[>] 06/04/2025 11:00:36 PM+00:00:
EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/00349.31WrRNG0034 IPSC2-EA4Master MMDVM 435.1250 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.