Telegram RegisterThe public register of Telegram
Telegram profile photo for Матюшенко Евгений, блог о жизни и бизнесе

Channel

Матюшенко Евгений, блог о жизни и бизнесе

@Evgen_blogg

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

698subscribers

+0 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-1002280515147
TypeChannel
Username@Evgen_blogg
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live24 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 24 August 2026
On Telegramt.me/Evgen_blogg

Growth

698699698.57 August 2026 — 698 subscribers8 August 2026 — 698 subscribers16 August 2026 — 699 subscribers24 August 2026 — 698 subscribers7 August 202624 August 2026
4 measurements spanning 17 days. 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 698–699 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 18:33698-1
16 Aug 2026, 06:58699+1
8 Aug 2026, 02:19698no change
7 Aug 2026, 14:04698first reading

Engagement

8 posts held, back to 21 June 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
27.7%
avg views ÷ 698 subscribers
Avg views / post
193
1 post measured
Reaction rate
17.6%
reactions ÷ views · ER floor
Posts in window
1
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 2 August 2026
Posts held8 (21 June 20262 August 2026)
Views total193
Reactions total34
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 02:19 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.

What this channel posts

Video runtime
3s
Average length
3s

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

107 reactions across 8 posts, in 8 distinct kinds. The most used accounts for 32.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥3532.7%
3431.8%
❤‍🔥1917.8%
💯54.67%
🌚43.74%
👏43.74%
👍32.80%
😁32.80%

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 107reactions 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 21 June 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, 05:33 UTC193 views34 reactionsread 8 August 2026
Photo

Отпуск в Китае был максимально необычным и насыщенным Почему так: 1. А как иначе? Сказать по правде, я не умею в расслабленный пляжный отдых. Я всегда стараюсь «за***ть» себя и окружающих, максимально насытив поездку событиями. В этом трипе на 12 дней у нас было 5 перелетов🙈 2. В Китае очень жарко - мы выбрали самый не подходящий сезон для путешествий. Пешеходные прогулки давались не просто🙂 3. Китай - это макси

🔥11❤‍🔥106👍3👏2💯2

Signed Евгений Матюшенко

26 Jun 2026, 19:21 UTC475 views7 reactionsread 8 August 2026
Video message

Video message, posted without a caption

4😁2🔥1

Signed Евгений Матюшенко

26 Jun 2026, 18:56 UTC441 views11 reactionsread 8 August 2026
Video message

Video message, posted without a caption

🔥9❤‍🔥1👏1

Signed Евгений Матюшенко

26 Jun 2026, 17:33 UTC447 views5 reactionsread 8 August 2026

Мы с Максом сегодня тусим🙂

🌚4❤‍🔥1

Signed Евгений Матюшенко

26 Jun 2026, 17:33 UTC435 views15 reactionsread 8 August 2026
Video message

Video message, posted without a caption

🔥104😁1

Signed Евгений Матюшенко

25 Jun 2026, 06:10 UTC475 views6 reactionsread 8 August 2026
Photo

В 2021 году мы с @Loktionov_on_off не задумываясь приняли решение взять на себя управление брендом RaftMaster - еще бы, ведь мы с детства знакомы с этими судами и не раз ходили на них в походы Прошло 5 лет и мы останавливаем работу по проекту RaftMaster Водный туризм и снаряжения для работы на высоте также далеки друг от друга, как волейбол и настольный теннис🙂 Настало время сфокусировать ресурсы на основном напра

❤‍🔥5👏1

Signed Евгений Матюшенко

24 Jun 2026, 18:27 UTC388 views5 reactionsread 8 August 2026
Photo

Друзья, нужна ваша помощь Я тут недавно тачку разбил и нужно ее ремонтировать Решил ремонтировать, а потом продавать Нужен проверенный кузовной ремонт, желательно на Юго-востоке Москвы Если можете кого-то порекомендовать, буду благодарен💚

🔥4❤‍🔥1

Signed Евгений Матюшенко

21 Jun 2026, 14:17 UTC486 views24 reactionsread 8 August 2026
Forwarded from @rehab_burovaPhoto

❤️ Большую часть жизни мы воспринимаем медицину как что-то само собой разумеющееся Поликлиники работают. Скорая приезжает. В больницах дежурят врачи. Где-то круглосуточно горит свет в операционной. Кажется, что так было и будет всегда! Но однажды приходит день, когда беда касается лично тебя. Когда заболевает ребенок. Когда родители оказываются в больнице. Когда после телефонного звонка мир вдруг делится на «до» и

20💯3❤‍🔥1

Signed Евгений Матюшенко

Showing the 8 most recent of 8 posts we hold for @Evgen_blogg. 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 24 August 2026 — this entry's latest reading, not the date you are reading this.

“Матюшенко Евгений, блог о жизни и бизнесе” (@Evgen_blogg), 698 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/Evgen_blogg.

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.