Telegram RegisterThe public register of Telegram
Telegram profile photo for BuBuz Company*

Channel

BuBuz Company*

@bubuZCompany

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

13subscribers

+0 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-1002603802942
TypeChannel
Username@bubuZCompany
DescriptionОфициальный телеграм канал команды BuBuz, разрабатывающей сезон по майнкрафту. Ресурсы: 1. Телеграм канал Key(для кого делается сезон) - https://t.me/Key753_Tele 2. Телеграм канал сценариста Vole - https://t.me/volepushet
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live25 September 2026
Measurements held2
On Telegramt.me/bubuZCompany

Growth

137 August 2026 — 13 subscribers12 August 2026 — 13 subscribers7 August 202612 August 2026
2 measurements spanning 5 days. 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 12–14 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 02:4613no change
7 Aug 2026, 08:1813first reading

Engagement

13 posts held, back to 1 March 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 13 posts for this entry, the most recent from 25 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
33
Videos
1
Links
1

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

7 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 42.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍342.9%
🔥342.9%
👏114.3%

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

Measured over the 13 most recent posts we hold, published 1 March 2026 to 25 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

25 Jul 2026, 22:12 UTC71 viewsread 12 August 2026
Photo

1 - катсцена с начале сезона, где Кей падает в дырку 2 - интро после падения, и начальная комната 3 - дизайн Инталиса 4 - торги с жителем, который должен был перенести ощущение карты по прокачке в сезон (копаешь камень -> покупаешь новую кирку -> по новой) 5-9 - пару скриншотов дизайна сициды

Signed VoleSolo

25 Jul 2026, 21:59 UTC14 viewsread 12 August 2026

Но Кей не знал, что тем скмым открыл не только врата, но и клетку с неразумными зомби, которые пробрались в сициду (кристальный город) и устроили там геноцид. Ради сохранности граждан Кей начинает резать зомби, а брат инталиса их ловить. По итогу умирают почти все зомби и гражданы города, включая инталиса. Данный инцидент является ключевым в характере персонажа Кея. На нем строится дальнейшее развитие и рост персонаж…

Signed VoleSolo

25 Jul 2026, 21:48 UTC12 viewsread 12 August 2026

Вернемся к обычному лору. По итогу Кей смог сделать гаджет и отправить сообщение. В это же время в сициде (кристальный город) проходили выборы нового мэра. В момент оглашения результатов инталиса не было дома, и Кей свалив с мероприятия пробрался в подвал инталиса. А если быть точным то в КРИСТАЛЬНОЕ ПОДЗЕМЕЛЬЕ В данной локации Кей встречает Инталиса, но он был немного другого цвета и с небольшими отличиями. Данны…

Signed VoleSolo

25 Jul 2026, 21:33 UTC12 viewsread 12 August 2026

Короче да Общий лор: Гг живет на Земле (практически обычной), но однажды он начинается гнаться на незнакомцем, побежав по горе во время погони незнакомец пробегает, а под кеем открывается гигантская яма, в которую он проваливается После он оказывается в шахтах в локации "кристальная долина". Оказывается он на её краю, где огромное количество ловушек и препятствий. В конце концов Кей доходит до города Сицида. В нем …

Signed VoleSolo

18 May 2026, 14:40 UTC45 viewsread 12 August 2026

Если уж сезон не выйдет, но в скором времени (прям щас начну писать) буду публиковать лорные хуйни, что могло бы быть. Буду говорить и про глобал лор, и про идеи в целом на будущее, и про то, что бы вышло (начало сезона)

Signed Volelelelelele

3 Mar 2026, 10:34 UTC76 views1 reactionsread 12 August 2026

Так ты ж нихуя не делаеш

👍1

Signed Яр

3 Mar 2026, 09:31 UTC68 views1 reactionsread 12 August 2026

Ребята с каждого подписчика 1к мне на счет на пропитание сезона

🔥1

Signed 𝓿𝓸𝓵𝓮 𝔰𝔬𝔩𝔬

1 Mar 2026, 09:58 UTC66 views3 reactionsread 12 August 2026

*признаны экстремистскими на территории РФ

🔥2👏1

Signed D!am0nd Almaz

1 Mar 2026, 09:57 UTC50 views2 reactionsread 12 August 2026

А еще,теперь мы делаем сезон не в minecraft в шахиерском ремесле

👍2

Signed Яр

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

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.

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

“BuBuz Company*” (@bubuZCompany), 13 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/bubuZCompany.

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.