Telegram RegisterThe public register of Telegram
Telegram profile photo for Зариф Байгускаров

Channel

Зариф Байгускаров

@bayguskarov

On this record: Growth · Engagement · Reactions · Posts · Cite this entry

762subscribers

-4 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001538700625
TypeChannel
Username@bayguskarov
CreatedBetween 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live23 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 23 August 2026
On Telegramt.me/bayguskarov

Growth

7627667647 August 2026 — 766 subscribers7 August 2026 — 766 subscribers23 August 2026 — 762 subscribers7 August 202623 August 2026
3 measurements spanning 17 days, net -4. 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 761–767 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 13:58762-4
7 Aug 2026, 01:46766no change
7 Aug 2026, 01:37766first reading

Engagement

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

Reaction mix

17 reactions across 4 posts, in 4 distinct kinds. The most used accounts for 58.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1058.8%
🔥529.4%
15.88%
🥰15.88%

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

Measured over the 4 most recent posts we hold, published 16 July 2026 to 19 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.

Recent posts

18 Jul 2026, 04:35 UTC95 views2 reactionsread 7 August 2026
Photo

↗ Съездил в г. Сибай, провел приём граждан. 🔺Пришли родственники участников СВО с просьбами помочь в установлении места нахождения сыновей, мужей, о разъяснении законов по их поддержке. Эти вопросы будем решать совместно с Министерством обороны РФ и Прокуратурой РФ. 🔺Обратились родители участника СВО, погибшего при защите безопасности Отечества. Как они узнали после смерти сына, во время отпуска он зарегистрировал б

1👍1

17 Jul 2026, 03:23 UTC84 views4 reactionsread 7 August 2026
Photo

↗ КАК Я УВИДЕЛ СЛЕД ПРОРОКА Получив приглашение жителей села Кадырша Зилаирского района на праздник "Здравствуйте, односельчане", посмотрел на карту. Нужно ехать около 55 км от районного центра Зилаир по грунтовой дороге. Надо съездить, посмотреть, как живут люди в дальней деревне среди лесов. Прилёт из Москвы в Уфу, переезд на машине около 5 часов из Уфы в Зилаир и около часа езды до села Кадырша. И я на месте. Осн

👍3🥰1

16 Jul 2026, 05:52 UTC86 views3 reactionsread 7 August 2026
Photo

↗ Съездил в город Кумертау. ➡️ Проверил работы по капитальному ремонту школы № 6 по Федеральному проекту "Модернизация школьных систем образования" на сумму 128 млн руб. Это одна из самых больших школ города, здесь обучаются более тысячи детей. Все замечания, высказанные нами ранее, подрядчик устранил. Глава города О. А. Астахов часто бывает на объекте и держит на контроле. Работы идут по графику. 1 сентября 2026 го

👍3

Showing the 4 most recent of 4 posts we hold for @bayguskarov. 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.

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

“Зариф Байгускаров” (@bayguskarov), 762 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/bayguskarov.

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.