Telegram RegisterThe public register of Telegram
Telegram profile photo for dianluvsvx

Channel

dianluvsvx

@dianluvsv

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

294subscribers

-2 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001716962032
TypeChannel
Username@dianluvsv
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live9 October 2026
Measurements held7
Confirmed unchanged1 time, most recently 9 October 2026
On Telegramt.me/dianluvsv

Topic

Other / unclassifiable — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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

2882962927 August 2026 — 296 subscribers8 August 2026 — 296 subscribers14 August 2026 — 294 subscribers28 August 2026 — 288 subscribers6 September 2026 — 293 subscribers28 September 2026 — 296 subscribers9 October 2026 — 294 subscribers2947 August 20269 October 2026
7 measurements spanning 63 days, net -2. 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 287–297 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Oct 2026, 09:36294-2
28 Sept 2026, 01:57296+3
6 Sept 2026, 08:02293+5
28 Aug 2026, 10:28288-6
14 Aug 2026, 23:56294-2
8 Aug 2026, 08:05296no change
7 Aug 2026, 18:19296first reading

Engagement

11 posts held, back to 21 June 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 11 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 00s
Average length
12s

Measured directly from 5 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.

Reaction mix

257 reactions across 11 posts, in 5 distinct kinds. The most used accounts for 28.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52604603963592196637428.8%
custom 53643467131275451256424.9%
custom 52716643640116745445019.5%
custom 52715527421066124634417.1%
custom 5305711433055495160259.73%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 11 of the 11 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 257 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 11 most recent posts we hold, published 21 June 2026 to 5 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

5 Aug 2026, 21:55 UTC183 views23 reactionsread 8 August 2026
Photo

Photo, posted without a caption

custom 536434671312754512511custom 52604603963592196636custom 52716643640116745446

1 Aug 2026, 11:25 UTC385 views31 reactionsread 8 August 2026
Photo

💋

custom 527155274210661246313custom 52604603963592196639custom 52716643640116745449

30 Jul 2026, 12:21 UTC393 views24 reactionsread 8 August 2026
Photo

Photo, posted without a caption

custom 526046039635921966310custom 52715527421066124637custom 53643467131275451257

26 Jul 2026, 22:49 UTC462 views29 reactionsread 8 August 2026
Video

😊😊😊

custom 536434671312754512511custom 526046039635921966310custom 53057114330554951608

16 Jul 2026, 23:28 UTC611 views33 reactionsread 8 August 2026
Video

🤩

custom 527166436401167454414custom 526046039635921966310custom 53643467131275451257custom 52715527421066124632

16 Jul 2026, 23:17 UTC426 views20 reactionsread 8 August 2026
Video message

Video message, posted without a caption

custom 53057114330554951606custom 52604603963592196635custom 53643467131275451255custom 52715527421066124634

6 Jul 2026, 22:23 UTC644 views25 reactionsread 8 August 2026
Photo

#жесткийворк

custom 527166436401167454410custom 52604603963592196637custom 52715527421066124637custom 53057114330554951601

6 Jul 2026, 05:28 UTC557 views16 reactionsread 8 August 2026
Photo

Photo, posted without a caption

custom 52604603963592196636custom 52715527421066124635custom 52716643640116745445

29 Jun 2026, 18:38 UTC706 views25 reactionsread 8 August 2026
Photo

Photo, posted without a caption

custom 530571143305549516010custom 53643467131275451257custom 52716643640116745446custom 52604603963592196632

27 Jun 2026, 21:55 UTC583 views23 reactionsread 8 August 2026
Video

Video, posted without a caption

custom 52604603963592196639custom 53643467131275451258custom 52715527421066124636

Showing the 11 most recent of 11 posts we hold for @dianluvsv. 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.

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

“dianluvsvx” (@dianluvsv), 294 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/dianluvsv.

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.