Куда меня занесло 😱
custom 5463199066231937162184custom 528725266863961636844❤11custom 54630592435716172069custom 54610054030955716433
![Telegram profile photo for VeselOFF - [Грустнофф]💡](https://cdn.tgregister.com/av/93/931e344a6782ddbfc807135204aafda69f12822b8cc7612836eca1d3f9b6d271.jpg)
Channel
@veseloofYT
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
13,048subscribers
-103 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001571144880 |
|---|---|
| Type | Channel |
| Username | @veseloofYT |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/veseloofYT |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 03:20 | 13,048 | -32 |
| 5 Sept 2026, 20:42 | 13,080 | -21 |
| 3 Sept 2026, 16:37 | 13,101 | -13 |
| 2 Sept 2026, 09:06 | 13,114 | -13 |
| 1 Sept 2026, 10:48 | 13,127 | -23 |
| 31 Aug 2026, 09:43 | 13,150 | -5 |
| 30 Aug 2026, 12:12 | 13,155 | -4 |
| 29 Aug 2026, 12:38 | 13,159 | -13 |
| 28 Aug 2026, 09:03 | 13,172 | -12 |
| 27 Aug 2026, 06:08 | 13,184 | +42 |
| 26 Aug 2026, 02:53 | 13,142 | +126 |
| 25 Aug 2026, 04:48 | 13,016 | -9 |
| 24 Aug 2026, 04:46 | 13,025 | -19 |
| 22 Aug 2026, 14:42 | 13,044 | -6 |
| 21 Aug 2026, 04:33 | 13,050 | -1 |
| 19 Aug 2026, 06:35 | 13,051 | -26 |
| 18 Aug 2026, 07:35 | 13,077 | -8 |
| 17 Aug 2026, 10:48 | 13,085 | -4 |
| 15 Aug 2026, 17:37 | 13,089 | -15 |
| 14 Aug 2026, 02:37 | 13,104 | first reading |
104 posts held, back to 31 July 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 49 pages 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 1 September 2026 |
|---|---|
| Posts held | 104 (31 July 2026 – 1 September 2026) |
| Views total | 353,270 |
| Reactions total | 17,722 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 20:39 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.
Measured directly from 9 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.
25,368 reactions across 104 posts, in 7 distinct kinds. The most used accounts for 30.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 7,606 | 30.0% | |
| custom 5287252668639616368 | 7,064 | 27.8% | |
| custom 5463199066231937162 | 4,913 | 19.4% | |
| custom 5463059243571617206 | 3,340 | 13.2% | |
| custom 5461005403095571643 | 876 | 3.45% | |
| custom 5461026126312775671 | 833 | 3.28% | |
| custom 5463303107519716229 | 736 | 2.90% |
Custom emoji. 6 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 104 of the 104 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 25,368 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 104 most recent posts we hold, published 31 July 2026 to 1 September 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @veseloofYT. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 104 most recent posts we hold for this entry, published 31 July 2026 to 1 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Куда меня занесло 😱
custom 5463199066231937162184custom 528725266863961636844❤11custom 54630592435716172069custom 54610054030955716433
Купил сегодня еще такую штуковину Мб пригодиться для съемок
❤115custom 528725266863961636822custom 54630592435716172063
Это чушь собачья
custom 5463199066231937162127custom 528725266863961636819❤1custom 54630592435716172061
Тарифы у Старлинка, конечно, не дешевые, но буду тестить Вообще история его покупки достаточно интересная, обязательно расскажу в видео Вам вообще интересно то будет такое посмотреть?
custom 5287252668639616368220❤33custom 54631990662319371624custom 54610054030955716432custom 54630592435716172061
Я купил Старлинк Спасибо, Илон Маск, за хорошую упаковку
❤239custom 528725266863961636836custom 546319906623193716236custom 546330310751971622910custom 54610054030955716434custom 54630592435716172063
Как провели лето? Пишите в комментариях
❤112custom 546100540309557164329custom 528725266863961636827custom 54630592435716172064
Забирайте ключ У меня в регионе не доступно
custom 5287252668639616368183custom 546100540309557164321custom 546330310751971622917❤1custom 54630592435716172061
ВЫБОРЫ БЕЗ ИНТЕРНЕТА Немного рассуждений про будущее интернета после выборов https://youtu.be/mYmrqvfdkko
custom 5463059243571617206106custom 528725266863961636826custom 54610054030955716436custom 54633031075197162292❤1
Очень странное поведение со стороны YouTube. На видео про GTA 6 на втором канале сегодня прилетело предупреждение из-за «опасных кадров». Чтобы вы понимали, на протяжении всего видео были кадры из трейлера игры, и часть из них YouTube посчитал «опасными кадрами». Пришлось заблюрить некоторые моменты, и после этого YouTube сразу снял ограничения. Сделал это не потому, что я денег с монетизации не заработают (да плев…
❤184custom 528725266863961636845custom 546100540309557164314custom 54630592435716172068custom 54631990662319371622
Video message, posted without a caption
❤140custom 528725266863961636837custom 54630592435716172061
По факту Моё мнение естественно самое правильное
custom 5287252668639616368175❤12custom 54631990662319371628custom 54630592435716172065custom 54633031075197162291
ПЕЧАЛЬНАЯ СУДЬБА GTA 6 Новое всем нужное видео про трейлер GTA 6 С вас лайк и комментарий ❤️ https://youtu.be/DUxgGLN7RHc
❤85custom 528725266863961636813custom 54630592435716172063
Showing the 12 most recent of 104 posts we hold for @veseloofYT. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
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.
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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.
“VeselOFF - [Грустнофф]💡” (@veseloofYT), 13,048 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/veseloofYT.
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.