что именно вам безумно нравится, но вы не хотите рисковать и рассказывать об этом своему партнеру?
❤185🍓46🥴21🗿5

Channel
@usveex
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
49,897subscribers
-1,466 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001155405801 |
|---|---|
| Type | Channel |
| Username | @usveex |
| Description | психология, искусство, мотивация. по вопросам сотрудничества: @qwlink |
| Created | 29 February 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 October 2026 |
| Measurements held | 40 |
| Confirmed unchanged | 1 time, most recently 14 October 2026 |
| On Telegram | t.me/usveex |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 80% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Oct 2026, 20:00 | 49,897 | -31 |
| 13 Oct 2026, 10:49 | 49,928 | -119 |
| 9 Oct 2026, 08:18 | 50,047 | -87 |
| 4 Oct 2026, 18:55 | 50,134 | -116 |
| 26 Sept 2026, 23:21 | 50,250 | -139 |
| 19 Sept 2026, 17:20 | 50,389 | -65 |
| 17 Sept 2026, 06:37 | 50,454 | -48 |
| 15 Sept 2026, 07:18 | 50,502 | -25 |
| 13 Sept 2026, 19:39 | 50,527 | -29 |
| 12 Sept 2026, 03:39 | 50,556 | -68 |
| 9 Sept 2026, 17:42 | 50,624 | -84 |
| 6 Sept 2026, 13:41 | 50,708 | -31 |
| 4 Sept 2026, 02:39 | 50,739 | -39 |
| 2 Sept 2026, 16:44 | 50,778 | -15 |
| 1 Sept 2026, 18:46 | 50,793 | -21 |
| 31 Aug 2026, 21:13 | 50,814 | -44 |
| 31 Aug 2026, 00:37 | 50,858 | -11 |
| 30 Aug 2026, 04:04 | 50,869 | -16 |
| 29 Aug 2026, 05:43 | 50,885 | -16 |
| 28 Aug 2026, 04:33 | 50,901 | first reading |
17 posts held, back to 25 June 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 140 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 11 October 2026 |
|---|---|
| Posts held | 17 (25 June 2026 – 11 October 2026) |
| Views total | 56,960 |
| Reactions total | 1,985 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Oct 2026, 20:34 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 14 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
5,104 reactions across 17 posts, in 6 distinct kinds. The most used accounts for 61.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3,152 | 61.8% | |
| 😭 | 516 | 10.1% | |
| 🍓 | 412 | 8.07% | |
| 😁 | 364 | 7.13% | |
| 🗿 | 353 | 6.92% | |
| 🥴 | 307 | 6.01% |
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 17 of the 17 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 5,104 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 25 June 2026 to 11 October 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.
что именно вам безумно нравится, но вы не хотите рисковать и рассказывать об этом своему партнеру?
❤185🍓46🥴21🗿5
кто работал в общепите, расскажите историю, когда гость ввел вас в ступор
❤194😁70🗿26🍓10
АХАХАХХХААХХ, здесь стебут тупых мужиков так, что хочется переслать каждой подруге 🤣 На канале CONSTANT’S | Территория Императриц жестко разбирают таких особей мужского пола 🚩🚩🚩 Подпишись, если хочешь вовремя распознавать таких «мужчин»: https://t.me/+2C4gpLoewj9lMjU6
🗿16❤7🍓2
собираем доску желаний! 🌊 отправь в комментарии фото своей мечты/ цели
❤195🍓51
девушки, о чем вы всегда хотели спросить парней, но стеснялись?
❤311🍓57🥴24🗿7
расскажите историю, когда можно сказать «это была судьба»
❤312🍓61😭30
Проверь себя. Только честно. 🚩 Он проверяет твой телефон, а свой кладёт экраном вниз и уносит с собой в душ 🚩 У него «все бывшие были сумасшедшими», но ты искренне веришь, что станешь исключением 🚩 Тебе нельзя это платье, эти подписки и эту подругу, а ему можно всё 🚩 После каждой ссоры извиняешься ты, даже когда не виновата 🚩 Внимание в сторис ему важнее, чем твоё 🚩 Ты заранее продумываешь, как сказать ему что-то, ч…
🥴15❤1
девушки, после какой его фразы ваша влюбленность пропала?
❤193🗿95😭37🍓14
парни, какой красный флаг вы прощали своей девушке?
❤186🥴97🗿34😭23
Threads заблокировал один из самых популярных русскоязычных аккаунтов — Мистера Гринфлага На его профиле было почти 6 млн просмотров. Парень развирусился в сети своими разборами поведения и психологии мужчин. После бана в Тредс он снова начал вести ТГ-канал @greenflagmr — там прекрасно всё: стыдные истории измен, кринжовые переписки с нарциссами в Twinby и просто интересные мысли о бесконечно-вечном. От его канала…
🥴14❤4
какая серьёзная тема редко поднимается в обществе?
❤279🍓55🗿32😁4
Друзья! Давайте поддержим подопечных фонда @dariedu. Переходите по ссылке, кладите в корзину один или несколько продуктовых наборов и сделайте жизнь 3000 семей немного проще. Нам надо собрать всего 5 миллионов, чтобы мамы, которые растят детей в одиночку, родители с детьми инвалидами и просто семьи, где выбирают между покупкой тетрадок с красивой обложкой и пачкой макарон, в этот раз 1 сентября стал праздничным. Пр…
❤38😭7🍓5
Showing the 12 most recent of 17 posts we hold for @usveex. 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.
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.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 25 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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 15 seed channels' Telegram-generated recommendation lists 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 14 October 2026 — this entry's latest reading, not the date you are reading this.
“никому не рассказывай” (@usveex), 49,897 subscribers as measured 14 October 2026. Telegram Register, tgregister.com/channel/usveex.
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.