Telegram RegisterThe public register of Telegram
Telegram profile photo for Фанклуб Буши

Channel

Фанклуб Буши

@Bush1nsk

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

77subscribers

+1 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1002546340254
TypeChannel
Username@Bush1nsk
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live31 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 31 August 2026
On Telegramt.me/Bush1nsk

Growth

767776.510 August 2026 — 76 subscribers11 August 2026 — 76 subscribers31 August 2026 — 77 subscribers10 August 202631 August 2026
3 measurements spanning 21 days, net +1. 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 76–77 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 05:4277+1
11 Aug 2026, 02:2476no change
10 Aug 2026, 13:0176first reading

Engagement

18 posts held, back to 15 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 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 4 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
7m 27s
Average length
1m 52s

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

Reaction mix

122 reactions across 17 posts, in 8 distinct kinds. The most used accounts for 22.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52806922564188460602722.1%
custom 54295463310204674812621.3%
❤‍🔥2419.7%
custom 51926505979914753711713.9%
custom 54293831995726305521411.5%
🕊75.74%
custom 542731716997940100443.28%
32.46%

Custom emoji. 5 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 17 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 122 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 15 July 2026 to 4 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.

Recent posts

4 Aug 2026, 18:09 UTC24 views1 reactionsread 10 August 2026
File

сегодня без барабанов #трек

custom 54293831995726305521

4 Aug 2026, 06:42 UTC40 views10 reactionsread 10 August 2026
Photo

Все персонажи моего будущего ош в кратце: #щп

❤‍🔥8custom 54295463310204674812

3 Aug 2026, 12:12 UTC45 views17 reactionsread 10 August 2026
Video

Тот самый незавершенный контент 2024 #анимация

custom 519265059799147537110custom 52806922564188460603custom 54293831995726305522🕊1custom 54295463310204674811

2 Aug 2026, 15:06 UTC48 views9 reactionsread 10 August 2026
Photo

спойлер к арту, я снова начинаю лениться доканчивать начатое, поэтому пусть здесь будут в открытом доступе эти две ведьмочки #скетч #спойлер

custom 52806922564188460609

1 Aug 2026, 15:42 UTC54 views5 reactionsread 10 August 2026
File

очередной черновик закончен (наверное)🔫 #трек

🕊4❤‍🔥1

31 Jul 2026, 07:33 UTC73 views7 reactionsread 10 August 2026
Photo

Бешеное Тако #арт #InanimateInsanity

custom 51926505979914753717

27 Jul 2026, 06:46 UTC86 views9 reactionsread 10 August 2026
Photo

Стульеманка 🤩 #арт #InanimateInsanity

custom 54295463310204674816❤‍🔥3

24 Jul 2026, 09:11 UTC100 views4 reactionsread 10 August 2026
Photo

Внимание спойлер! #спойлер

custom 54293831995726305523custom 52806922564188460601

24 Jul 2026, 06:38 UTC99 views6 reactionsread 10 August 2026
Video

🤩Вообще, давайте поговорим о том, что здесь в основном будет публиковаться и о том что я планирую выпустить🤩 🕊👆🕊 🤩Что здесь будет: – фандомные арты – арты уже с моими ос – спойлеры к проектам – реквесты и т.п. – ленивые анимации – музяка 🌷Что я планирую делать: – полноценные комиксы (возможно в будущем пойдут в печать и у меня будет бизнес хохохо) – свое обджект шоу (планируется именно полнометражка, серийник рисоват

custom 52806922564188460605custom 54293831995726305521

23 Jul 2026, 09:06 UTC89 views6 reactionsread 10 August 2026

УРА НАС СНОВА 70 РЕБЯТА НАС 70 УРААААА НАС 70 ЮБИЛЕЙ УРАОАОРАКРАОАОАРАО #щп

❤‍🔥6

23 Jul 2026, 06:00 UTC97 views3 reactionsread 10 August 2026
File

File, posted without a caption

custom 54273171699794010043

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

22 Jul 2026, 11:00 UTCAnonymous Poll28 voters

Какие арты вы хотите видеть здесь?

  1. Обджект шоу54%
  2. Млп14%
  3. Тяночки21%
  4. Фнф❤29%
  5. Дельтарун18%
  6. Мои ос39%
  7. Другое7%

The shares total 182%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 18 most recent posts we hold, published 15 July 2026 to 4 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Mentions

Named by 4 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.

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

“Фанклуб Буши” (@Bush1nsk), 77 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/Bush1nsk.

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.