DMR Network Monitor
Date/Time (Local) | Source ID | Callsign | Name | Slot | Destination | Via Repeater | Repeater QTH | Duration |
---|---|---|---|---|---|---|---|---|
28.04.2024 11:42:14 | 2352926 | M3YGQ | Martin | 2 | 840 | 1 | ||
27.04.2024 22:54:40 | 2352926 | M3YGQ | Martin | 2 | 840 | 0 | ||
21.04.2024 20:06:26 | 2352926 | M3YGQ | Martin | 1 | 23526 | 2 | ||
21.04.2024 18:19:25 | 2352926 | M3YGQ | Martin | 1 | 23526 | 2 | ||
21.04.2024 16:39:37 | 2352926 | M3YGQ | Martin | 1 | 23526 | 2 | ||
21.04.2024 15:29:27 | 2352926 | M3YGQ | Martin | 1 | 23526 | 0 | ||
21.04.2024 14:10:15 | 2352926 | M3YGQ | Martin | 1 | 23526 | 2 | ||
21.04.2024 14:10:11 | 2352926 | M3YGQ | Martin | 1 | 23526 | 0 | ||
21.04.2024 13:16:13 | 2352926 | M3YGQ | Martin | 1 | 23526 | 2 | ||
21.04.2024 13:15:10 | 2352926 | M3YGQ | Martin | 1 | 23526 | 0 | ||
21.04.2024 09:17:34 | 2352926 | M3YGQ | Martin | 1 | 23526 | 1 | ||
20.04.2024 23:35:26 | 2352926 | M3YGQ | Martin | 1 | 23526 | 0 | ||
20.04.2024 22:34:46 | 2352926 | M3YGQ | Martin | 1 | 23526 | 0 | ||
20.04.2024 22:34:00 | 2352926 | M3YGQ | Martin | 1 | 23526 | 2 | ||
20.04.2024 22:32:22 | 2352926 | M3YGQ | Martin | 1 | 23526 | 0 | ||
20.04.2024 22:32:21 | 2352926 | M3YGQ | Martin | 1 | 23526 | 0 | ||
20.04.2024 22:32:14 | 2352926 | M3YGQ | Martin | 1 | 23526 | 0 | ||
20.04.2024 22:04:11 | 2352926 | M3YGQ | Martin | 1 | 23526 | 0 | ||
20.04.2024 22:04:04 | 2352926 | M3YGQ | Martin | 1 | 23526 | 0 | ||
20.04.2024 21:57:22 | 2352926 | M3YGQ | Martin | 1 | 23526 | 0 | ||
20.04.2024 20:06:12 | 2352926 | M3YGQ | Martin | 1 | 23526 | 0 | ||
20.04.2024 18:41:03 | 2352926 | M3YGQ | Martin | 1 | 23526 | 2 | ||
20.04.2024 18:40:17 | 2352926 | M3YGQ | Martin | 1 | 23526 | 0 | ||
20.04.2024 18:39:40 | 2352926 | M3YGQ | Martin | 2 | 9 | 0 | ||
04.04.2024 17:31:12 | 2352926 | M3YGQ | Martin | 2 | 9 | 3 |
Data can be delayed using Netmon, if you want real-time network information use Last Heard
Netmon is a legacy system, issues and errors are to be expected