Channel
www.dmunlocker.com
@dmunlockerserver
On this record: Topic · Growth · Engagement · Cite this entry
2,746subscribers
+138 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002559181449 |
|---|---|
| Type | Channel |
| Username | @dmunlockerserver |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 September 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/dmunlockerserver |
Topic
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 15 September 2026 and assigned it the closest of 31 fixed categories, at 69% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Oct 2026, 16:37 | 2,746 | +2 |
| 5 Oct 2026, 18:59 | 2,744 | +10 |
| 28 Sept 2026, 06:36 | 2,734 | +25 |
| 15 Sept 2026, 20:38 | 2,709 | +7 |
| 14 Sept 2026, 00:02 | 2,702 | no change |
| 12 Sept 2026, 12:41 | 2,702 | +6 |
| 8 Sept 2026, 06:41 | 2,696 | +16 |
| 2 Sept 2026, 23:53 | 2,680 | +8 |
| 30 Aug 2026, 18:13 | 2,672 | +9 |
| 27 Aug 2026, 09:55 | 2,663 | +7 |
| 24 Aug 2026, 18:38 | 2,656 | +14 |
| 20 Aug 2026, 16:34 | 2,642 | +13 |
| 17 Aug 2026, 18:38 | 2,629 | +10 |
| 14 Aug 2026, 13:33 | 2,619 | +5 |
| 11 Aug 2026, 14:12 | 2,614 | +5 |
| 8 Aug 2026, 03:26 | 2,609 | +1 |
| 7 Aug 2026, 20:55 | 2,608 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 12 October 2026 — this entry's latest reading, not the date you are reading this.
“www.dmunlocker.com” (@dmunlockerserver), 2,746 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/dmunlockerserver.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.