A total of 135 recevied packets have been found for station/object 2M0BGK-DP between 06/01/2025 8:09:40 AM+00:00 and 06/04/2025 8:09:40 AM+00:00.
Request took 0.012 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 135 packets.
[>] 06/04/2025 8:03:46 AM+00:00:
2M0BGK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)2M0BGK-DP!5612.81N/00311.38WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
[>] 06/04/2025 7:31:45 AM+00:00:
2M0BGK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)2M0BGK-DP!5612.81N/00311.38WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
[>] 06/04/2025 6:59:46 AM+00:00:
2M0BGK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)2M0BGK-DP!5612.81N/00311.38WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
[>] 06/04/2025 6:28:04 AM+00:00:
2M0BGK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)2M0BGK-DP!5612.81N/00311.38WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
[>] 06/04/2025 5:56:25 AM+00:00:
2M0BGK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)2M0BGK-DP!5612.81N/00311.38WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
[>] 06/04/2025 5:24:30 AM+00:00:
2M0BGK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)2M0BGK-DP!5612.81N/00311.38WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
[>] 06/04/2025 4:52:53 AM+00:00:
2M0BGK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)2M0BGK-DP!5612.81N/00311.38WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
[>] 06/04/2025 4:21:16 AM+00:00:
2M0BGK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)2M0BGK-DP!5612.81N/00311.38WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
[>] 06/04/2025 3:49:21 AM+00:00:
2M0BGK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)2M0BGK-DP!5612.81N/00311.38WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
[>] 06/04/2025 3:17:42 AM+00:00:
2M0BGK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)2M0BGK-DP!5612.81N/00311.38WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
[>] 06/04/2025 2:46:01 AM+00:00:
2M0BGK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)2M0BGK-DP!5612.81N/00311.38WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
[>] 06/04/2025 2:14:20 AM+00:00:
2M0BGK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)2M0BGK-DP!5612.81N/00311.38WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
[>] 06/04/2025 1:42:38 AM+00:00:
2M0BGK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)2M0BGK-DP!5612.81N/00311.38WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
[>] 06/04/2025 1:10:22 AM+00:00:
2M0BGK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)2M0BGK-DP!5612.81N/00311.38WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
[>] 06/04/2025 12:38:41 AM+00:00:
2M0BGK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)2M0BGK-DP!5612.81N/00311.38WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
[>] 06/04/2025 12:06:42 AM+00:00:
2M0BGK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)2M0BGK-DP!5612.81N/00311.38WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
[>] 06/03/2025 11:35:00 PM+00:00:
2M0BGK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)2M0BGK-DP!5612.81N/00311.38WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
[>] 06/03/2025 11:03:19 PM+00:00:
2M0BGK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)2M0BGK-DP!5612.81N/00311.38WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
[>] 06/03/2025 10:31:00 PM+00:00:
2M0BGK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)2M0BGK-DP!5612.81N/00311.38WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
[>] 06/03/2025 9:59:17 PM+00:00:
2M0BGK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)2M0BGK-DP!5612.81N/00311.38WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
[>] 06/03/2025 9:27:33 PM+00:00:
2M0BGK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)2M0BGK-DP!5612.81N/00311.38WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
[>] 06/03/2025 8:55:10 PM+00:00:
2M0BGK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)2M0BGK-DP!5612.81N/00311.38WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
[>] 06/03/2025 8:23:03 PM+00:00:
2M0BGK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)2M0BGK-DP!5612.81N/00311.38WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
[>] 06/03/2025 7:51:10 PM+00:00:
2M0BGK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)2M0BGK-DP!5612.81N/00311.38WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
[>] 06/03/2025 7:18:58 PM+00:00:
2M0BGK>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)2M0BGK-DP!5612.81N/00311.38WrRNG0034 IPSC2-DVSPh-F 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.