Telegram RegisterThe public register of Telegram

Channel

[ПОИСК АДМИНОВ ПО ВП] HATE BUS CF

@hatebuscf

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

325subscribers

+1 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-1003170581737
TypeChannel
Username@hatebuscf
CreatedBetween 1 September 2025 and 30 November 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 8 August 2026
On Telegramt.me/hatebuscf

Growth

324325324.57 Aug 2026, 19:16 — 324 subscribers8 Aug 2026, 07:20 — 324 subscribers8 Aug 2026, 12:45 — 325 subscribers7 Aug 2026, 19:168 Aug 2026, 12:45
3 measurements taken within a single day, 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 324–325 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 12:45325+1
8 Aug 2026, 07:20324no change
7 Aug 2026, 19:16324first reading

Engagement

19 posts held, back to 20 June 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.

ERR · 30 days
16.9%
avg views ÷ 325 subscribers
Avg views / post
54.8
9 posts measured
Reaction rate
12.7%
reactions ÷ views · ER floor
Posts in window
9
of 19 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 6 of 9 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 August 2026
Posts held19 (20 June 20263 August 2026)
Views total493
Reactions total41
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 07:20 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

122 reactions across 16 posts, in 5 distinct kinds. The most used accounts for 33.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥4133.6%
3024.6%
❤‍🔥2419.7%
🤬2218.0%
💯54.10%

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 16 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 122reactions 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 20 June 2026 to 3 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

3 Aug 2026, 16:20 UTC50 views10 reactionsread 8 August 2026

Само дьявольское пособие прибыло в прекрасный и всеми любимый Екатеринбург для исполнения своей работы посланной сатаной с низины ада дабы все людишки горели в огне и ощутили эти 50° на себе параллельно этому страдая и плача ведь вместо дороги в укромное местечко под названием "дом" те получили билет в один конец и курорт самого девятого круга ада куда едут только 64 и 85 приспешники иссушителя Неанон химия хейтер а

❤‍🔥6🔥3🤬1

Signed Тейкбот хейт автобусы кф

3 Aug 2026, 16:05 UTC45 views6 reactionsread 8 August 2026

64 и 85 хуебусы екб которые ебашут обогреватель по ногам ЛЕТОМ я не хочу ехать в дряхлой бане на колесах я хочу ехать на автобусе с кондиционером🥹🥹 неанон виктар #тейк | @HATEBUSCONF_bot

❤‍🔥3🔥2🤬1

Signed Тейкбот хейт автобусы кф

2 Aug 2026, 09:39 UTC51 views5 reactionsread 8 August 2026

1472 хуже любой труповозки, ехал так что у всех уши нахуй отвяли, ощущение как будто в самолёте с бухим пилотом летишь было #тейк | @HATEBUSCONF_bot

5

Signed Тейкбот хейт автобусы кф

2 Aug 2026, 09:38 UTC52 views5 reactionsread 8 August 2026

51 автобус в Волгодонске сдохнет и сгорит, приходит спустя 50 минут на остановке #тейк | @HATEBUSCONF_bot

5

Signed Тейкбот хейт автобусы кф

2 Aug 2026, 09:37 UTC54 views6 reactionsread 8 August 2026

222 автобус спб, сука маленькая, которая отключает gps и хуй знает когда прибудет #тейк | @HATEBUSCONF_bot

6

Signed Тейкбот хейт автобусы кф

29 Jul 2026, 05:30 UTC67 viewsread 8 August 2026
Forwarded from @mppconfPhoto

Блин, где же найти вп? Да где порог 0+, я устал уже искать... ❌❌❌❌❌🤩🤩🤩🤩 ❌❌❌🔡🔡🔡🔡🔡🔡🔡🔣 ❌❌❌🤩🤩🤩🤩🤩🤩🤩🤩 Тогда мы к вашим услугам! Здесь вы можете спокойно найти нужное вам вп с любым порогом или дни! Вп чистятся только если кф удалён или заблокирован. ❌❌❌🤩🤩🤩🤩🤩🤩🤩🤩 Вп пост // буст // бот поддержки(не для вп) // прайс ❌❌❌🤩🤩🤩🤩🤩🤩🤩🤩 🎀🎀🎀🎀🎀: 🤩 - вафля, он/его, влд. ⚪️⚪️⚪️: отсутствуют! Эмодзи комбо [🔍🤝]

Signed пᴀᴩᴀнойя

28 Jul 2026, 18:38 UTC46 viewsread 8 August 2026
Forwarded from @ilikeitcfPhoto

︎ ︎ ︎ ︎︎ ︎🥹🎁 ︎: ︎ ︎Я ЛЮБЛЮ ЭТО.. ︎ ︎ ︎ ︎︎ ︎︎⎯ ︎ ︎ confession ︎ ︎ ┈ ︎ ︎ ︎ ︎welcome ︎ ︎ ︎ ︎ а что | кого любишь ты ? { 🎁} « mp , rеклама , поиск админов , @ilikeitcf_bot , own : nnasbekk »

Signed пᴀᴩᴀнойя

28 Jul 2026, 11:11 UTC58 viewsread 8 August 2026
Forwarded from @EpsteinSh0pPhoto

🔹очется приобрести аккаунт,который 100% не слетит?накрутить бусты,реакции,чтобы тгк выглядел красиво?🔮 ➖elcome to🥹 t.me/EpsteinSh0p 🪙 ➿➿➿➿➿➿➿➿➿➿➿➿ ❤️вп пост(+300/0+) отзывы прайс ❤️ 🌩🌩🌩🌩🌩🌩🌩🌩🌩🌩🌩

Signed пᴀᴩᴀнойя

26 Jul 2026, 19:03 UTC70 views9 reactionsread 8 August 2026

А 627 бещасть расписание ниибет у него холидейс 627 иди нахуй #тейк | @HATEBUSCONF_bot

7❤‍🔥1🤬1

Signed Тейкбот хейт автобусы кф

11 Jul 2026, 08:58 UTC124 views6 reactionsread 8 August 2026
Photo

👽 - пр. На всякий случай уведомлю, что пустые/подозрительные аккаунты типо таких из конфв летят назуй. Щас заметила нехилое количество потенциальных ботов, и буду чистить 👍

6

Signed ⲕ𐔖ρ𐔖᥈ᥱⲃᥲ ᥈ᥲρᥒᥲ

7 Jul 2026, 21:33 UTC138 views9 reactionsread 8 August 2026

917 автобус иди нахуй, надеюсь ты умрёшь мучительной смертью #тейк | @HATEBUSCONF_bot

🔥7❤‍🔥1🤬1

Signed Тейкбот хейт автобусы кф

7 Jul 2026, 20:24 UTC144 views9 reactionsread 8 August 2026

38 автобус умрет у него мама жирная #тейк | @HATEBUSCONF_bot

🔥6🤬2❤‍🔥1

Signed Тейкбот хейт автобусы кф

Showing the 12 most recent of 19 posts we hold for @hatebuscf. 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 — 984,619 of 1,160,990entries 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

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

“[ПОИСК АДМИНОВ ПО ВП] HATE BUS CF” (@hatebuscf), 325 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/hatebuscf.

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.