A total of 46 recevied packets have been found for station/object M1BZM-DP between 07/22/2025 11:56:55 AM+00:00 and 07/25/2025 11:56:55 AM+00:00.
Request took 0.008 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 46 packets.
[>] 07/25/2025 11:42:19 AM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 07/25/2025 11:10:26 AM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 07/25/2025 10:38:14 AM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 07/25/2025 10:06:20 AM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 07/25/2025 9:33:49 AM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 07/25/2025 9:01:36 AM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 07/25/2025 8:29:43 AM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 07/25/2025 7:57:52 AM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 07/25/2025 7:26:02 AM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 07/25/2025 6:53:36 AM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 07/25/2025 6:21:46 AM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 07/25/2025 5:49:40 AM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 07/25/2025 5:17:37 AM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 07/24/2025 11:27:48 PM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 07/24/2025 10:56:00 PM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 07/24/2025 10:23:52 PM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 07/24/2025 9:52:01 PM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 07/24/2025 9:19:34 PM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 07/23/2025 11:28:50 PM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 07/23/2025 10:57:02 PM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 07/23/2025 10:25:12 PM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 07/23/2025 9:53:03 PM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 07/23/2025 9:21:10 PM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 07/23/2025 8:49:35 PM+00:00:
M1BZM>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5731.99N/01225.68WrRNG0034 IPSC2-DVSPh-F MMDVM 432.3000 MHz
[>] 07/22/2025 11:29:49 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.
Snapshot Active 
Filter Active 
Map Wizard Active 
Please wait while the map is redrawn...