The Winner Takes it all!!! 🍾
💘11custom 54247015306011831805custom 54609878538592159835🔥3

Channel
@matveykinblog
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
174subscribers
+0 since we began measuring on 9 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001790505303 |
|---|---|
| Type | Channel |
| Username | @matveykinblog |
| Description | Мотя из Тулы✌️ ✨здесь про… - саморазвитие и работу - учёбу - жизнь 17-летнего подростка - творчество 📍my inst & tiktok: matveeeykaz |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 September 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/matveykinblog |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 04:22 | 174 | no change |
| 9 Sept 2026, 00:47 | 174 | first reading |
10 posts held, back to 24 May 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.
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.
| Window | Rolling 30 days · latest post in window 28 August 2026 |
|---|---|
| Posts held | 10 (24 May 2026 – 28 August 2026) |
| Views total | 141 |
| Reactions total | 24 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Sept 2026, 04:22 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.
Lifetime counters from Telegram’s own channel header, read 9 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
157 reactions across 10 posts, in 15 distinct kinds. The most used accounts for 19.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 31 | 19.7% | |
| 💘 | 27 | 17.2% | |
| custom 5424701530601183180 | 21 | 13.4% | |
| custom 5285150634335555693 | 17 | 10.8% | |
| custom 5406647824551001927 | 17 | 10.8% | |
| ❤🔥 | 11 | 7.01% | |
| custom 5460987853859215983 | 8 | 5.10% | |
| custom 5465456264819532853 | 7 | 4.46% | |
| custom 5400303659638607074 | 5 | 3.18% | |
| custom 5418250489722594220 | 4 | 2.55% | |
| 💋 | 3 | 1.91% | |
| 🔥 | 3 | 1.91% | |
| custom 5269750698383281208 | 1 | 0.637% | |
| custom 5454333025372384709 | 1 | 0.637% | |
| custom 5463358572727386853 | 1 | 0.637% |
Custom emoji. 10 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 10 of the 10 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 157 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 24 May 2026 to 28 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.
The Winner Takes it all!!! 🍾
💘11custom 54247015306011831805custom 54609878538592159835🔥3
насыщенные дни, возвращение домой, поступление и последние деньки в релаксе🤩 👉ссылка на вопросы как всегда здесь
❤4custom 54182504897225942202custom 54609878538592159832custom 52697506983832812081custom 52851506343355556931custom 54066478245510019271custom 54247015306011831801custom 54543330253723847091
🖇Из Москвы в Турцию с пересадкой в Ханте-Мансийске😬
❤8custom 52851506343355556935custom 54654562648195328533custom 54247015306011831801custom 54609878538592159831
✈️ куда лечу?
❤🔥3custom 52851506343355556931custom 54066478245510019271custom 54247015306011831801custom 54654562648195328531
👽меня долго здесь не было, возвращаюсь после насыщенных событиями июня и июля! ну и, конечно, спрашивайте, что интересно, с радостью отвечу! 👉ссылка как всегда здесь
❤4💘2❤🔥1💋1custom 52851506343355556931custom 54066478245510019271custom 54654562648195328531
Я влюбился в этот город, он меня очень вдохновляет!
❤🔥7custom 54247015306011831803💋2💘1custom 52851506343355556931custom 54066478245510019271custom 54654562648195328531
🔥Белые ночи и приключения в Петербурге захватывают, давайте поболтаем, жду ваших вопросов 👉 ТУТ
❤10💘1custom 54247015306011831801
🌟прошлая жизнь заканчивается в Туле, новый этап начинается в Петербурге
💘11custom 54066478245510019274custom 54247015306011831804custom 54182504897225942201
✅шпаргалки – done ✅съездить на речку – done ✅ЕГЭ по русскому – done ✅18 лет – done
custom 52851506343355556938custom 54003036596386070745custom 54066478245510019275💘1custom 54182504897225942201custom 54247015306011831801custom 54654562648195328531
✌предлагаю нам с вами немного поболтать: пишите всё, что интересно 👉 сюда
❤5custom 54066478245510019274custom 54247015306011831804custom 54633585727273868531
Showing the 10 most recent of 10 posts we hold for @matveykinblog. 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“матвей” (@matveykinblog), 174 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/matveykinblog.
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.