Telegram RegisterThe public register of Telegram
Telegram profile photo for андрей мир

Channel

андрей мир

@dotapruf228

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

85subscribers

-1 since we began measuring on 9 August 2026

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

Register entry

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

Growth

858685.59 Aug 2026, 14:15 — 86 subscribers9 Aug 2026, 16:15 — 86 subscribers10 Aug 2026, 10:41 — 85 subscribers9 Aug 2026, 14:1510 Aug 2026, 10:41
3 measurements taken within a single day, net -1. 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 85–86 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 10:4185-1
9 Aug 2026, 16:1586no change
9 Aug 2026, 14:1586first reading

Engagement

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

What this channel posts

Video runtime
4m 57s
Average length
42s

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

57 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 63.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53302642020135821463663.2%
custom 53300666034531944202136.8%

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 6 of the 16 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 57 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 24 April 2026 to 2 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

2 Aug 2026, 15:59 UTC70 views16 reactionsread 9 August 2026
Photo

Подмутился

custom 533006660345319442014custom 53302642020135821462

24 Jul 2026, 15:51 UTC159 views7 reactionsread 9 August 2026

главный спонсор этого канала - Билайн Фото-локально в лауде

custom 53302642020135821467

4 Jul 2026, 17:02 UTC218 views8 reactionsread 9 August 2026

меня ксюша попросила добавить хотя бы одну реакцию... короче теперь есть лайки

custom 53302642020135821468

4 Jul 2026, 17:00 UTC298 views23 reactionsread 9 August 2026
Video

"Это рассказ о парне, который упал с небоскреба. Падая вниз, этаж за этажом он повторяет снова и снова, чтобы подбодрить себя: "Пока все в порядке... пока все в порядке..." Но важно не само падение. Куда важнее, как ты приземлишься"

custom 533026420201358214618custom 53300666034531944205

28 Jun 2026, 19:11 UTC318 viewsread 9 August 2026
Photo

Йоу, я в данный момент нахожусь в будке, блять, и записываю рэп и, возможно, этот разговор тоже записывается

2 Jun 2026, 10:32 UTC346 views1 reactionsread 9 August 2026
Video

Не люблю делать рилсы, чисто с отсылкой. поработал. Щас медиа шатает по полной. Если раньше можно было вытащить пул через тт/тг и нативной афишей, то сейчас дело обстоит не только в юр. поле площадки, но ещё и в самой форме и цикле её распострания. По идее самым выигрыающим действием будет performance (осмысленный) с добавлением классического маркетинга... а если его ещё закинуть в на федеральные СМИ - коллапс буде

custom 53302642020135821461

29 May 2026, 14:36 UTC310 viewsread 9 August 2026
Photo

Да, ниче, работаю. Идей пока нет

6 May 2026, 18:04 UTC351 viewsread 9 August 2026
Photo

а вообще меня официально нет в культуре. пиздец жду июнь, ибо там точно скажут на счёт поступления и в целом про портфолио

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

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

“андрей мир” (@dotapruf228), 85 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/dotapruf228.

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.