A total of 49 recevied packets have been found for station/object M1BZM-DP between 06/16/2025 2:09:50 AM+00:00 and 06/19/2025 2:09:50 AM+00:00.
Request took 0.003 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 49 packets.
[>] 06/19/2025 1:57:33 AM+00:00:
M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 06/19/2025 1:25:24 AM+00:00:
M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 06/19/2025 12:52:57 AM+00:00:
M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 06/19/2025 12:20:30 AM+00:00:
M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 06/18/2025 11:47:44 PM+00:00:
M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 06/18/2025 11:15:51 PM+00:00:
M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 06/18/2025 10:43:38 PM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 06/18/2025 10:11:43 PM+00:00:
M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 06/18/2025 9:39:29 PM+00:00:
M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 06/18/2025 9:07:12 PM+00:00:
M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 06/18/2025 8:34:52 PM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 06/18/2025 8:02:13 PM+00:00:
M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 06/18/2025 7:30:26 PM+00:00:
M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 06/18/2025 6:58:37 PM+00:00:
M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 06/18/2025 6:26:51 PM+00:00:
M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 06/18/2025 5:54:28 PM+00:00:
M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 06/18/2025 5:22:25 PM+00:00:
M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 06/18/2025 4:50:39 PM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 06/18/2025 4:18:53 PM+00:00:
M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 06/18/2025 3:47:05 PM+00:00:
M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 06/18/2025 3:15:17 PM+00:00:
M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 06/18/2025 2:43:31 PM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 06/18/2025 2:11:44 PM+00:00:
M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 06/18/2025 1:39:57 PM+00:00:
M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 06/18/2025 1:08:09 PM+00:00:
M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 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.