A total of 101 recevied packets have been found for station/object M1BZM-DP between 08/26/2025 5:31:37 AM+00:00 and 08/29/2025 5:31:37 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 101 packets.
[>] 08/29/2025 5:25:38 AM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 08/29/2025 4:53:40 AM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 08/29/2025 4:21:41 AM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 08/29/2025 3:49:55 AM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 08/29/2025 3:18:23 AM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 08/29/2025 2:46:50 AM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 08/29/2025 2:15:15 AM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 08/29/2025 1:43:30 AM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 08/29/2025 1:12:00 AM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 08/29/2025 12:40:04 AM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 08/29/2025 12:08:20 AM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 08/28/2025 11:36:09 PM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 08/28/2025 11:04:23 PM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 08/28/2025 10:32:23 PM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 08/28/2025 10:00:38 PM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 08/28/2025 9:28:51 PM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 08/28/2025 8:56:35 PM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 08/28/2025 8:24:44 PM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 08/28/2025 7:52:51 PM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 08/28/2025 7:20:54 PM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 08/28/2025 6:49:08 PM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 08/28/2025 6:17:22 PM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 08/28/2025 5:45:36 PM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 08/28/2025 5:13:39 PM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 08/28/2025 4:41:32 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.