Telegram RegisterThe public register of Telegram
Telegram profile photo for ванёк дрозд

Channel

ванёк дрозд

@itzdrozd

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

57subscribers

+2 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1001693100250
TypeChannel
Username@itzdrozd
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live31 August 2026
Measurements held3
Confirmed unchanged3 times, most recently 31 August 2026
On Telegramt.me/itzdrozd

Growth

5557568 August 2026 — 55 subscribers10 August 2026 — 55 subscribers17 August 2026 — 57 subscribers8 August 202617 August 2026
3 measurements spanning 9 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 55–57 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 18:0357+2
10 Aug 2026, 08:1655no change
8 Aug 2026, 20:3255first reading

Engagement

20 posts held, back to 16 July 2026the 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 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

125 reactions across 19 posts, in 11 distinct kinds. The most used accounts for 43.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52223251712846224615443.2%
custom 52201992483724474733528.0%
😢86.40%
custom 546070446332707455764.80%
custom 521993389670296966954.00%
👍54.00%
👏54.00%
custom 523554542421908797232.40%
🤡21.60%
🔥10.8%
🫡10.8%

Custom emoji. 5 of the rows above are 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 19 of the 20 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 125 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 16 July 2026 to 6 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

6 Aug 2026, 21:14 UTC18 views2 reactionsread 10 August 2026
Forwarded from @xekuroPhoto

xekuro - #nocore prod/mix - я feat ЛИИН и спалвчера (тож я) cover - я и moiiik слушать ТУТ текст (СКОРО)

custom 52223251712846224612

4 Aug 2026, 14:15 UTC40 views4 reactionsread 10 August 2026
Photo

я съел 12 хинкалей и чуть не умер это рекорд

custom 52201992483724474734

3 Aug 2026, 20:00 UTC44 views4 reactionsread 10 August 2026

здарова заебал

custom 52223251712846224614

3 Aug 2026, 16:56 UTC45 views10 reactionsread 10 August 2026

как же пиздато было без ВПН, прокси, запретов и блокировок аж дышалось свободнее

custom 522232517128462246110

3 Aug 2026, 16:50 UTC43 views7 reactionsread 10 August 2026

о нет, меня засосала россия(((

😢7

2 Aug 2026, 20:00 UTC46 views7 reactionsread 10 August 2026

как же охуенно устроить детокс от соцсетей

👍5🔥1😢1

2 Aug 2026, 19:53 UTC46 views12 reactionsread 10 August 2026
Photo

ALGA KAZAKHSTAN

custom 522232517128462246112

31 Jul 2026, 15:05 UTC62 views6 reactionsread 10 August 2026
Photo

haha goodbye Russia

custom 54607044633270745576

31 Jul 2026, 09:23 UTC62 views6 reactionsread 10 August 2026
Photo

съебываю из рашки 🥳

custom 52201992483724474736

30 Jul 2026, 22:20 UTC54 views6 reactionsread 10 August 2026
Photo

Я ждал возвращения этого вкуса 13 лет....... Лучший вкус Лэйс

custom 52223251712846224616

28 Jul 2026, 17:16 UTC51 views8 reactionsread 10 August 2026
Photo

порез на собаке самый скучный и унылый концерт, на котором я был

custom 52199338967029696695custom 52355454242190879723

25 Jul 2026, 19:09 UTC74 views10 reactionsread 10 August 2026
Photo

ННННННННЕЕЕЕЕЕЕЕЕЕЕЕЕЕЕЕЕЕЕЕЕЕТТТТТТТТТТТТТ

custom 52201992483724474739🫡1

Showing the 12 most recent of 20 posts we hold for @itzdrozd. 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.

Forward network

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 4 registered channels — 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.

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.

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

“ванёк дрозд” (@itzdrozd), 57 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/itzdrozd.

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.