Telegram RegisterThe public register of Telegram

Channel

Ярмарка мёда

@rinatbashirov

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

3,237subscribers

-3 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001650830277
TypeChannel
Username@rinatbashirov
Created31 August 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/rinatbashirov

Growth

3,2373,2403,238.56 August 2026 — 3,240 subscribers7 August 2026 — 3,240 subscribers10 August 2026 — 3,237 subscribers6 August 202610 August 2026
3 measurements spanning 4 days, net -3. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 3,237–3,240 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 17:363,237-3
7 Aug 2026, 10:513,240no change
6 Aug 2026, 11:193,240first reading

Engagement

20 posts held, back to 1 February 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof 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 20 posts for this entry, the most recent from 21 May 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
8s
Average length
8s

Measured directly from 1 video 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.

Reaction mix

10,857 reactions across 20 posts, in 17 distinct kinds. The most used accounts for 30.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3,27330.1%
😁2,24620.7%
👍1,22411.3%
👎8477.80%
🏆7136.57%
❤‍🔥6956.40%
🔥4624.26%
💯4013.69%
😢4013.69%
1631.50%
1341.23%
👏1311.21%
🐳650.599%
🙏530.488%
🤝350.322%
🤗110.101%
😍30.028%

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 20 of the 20 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 10,857reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 1 February 2024 to 21 May 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.

Recent posts

21 May 2026, 19:23 UTC≈9,540 views556 reactionsread 7 August 2026

Полностью познал хоккей)

😁286164❤‍🔥35👎32🏆11💯11👍10🔥3

14 Apr 2026, 16:40 UTC≈19,800 views1,344 reactionsread 7 August 2026

Это нечестная игра. Локомотиву дальнейших успехов🤝

😁588❤‍🔥323👎195💯1074925👍18🐳15

10 Apr 2026, 10:13 UTC≈23,700 views755 reactionsread 7 August 2026

КХЛ необходимо ввести в регламент антимонопольные положения. Наподобие тех, что существуют в США. Там принята система норм, направленная на предотвращение монополизации рынков, защиту конкуренции и обеспечение баланса интересов участников рыночных отношений. Не должно быть в КХЛ команд без слабых мест. Локомотив обязан перераспределить свой кадровый ресурс в пользу конкурентов🤭 P.S. С нами можно не перераспределятьс

😁483139👍57👎48👏8🐳64💯4

4 Apr 2026, 07:29 UTC≈38,300 views950 reactionsread 7 August 2026

Не могу сказать, что мы давние друзья с Николаем Николаевичем Заварухиным. Но вместе с этой фамилией прожили свою жизнь тысячи болельщиков в республике. Это фундамент Салавата Юлаева💚

616👍181👏99💯26🏆9👎8🤝7🐳4

2 Apr 2026, 17:43 UTC≈44,200 views1,237 reactionsread 7 August 2026

Очень горд за ребят! Мы идём дальше 💚💚💚

793🔥250🏆150❤‍🔥14👎7👍6🤝5😁5

1 May 2025, 13:56 UTC≈63,900 views1,335 reactionsread 7 August 2026

Сегодня было безобразие. Мы держим строй💚

845💯223👎82❤‍🔥71😁46🏆2217👍15

26 Feb 2024, 17:52 UTC≈45,100 views396 reactionsread 7 August 2026

Очень интересный был сегодня матч. Нашим ребятам спасибо за победу!💚Хороший подарок болельщикам на завершение регулярного чемпионата. Могли выиграть с бОльшим счетом. Аймурзина не хватило😄

217👍60👎42😁35🏆18❤‍🔥10🔥74

24 Feb 2024, 15:25 UTC≈40,100 views237 reactionsread 7 August 2026

Наверное, надо было проиграть сегодня, чтобы привести себя в порядок в нужный момент.

117👎6720🏆12😁11🐳5💯2😢2

24 Feb 2024, 11:31 UTC≈39,200 views468 reactionsread 7 August 2026
Video

Егор Сучков. Травма верхней части тела (по отношению к нападавшему-нижняя). Срок восстановления 2-3 недели. Заказчики разыскиваются

😢357🙏39👎21😁1714👍65🤝4

21 Feb 2024, 17:13 UTC≈22,300 views248 reactionsread 7 August 2026

Обе команды хотели выиграть😂

128😁49🏆30👎23👍9🤝4🐳31

20 Feb 2024, 18:45 UTC≈22,600 views311 reactionsread 7 August 2026

Вчера пришлось срочно вернуться домой по семейным обстоятельствам. Важным. Не смог быть на матче с Динамо. Посмотрел только сегодня утром. Видимо, часть удачи тоже с собой увез😂Но играли хорошо. Команда вернулась, значит, удача в Уфе уже в полном объеме. Реально, не динамо😎

🏆202👎36👍26❤‍🔥139😁8💯74

17 Feb 2024, 16:37 UTC≈25,200 views400 reactionsread 7 August 2026

Не расстраиваемся. Сейчас на местном автобусе в аэропорт, потом самолетом в МСК. Там ждёт нас победа

🏆175👎111😁4217👍16😢129🤝6

Showing the 12 most recent of 20 posts we hold for @rinatbashirov. 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.

Citation-graph rank

Citation-graph rank — 660,978 of 1,183,361entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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.

Mentions

Named by 2 registered channels — 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.

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.

Cite this entry

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 10 August 2026 — this entry's latest reading, not the date you are reading this.

“Ярмарка мёда” (@rinatbashirov), 3,237 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/rinatbashirov.

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.