A total of 549 recevied packets have been found for station/object EA3EIZ-DP between 06/03/2025 3:11:53 PM+00:00 and 06/06/2025 3:11:53 PM+00:00.
Request took 0.034 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 549 packets.
[>] 06/06/2025 3:05:35 PM+00:00:
EA3EIZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EIZ-DP!4131.84N/00211.13ErRNG0034 IPSC2-EA-Hotspot MMDVM 434.4000 MHz
[>] 06/06/2025 2:58:57 PM+00:00:
EA3EIZ>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3EIZ-DP!4131.84N/00211.13ErRNG0034 IPSC2-EA4Master MMDVM 431.2000 MHz
[>] 06/06/2025 2:58:57 PM+00:00:
EA3EIZ>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3EIZ-DP!4131.84N/00211.13ErRNG0034 IPSC2-EA4Master MMDVM 435.0000 MHz
[>] 06/06/2025 2:58:57 PM+00:00:
EA3EIZ>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3EIZ-DP!4131.84N/00211.13ErRNG0034 IPSC2-EA4Master MMDVM 436.0000 MHz
[>] 06/06/2025 2:58:57 PM+00:00:
EA3EIZ>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3EIZ-DP!4131.84N/00211.13ErRNG0034 IPSC2-EA4Master MMDVM 434.1000 MHz
[>] 06/06/2025 2:28:21 PM+00:00:
EA3EIZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EIZ-DP!4131.84N/00211.13ErRNG0034 IPSC2-EA4Master MMDVM 436.0000 MHz
[>] 06/06/2025 2:28:21 PM+00:00:
EA3EIZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EIZ-DP!4131.84N/00211.13ErRNG0034 IPSC2-EA4Master MMDVM 435.0000 MHz
[>] 06/06/2025 2:28:21 PM+00:00:
EA3EIZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EIZ-DP!4131.84N/00211.13ErRNG0034 IPSC2-EA4Master MMDVM 434.1000 MHz
[>] 06/06/2025 1:57:31 PM+00:00:
EA3EIZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EIZ-DP!4131.84N/00211.13ErRNG0034 IPSC2-EA4Master MMDVM 435.0000 MHz
[>] 06/06/2025 1:57:31 PM+00:00:
EA3EIZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EIZ-DP!4131.84N/00211.13ErRNG0034 IPSC2-EA4Master MMDVM 434.1000 MHz
[>] 06/06/2025 1:26:50 PM+00:00:
EA3EIZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EIZ-DP!4131.84N/00211.13ErRNG0034 IPSC2-EA4Master MMDVM 435.0000 MHz
[>] 06/06/2025 1:26:50 PM+00:00:
EA3EIZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EIZ-DP!4131.84N/00211.13ErRNG0034 IPSC2-EA4Master MMDVM 434.1000 MHz
[>] 06/06/2025 12:55:58 PM+00:00:
EA3EIZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EIZ-DP!4131.84N/00211.13ErRNG0034 IPSC2-EA4Master MMDVM 435.0000 MHz
[>] 06/06/2025 12:55:58 PM+00:00:
EA3EIZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EIZ-DP!4131.84N/00211.13ErRNG0034 IPSC2-EA4Master MMDVM 434.1000 MHz
[>] 06/06/2025 12:25:14 PM+00:00:
EA3EIZ>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3EIZ-DP!4131.84N/00211.13ErRNG0034 IPSC2-EA4Master MMDVM 435.0000 MHz
[>] 06/06/2025 12:25:14 PM+00:00:
EA3EIZ>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3EIZ-DP!4131.84N/00211.13ErRNG0034 IPSC2-EA4Master MMDVM 434.1000 MHz
[>] 06/06/2025 11:54:24 AM+00:00:
EA3EIZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EIZ-DP!4131.84N/00211.13ErRNG0034 IPSC2-EA4Master MMDVM 435.0000 MHz
[>] 06/06/2025 11:54:24 AM+00:00:
EA3EIZ>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3EIZ-DP!4131.84N/00211.13ErRNG0034 IPSC2-EA4Master MMDVM 434.1000 MHz
[>] 06/06/2025 11:23:37 AM+00:00:
EA3EIZ>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3EIZ-DP!4131.84N/00211.13ErRNG0034 IPSC2-EA4Master MMDVM 435.0000 MHz
[>] 06/06/2025 11:23:36 AM+00:00:
EA3EIZ>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3EIZ-DP!4131.84N/00211.13ErRNG0034 IPSC2-EA4Master MMDVM 434.1000 MHz
[>] 06/06/2025 10:52:40 AM+00:00:
EA3EIZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EIZ-DP!4131.84N/00211.13ErRNG0034 IPSC2-EA4Master MMDVM 435.0000 MHz
[>] 06/06/2025 10:52:40 AM+00:00:
EA3EIZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EIZ-DP!4131.84N/00211.13ErRNG0034 IPSC2-EA4Master MMDVM 434.1000 MHz
[>] 06/06/2025 10:21:55 AM+00:00:
EA3EIZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EIZ-DP!4131.84N/00211.13ErRNG0034 IPSC2-EA4Master MMDVM 435.0000 MHz
[>] 06/06/2025 10:21:55 AM+00:00:
EA3EIZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EIZ-DP!4131.84N/00211.13ErRNG0034 IPSC2-EA4Master MMDVM 434.1000 MHz
[>] 06/06/2025 9:51:21 AM+00:00:
EA3EIZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EIZ-DP!4131.84N/00211.13ErRNG0034 IPSC2-EA4Master MMDVM 435.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.