Telegram RegisterThe public register of Telegram
Telegram profile photo for PESTRYAK | Дмитрий Пестряков

Channel

PESTRYAK | Дмитрий Пестряков

@pestryak71

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

246subscribers

-5 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-1003696249424
TypeChannel
Username@pestryak71
CreatedBetween 1 December 2025 and 30 April 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/pestryak71

Growth

246251248.57 August 2026 — 251 subscribers8 August 2026 — 251 subscribers8 August 2026 — 250 subscribers15 August 2026 — 246 subscribers7 August 202615 August 2026
4 measurements spanning 8 days, net -5. 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 245–252 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 15:26246-4
8 Aug 2026, 11:39250-1
8 Aug 2026, 09:31251no change
7 Aug 2026, 19:09251first reading

Engagement

8 posts held, back to 28 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
46.5%
avg views ÷ 246 subscribers
Avg views / post
115
8 posts measured
Reaction rate
20.6%
reactions ÷ views · ER floor
Posts in window
8
of 8 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 August 2026
Posts held8 (28 July 20268 August 2026)
Views total916
Reactions total189
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 09:31 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

189 reactions across 8 posts, in 16 distinct kinds. The most used accounts for 21.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4021.2%
custom 54113805993383285483116.4%
custom 53821191503594527783015.9%
custom 5409359336189240910168.47%
🔥168.47%
custom 5262779386641290539157.94%
custom 542009303069259291284.23%
custom 537982030347400584863.17%
🎉63.17%
custom 540673045542683740252.65%
custom 538193923417942019542.12%
🙏42.12%
custom 540708335141470940331.59%
😍31.59%
custom 537993969926986677810.529%
custom 537994520541794470110.529%

Custom emoji. 11 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 areTelegram’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 8 of the 8 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 189reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

8 Aug 2026, 08:20 UTC28 views17 reactionsread 8 August 2026
Photo

🇷🇺 ДЕНЬ МАТЧА 🇷🇺 🇷🇺 РПЛ | 3 тур ⏰ 19:00 (ТЛТ) | 18:00 (МСК) 🏟️ «РЖД Арена» 📺 Трансляция на Матч Премьер 🇷🇺 — на победу Акрона! 😊 PESTRYAK✨BOOST✨INST 📷

custom 542009303069259291285🙏3custom 54093593361892409101

7 Aug 2026, 17:24 UTC61 views20 reactionsread 8 August 2026
Photo

Пестряк. Вечер. Тренировка. ⭐️ Шикарные кадры в объективе Златы 📸 😊 PESTRYAK✨BOOST✨INST 📷

custom 53821191503594527787custom 52627793866412905395😍32🎉1🙏1custom 53799452054179447011

6 Aug 2026, 18:22 UTC76 views23 reactionsread 8 August 2026
Photo

А это Гарик рассказывает как Дима будет забивать в ближайшее время ⚽️ 😊 PESTRYAK✨BOOST✨INST 📷

9custom 53821191503594527786custom 53819392341794201954custom 54070833514147094033custom 53799396992698667781

5 Aug 2026, 11:13 UTC105 views23 reactionsread 8 August 2026
Photo

Автограф-сессия Димы 📷 📸 Альбом с фотосессии 😊 PESTRYAK✨BOOST✨INST 📷

custom 5382119150359452778106custom 54093593361892409105custom 52627793866412905392

4 Aug 2026, 08:06 UTC148 views25 reactionsread 8 August 2026
Photo

🇷🇺 ДЕНЬ МАТЧА 🟨 ⚽️ Кубок России | 1 тур ⏰ 17:15 (ТЛТ) | 16:15 (МСК) 🏟️ «Солидарность Арена» 📺 Трансляция на Матч ТВ ✍️ Автограф-сессия Пестряка 🇷🇺 — на победу Акрона! P.S. 🔔 🌟🌟🌟 🟡 😊 PESTRYAK✨BOOST✨INST 📷

custom 541138059933832854814custom 52627793866412905395custom 540673045542683740242

3 Aug 2026, 14:30 UTC84 views26 reactionsread 8 August 2026
Forwarded from @fcakronPhoto

Автограф-сессия Дмитрия Пестрякова 🤩 Дима раздаст автографы перед матчем с «Ростовом» на Gate 3 с 16:20 до 17:00. Fan ID для посещения матча не требуется. 🎟 Билеты на матч 🔺 ❌ 🚜 04.08 | 17:15 samt

🔥14custom 53798203034740058486🎉51

1 Aug 2026, 07:13 UTC184 views29 reactionsread 8 August 2026
Photo

🇷🇺 ДЕНЬ МАТЧА 🇷🇺 🐻 РПЛ | 2 тур ⏰ 15:00 (ТЛТ) | 14:00 (МСК) 🏟️ «Солидарность Арена» 📺 Трансляция на Матч Премьер 🇷🇺 — на победу Акрона! P.S. 🇷🇺 🌟🌟🌟 🇷🇺 😊 PESTRYAK✨BOOST✨INST 📷

custom 541138059933832854817custom 54093593361892409106custom 52627793866412905393🔥21

28 Jul 2026, 10:31 UTC230 views26 reactionsread 8 August 2026
Photo

Встреча в академии в кадрах 📸 Без хорошего настроения оттуда уйти было невозможно) 😊 PESTRYAK✨BOOST✨INST 📷

14custom 53821191503594527787custom 54093593361892409104custom 54067304554268374021

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

Republishes

Channels on the register whose posts this channel has forwarded.

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.

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

“PESTRYAK | Дмитрий Пестряков” (@pestryak71), 246 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/pestryak71.

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.