Ждем все вместе😄💚
custom 52401283776622329109custom 54360383458870659021

Channel
@ReginaproSalavat
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
339subscribers
-3 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003343032097 |
|---|---|
| Type | Channel |
| Username | @ReginaproSalavat |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 3 times, most recently 19 September 2026 |
| On Telegram | t.me/ReginaproSalavat |
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 22 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 1 Sept 2026, 16:16 | 339 | -2 |
| 11 Aug 2026, 09:23 | 341 | -1 |
| 10 Aug 2026, 14:00 | 342 | no change |
| 10 Aug 2026, 13:46 | 342 | first reading |
19 posts held, back to 18 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 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 19 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 5 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.
215 reactions across 17 posts, in 6 distinct kinds. The most used accounts for 55.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5436038345887065902 | 119 | 55.3% | |
| custom 5240128377662232910 | 27 | 12.6% | |
| custom 5276099587759695729 | 25 | 11.6% | |
| custom 5237865947804488351 | 19 | 8.84% | |
| custom 5230981123818921967 | 17 | 7.91% | |
| custom 5224372612259405298 | 8 | 3.72% |
Custom emoji. Every row above is a 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 18 of the 19 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 215 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 18 July 2026 to 10 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.
Ждем все вместе😄💚
custom 52401283776622329109custom 54360383458870659021
Скорее бы...💚
custom 543603834588706590213
Опачки
custom 54360383458870659027
Мои соболезнования😔
Трагическая новость, на прошедшей неделе не стало воспитанника «Салавата Юлаева» Амира Ханова Амир считался одним из ведущих защитников Поволжья по 2007 году рождения! неоднократно призывался в сборную ПФО и последние два сезона выступал в НМХЛ за рыбинский «Полет» и «Самару» Наш канал выражает соболезнования всем родным и близким Амира. Уфимский Хоккей ✅
custom 54360383458870659023
Нет, я не плачу ....
custom 52243726122594052988
Спасибо за всё, Кузя 💚 Евгений Кузнецов покидает «Салават Юлаев». Кузнецов присоединился к «Салавату Юлаеву» в январе 2026 года. За это время нападающий провёл за наш клуб 19 матчей в регулярном чемпионате, в которых набрал 18 (6+12) очков. Также на его счету гол и передача в 7 играх плей-офф. Клуб благодарит Евгения за игру и желает удачи в дальнейшей карьере! 🏆 подписывайся, это «Салават»
custom 523098112381892196711
🤣 Кравцов и Кузнецов отдыхают по полной
custom 52378659478044883516custom 52401283776622329102custom 54360383458870659022
💚💚💚
custom 543603834588706590214custom 52760995877596957296custom 52309811238189219673custom 52378659478044883513
Наш идет 💚
Тренерский штаб тоже на месте 😎 🫥МАТЧ ГОДА
custom 54360383458870659026custom 52309811238189219672custom 52760995877596957291
Поздравляю Артёма Горшкова и его возлюбленную🥹❤️
custom 524012837766223291010custom 52760995877596957295custom 54360383458870659023
Showing the 12 most recent of 19 posts we hold for @ReginaproSalavat. 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.
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.
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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“Regi.SY” (@ReginaproSalavat), 339 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/ReginaproSalavat.
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.