Channel
@ushainlovecanal
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
165subscribers
+8 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002223599095 |
|---|---|
| Type | Channel |
| Username | @ushainlovecanal |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/ushainlovecanal |
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 25 September 2026 and assigned it the closest of 31 fixed categories, at 53% 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 |
|---|---|---|
| 19 Sept 2026, 08:01 | 165 | +1 |
| 10 Sept 2026, 16:16 | 164 | +1 |
| 31 Aug 2026, 19:58 | 163 | +2 |
| 24 Aug 2026, 22:33 | 161 | +1 |
| 17 Aug 2026, 10:19 | 160 | +3 |
| 8 Aug 2026, 18:15 | 157 | no change |
| 8 Aug 2026, 06:00 | 157 | first reading |
18 posts held, back to 18 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 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 18 posts for this entry, the most recent from 26 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 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.
32 reactions across 9 posts, in 7 distinct kinds. The most used accounts for 40.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5391215835257784359 | 13 | 40.6% | |
| custom 5255923755548420622 | 7 | 21.9% | |
| ❤ | 5 | 15.6% | |
| custom 5260674380219820276 | 3 | 9.38% | |
| 😁 | 2 | 6.25% | |
| custom 5260615028066756701 | 1 | 3.13% | |
| 🔥 | 1 | 3.13% |
Custom emoji. 4 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 9 of the 18 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 32 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 18 June 2026 to 26 July 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.
Друзья, нужна ваша помощь ❤️ Сейчас я завершаю магистерскую диссертацию по психологии и очень прошу помочь мне с исследованием. Мне нужно набрать 100 респондентов в возрасте от 47 до 60 лет. Тема исследования — переживание одиночества и самопринятие в период поздней зрелости. Если вам от 47 до 60 лет, буду очень благодарна за участие. 🕒 Заполнение анкеты занимает 25–30 минут. 🔒 Все ответы полностью анонимны и буд…
Друзья большая просьба от моей подруги👇
Дорогие и прекрасные Юли и не Юли:)👆, завтра я еду в Москву вести моё любимое занятие и от всей души приглашаю вас присоединиться. Обняться, побыть в хорошем женском кругу, с хорошими взглядами и теплым отношением друг к другу. Позаниматься прекрасной, уникальной, целительной и вдохновляющей практикой. Очень этого сейчас хочется в это странное время. НАЧАЛО В 17:00 - центр "ШАМБАЛА" Воскресенье 26 июля
Video, posted without a caption
Подсмотрела это видео у Анжелы Каневской и проверила свою Алису по версии моей Алисы Аргентина победила Испанию со счётом 2:1, при этом Алиса тоже сказала, что финал прошёл 19 июля 2026 года и что сегодня 18е!
😁2custom 52606743802198202762
В МАКСЕ появилась возможность сделать канал публичным и с красивой ссылкой: https://max.ru/channel_ushainlove
custom 53912158352577843593custom 52559237555484206221custom 52606150280667567011
Сегодня мы решили, что хватит уютно сидеть в гостях у наших друзей. Нужно вести детей показывать культурное и другое красивое, так как просто природно красивое есть у наших друзей прямо не отходя от дома. Откровенно говоря, нам не ехалось и мы сомневались ещё даже стоя на платформе, но всё-таки поехали. Через несколько остановок на платформе Красное село наша электричка встала и больше уже никуда не поехала. Благо эт…
custom 53912158352577843595
Начало в 10:00 сегодня. Перенесли по техническим причинам
Спасибо всем, кто передавал от меня привет моей любимой Ладоге. Мы встретились.
Video, posted without a caption
Voice message, posted without a caption
Photo, posted without a caption
Showing the 12 most recent of 18 posts we hold for @ushainlovecanal. 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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Путь любви с Юлией Виноградовой” (@ushainlovecanal), 165 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/ushainlovecanal.
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.