Telegram RegisterThe public register of Telegram
Telegram profile photo for Дмитрий Нагиев

Channel

Дмитрий Нагиев

@mr_dnagiev

Verified by Telegram

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cross-platform identity · Cite this entry

15,812subscribers

+119 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002164691609
TypeChannel
Username@mr_dnagiev
Created19 December 2024 — measured — dated from the channel’s first post
First recorded6 August 2026
Last confirmed live30 October 2026
Measurements held49
Confirmed unchanged1 time, most recently 30 October 2026
On Telegramt.me/mr_dnagiev

Topic

Memes & entertainment — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 47% 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 the other topics.

Growth

15,67815,83515,756.56 August 2026 — 15,693 subscribers6 August 2026 — 15,697 subscribers7 August 2026 — 15,693 subscribers9 August 2026 — 15,686 subscribers10 August 2026 — 15,689 subscribers12 August 2026 — 15,682 subscribers13 August 2026 — 15,678 subscribers15 August 2026 — 15,701 subscribers16 August 2026 — 15,713 subscribers17 August 2026 — 15,725 subscribers18 August 2026 — 15,734 subscribers20 August 2026 — 15,744 subscribers21 August 2026 — 15,752 subscribers22 August 2026 — 15,754 subscribers24 August 2026 — 15,762 subscribers25 August 2026 — 15,754 subscribers26 August 2026 — 15,750 subscribers27 August 2026 — 15,744 subscribers28 August 2026 — 15,741 subscribers29 August 2026 — 15,738 subscribers30 August 2026 — 15,728 subscribers31 August 2026 — 15,727 subscribers1 September 2026 — 15,722 subscribers2 September 2026 — 15,723 subscribers3 September 2026 — 15,729 subscribers5 September 2026 — 15,739 subscribers8 September 2026 — 15,767 subscribers11 September 2026 — 15,809 subscribers13 September 2026 — 15,821 subscribers16 September 2026 — 15,817 subscribers18 September 2026 — 15,835 subscribers1 October 2026 — 15,799 subscribers6 October 2026 — 15,798 subscribers10 October 2026 — 15,807 subscribers13 October 2026 — 15,820 subscribers15 October 2026 — 15,822 subscribers16 October 2026 — 15,826 subscribers17 October 2026 — 15,830 subscribers18 October 2026 — 15,831 subscribers19 October 2026 — 15,828 subscribers21 October 2026 — 15,829 subscribers22 October 2026 — 15,826 subscribers23 October 2026 — 15,819 subscribers24 October 2026 — 15,815 subscribers25 October 2026 — 15,816 subscribers26 October 2026 — 15,813 subscribers27 October 2026 — 15,809 subscribers28 October 2026 — 15,816 subscribers30 October 2026 — 15,812 subscribers15,8126 August 202630 October 2026
49 measurements spanning 85 days, net +119. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 15,654–15,859 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 49
Measured (UTC)SubscribersChange
30 Oct 2026, 08:3715,812-4
28 Oct 2026, 07:5615,816+7
27 Oct 2026, 06:5815,809-4
26 Oct 2026, 06:4915,813-3
25 Oct 2026, 09:3615,816+1
24 Oct 2026, 09:2815,815-4
23 Oct 2026, 11:2515,819-7
22 Oct 2026, 10:0515,826-3
21 Oct 2026, 00:2815,829+1
19 Oct 2026, 03:3715,828-3
18 Oct 2026, 04:3615,831+1
17 Oct 2026, 02:3815,830+4
16 Oct 2026, 05:5715,826+4
15 Oct 2026, 03:1615,822+2
13 Oct 2026, 23:3015,820+13
10 Oct 2026, 18:3715,807+9
6 Oct 2026, 17:3915,798-1
1 Oct 2026, 21:0215,799-36
18 Sept 2026, 14:1715,835+18
16 Sept 2026, 08:2115,817first reading

Engagement

7 posts held, back to 19 December 2024 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 54 pages of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 7 posts for this entry, the most recent from 6 September 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 56s
Average length
39s

Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Recent posts

6 Sept 2025, 08:48 UTC≈90,600 viewsread 3 September 2026

Мечты сбываются. Моя мечта - деградация. Поэтому подписываюсь на канал Кирилла. Ну и что, что морально неустойчив, зато аморально стабилен. Удиви нас сынок, как кыштымский карлик Алёшенька. t.me/kirillnagiev

3 Mar 2025, 12:46 UTC≈166,000 viewsread 3 September 2026
Video

Вечно молодой, вечно потный.

Showing the 7 most recent of 7 posts we hold for @mr_dnagiev. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

Names

Channels on the register whose handles appear in this channel's posts.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cross-platform identity — Wikidata

A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.

Q3033167 on Wikidata, read 25 October 2026
LabelDmitriy Nagiev
DescriptionRussian actor, entertainer, TV and radio presenter

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 30 October 2026 — this entry's latest reading, not the date you are reading this.

“Дмитрий Нагиев” (@mr_dnagiev), 15,812 subscribers as measured 30 October 2026. Telegram Register, tgregister.com/channel/mr_dnagiev.

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.