A total of 100 recevied packets have been found for station/object DG3ACM-21 between 07/22/2025 4:09:17 PM+00:00 and 07/25/2025 4:09:17 PM+00:00.
Request took 0.015 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 100 packets.
[>] 07/25/2025 4:05:36 PM+00:00:
DG3ACM-21>APLG01,TCPIP*,qAC,T2SPAIN:=5133.54NL00918.92E&LoRa iGATE at DG3ACM/A QTH, contact via QRZ.com
[>] 07/25/2025 3:50:36 PM+00:00:
DG3ACM-21>APLG01,TCPIP*,qAC,T2SPAIN:=5133.54NL00918.92E&LoRa iGATE at DG3ACM/A QTH, contact via QRZ.com
[>] 07/25/2025 3:35:36 PM+00:00:
DG3ACM-21>APLG01,TCPIP*,qAC,T2SPAIN:=5133.54NL00918.92E&LoRa iGATE at DG3ACM/A QTH, contact via QRZ.com
[>] 07/25/2025 3:20:36 PM+00:00:
DG3ACM-21>APLG01,TCPIP*,qAC,T2SPAIN:=5133.54NL00918.92E&LoRa iGATE at DG3ACM/A QTH, contact via QRZ.com
[>] 07/25/2025 3:05:36 PM+00:00:
DG3ACM-21>APLG01,TCPIP*,qAC,T2SPAIN:=5133.54NL00918.92E&LoRa iGATE at DG3ACM/A QTH, contact via QRZ.com
[>] 07/25/2025 2:50:35 PM+00:00:
DG3ACM-21>APLG01,TCPIP*,qAC,T2SPAIN:=5133.54NL00918.92E&LoRa iGATE at DG3ACM/A QTH, contact via QRZ.com
[>] 07/25/2025 2:35:35 PM+00:00:
DG3ACM-21>APLG01,TCPIP*,qAC,T2SPAIN:=5133.54NL00918.92E&LoRa iGATE at DG3ACM/A QTH, contact via QRZ.com
[>] 07/25/2025 2:20:35 PM+00:00:
DG3ACM-21>APLG01,TCPIP*,qAC,T2SPAIN:=5133.54NL00918.92E&LoRa iGATE at DG3ACM/A QTH, contact via QRZ.com
[>] 07/25/2025 2:05:35 PM+00:00:
DG3ACM-21>APLG01,TCPIP*,qAC,T2SPAIN:=5133.54NL00918.92E&LoRa iGATE at DG3ACM/A QTH, contact via QRZ.com
[>] 07/25/2025 1:50:35 PM+00:00:
DG3ACM-21>APLG01,TCPIP*,qAC,T2SPAIN:=5133.54NL00918.92E&LoRa iGATE at DG3ACM/A QTH, contact via QRZ.com
[>] 07/25/2025 1:35:35 PM+00:00:
DG3ACM-21>APLG01,TCPIP*,qAC,T2SPAIN:=5133.54NL00918.92E&LoRa iGATE at DG3ACM/A QTH, contact via QRZ.com
[>] 07/25/2025 1:20:34 PM+00:00:
DG3ACM-21>APLG01,TCPIP*,qAC,T2SPAIN:=5133.54NL00918.92E&LoRa iGATE at DG3ACM/A QTH, contact via QRZ.com
[>] 07/25/2025 1:05:34 PM+00:00:
DG3ACM-21>APLG01,TCPIP*,qAC,T2SPAIN:=5133.54NL00918.92E&LoRa iGATE at DG3ACM/A QTH, contact via QRZ.com
[>] 07/25/2025 12:50:34 PM+00:00:
DG3ACM-21>APLG01,TCPIP*,qAC,T2SPAIN:=5133.54NL00918.92E&LoRa iGATE at DG3ACM/A QTH, contact via QRZ.com
[>] 07/25/2025 12:35:34 PM+00:00:
DG3ACM-21>APLG01,TCPIP*,qAC,T2SPAIN:=5133.54NL00918.92E&LoRa iGATE at DG3ACM/A QTH, contact via QRZ.com
[>] 07/25/2025 12:20:34 PM+00:00:
DG3ACM-21>APLG01,TCPIP*,qAC,T2SPAIN:=5133.54NL00918.92E&LoRa iGATE at DG3ACM/A QTH, contact via QRZ.com
[>] 07/25/2025 12:05:34 PM+00:00:
DG3ACM-21>APLG01,TCPIP*,qAC,T2SPAIN:=5133.54NL00918.92E&LoRa iGATE at DG3ACM/A QTH, contact via QRZ.com
[>] 07/25/2025 11:50:34 AM+00:00:
DG3ACM-21>APLG01,TCPIP*,qAC,T2SPAIN:=5133.54NL00918.92E&LoRa iGATE at DG3ACM/A QTH, contact via QRZ.com
[>] 07/25/2025 11:35:34 AM+00:00:
DG3ACM-21>APLG01,TCPIP*,qAC,T2SPAIN:=5133.54NL00918.92E&LoRa iGATE at DG3ACM/A QTH, contact via QRZ.com
[>] 07/25/2025 11:20:34 AM+00:00:
DG3ACM-21>APLG01,TCPIP*,qAC,T2SPAIN:=5133.54NL00918.92E&LoRa iGATE at DG3ACM/A QTH, contact via QRZ.com
[>] 07/25/2025 11:05:33 AM+00:00:
DG3ACM-21>APLG01,TCPIP*,qAC,T2SPAIN:=5133.54NL00918.92E&LoRa iGATE at DG3ACM/A QTH, contact via QRZ.com
[>] 07/25/2025 10:50:33 AM+00:00:
DG3ACM-21>APLG01,TCPIP*,qAC,T2SPAIN:=5133.54NL00918.92E&LoRa iGATE at DG3ACM/A QTH, contact via QRZ.com
[>] 07/25/2025 10:35:33 AM+00:00:
DG3ACM-21>APLG01,TCPIP*,qAC,T2SPAIN:=5133.54NL00918.92E&LoRa iGATE at DG3ACM/A QTH, contact via QRZ.com
[>] 07/25/2025 10:20:33 AM+00:00:
DG3ACM-21>APLG01,TCPIP*,qAC,T2SPAIN:=5133.54NL00918.92E&LoRa iGATE at DG3ACM/A QTH, contact via QRZ.com
[>] 07/25/2025 10:05:33 AM+00:00:
DG3ACM-21>APLG01,TCPIP*,qAC,T2SPAIN:=5133.54NL00918.92E&LoRa iGATE at DG3ACM/A QTH, contact via QRZ.com
* 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.