Channel
@bsdsetkibesitcf
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
25subscribers
+2 since we began measuring on 14 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004316127193 |
|---|---|
| Type | Channel |
| Username | @bsdsetkibesitcf |
| Created | 20 August 2026 — measured — dated from the channel’s first post |
| First recorded | 14 September 2026 |
| Last confirmed live | 30 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 4 times, most recently 30 October 2026 |
| On Telegram | t.me/bsdsetkibesitcf |
Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 16 October 2026 and assigned it the closest of 31 fixed categories, at 48% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Oct 2026, 19:38 | 25 | +1 |
| 28 Sept 2026, 14:17 | 24 | +1 |
| 14 Sept 2026, 21:22 | 23 | no change |
| 14 Sept 2026, 20:47 | 23 | first reading |
19 posts held, back to 20 August 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 19 posts for this entry, the most recent from 13 September 2026. An engagement rate over an empty window would be a number about nothing.
32 reactions across 7 posts, in 13 distinct kinds. The most used accounts for 34.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤝 | 11 | 34.4% | |
| 😭 | 4 | 12.5% | |
| ❤🔥 | 3 | 9.38% | |
| 👎 | 2 | 6.25% | |
| 🕊 | 2 | 6.25% | |
| 😁 | 2 | 6.25% | |
| 🤡 | 2 | 6.25% | |
| 👏 | 1 | 3.13% | |
| 💘 | 1 | 3.13% | |
| 🔥 | 1 | 3.13% | |
| 🗿 | 1 | 3.13% | |
| 🤔 | 1 | 3.13% | |
| 🥰 | 1 | 3.13% |
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 7 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 32 reactions 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 August 2026 to 13 September 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.
🖥📸 🤩ОБРО ПОЖАЛОВАТЬ В СЕТКУ ПО БСД/СТРИМЕРСКАЯ АУ 🪙 ↻ ◁ II ▷ ↺ 👾 ↠ⁿᵉˣᵗ ˢᵒⁿᵍ ↺ ʳᵉᵖᵉᵃᵗ ⊜ ᵖᵃᵘˢᵉ 🤩 😀😀😀😀😀😀 🤩 🤩могла бы ли Изуми Кека вести стримы на твиче ? -Насколько был бы популярным стримером Николай Гоголь? -Кто был бы менеджером Дазая? 🤩МОГ БЫ ЛИ ТЫ СТАТЬ СТРИМЕРОМ? ИЛИ МОНТАЖЕРЕМ ДЛЯ АКУТАГАВЫ РЮНОСКЕ? 🤩АВАЙ УЗНАЕМ! ᴠᴏʟᴜᴍᴇ: 🤩 😀😀😀😀😀 🤩
🔥1
× || :: Подслушка || #тейк || bot :: @vbsdsetkaxbesitbot
🤝6❤🔥3🤡2👏1🗿1
🌟🌟“Мотор.. И, начали!„ 🌟🌟 🌫——————🎇🎇——————🌫 А что если бы все персонажи из 𝙱𝚂𝙳 были бы актёрами? 🅰️обро пожаловать в сетку по Бродячим псам по актёр Ау! 🅰️ожет ли быть Рампо профессиональным актёром, а Мори Огай новичком, ведь всю жизнь до этой съёмки он был врачом? Да, конечно! Все, как пожелают наши "актёры"! 🅰️ы тоже можете стать актёром этого кино, а может вас по душе зрительское кресло? 🌟🌟——————😀😀——————🌟🌟 …
! В сетке гендерсвап. —Двери нашего города всегда открыты для вас, Господа!— голос диктора был мягким,обволакивающим.Хотелось слушать его только больше.—Не стоит стесняться,прошу вас.Наш драгоценный город примет всех и вся. — Но вы должны понимать,что всё не так просто,— диктор сделал паузу,словно выдерживал интригу перед открытием важной тайны.—Чтобы оказаться в нашем городе,вам стоит выполнить пару пунктов.Не бой…
#вп
— опанькии, кто-то читает этот пост, хехе? ⭒. ɜдᴩᴀᴄᴛᴇ-ɜдᴩᴀᴄᴛᴇᴇᴇ!! . • ⊳︎ ☆ ⊲︎ • ⭒ ° Давно искал ɯᴋᴏᴧьный ᴩуᴄᴩᴇᴀᴧ? • Тогда тебе к нам!¡! ⊳︎ ⊳︎ ⊳︎ — · — · — · — · — · — · — · — · — · — · — · — Задумывался, что сегодня приключилось у Гоголя, чем Огури занят всё лето, куда ездил Рембо или как отрывается Альбатросс? З…
🌟🌟🌟🌟🌟 — у меня есть классная идея для ивента! — я обожаю взаимодействия пейрингов в сетках... — ищу соигрока, пиши "я" Знакомо? Добро пожаловать в... 🤩 BSD SETKI CONFESSION 🤩 🤩 ...Здесь вы можете не только обсуждать определенные проекты, но и искать вдохновение, просить помощи или просто генерировать идеи для остальных игроков! Тематика тейков не ограничена. Просим ко вниманию: 🤩 🤿 …
× || :: Владелец сетки @BetweenTakes_BSD || #тейк || bot :: @vbsdsetkaxbesitbot
😭4👎2💘1
#вп
× || :: ...то что в этом посте некоторым людям безнаказанно позволили говорить откровенный грубости || #тейк || bot :: @vbsdsetkaxbesitbot
🤝5😁2🤔1
Оформление тейков добавлять не нужно, бот оформляет тейки сам. || #адм || bot :: @vbsdsetkaxbesitbot
🥰1
#вп
Showing the 12 most recent of 19 posts we hold for @bsdsetkibesitcf. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 9 October 2026 — this entry's latest reading, not the date you are reading this.
“в bsd сетках бесит . . .” (@bsdsetkibesitcf), 25 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/bsdsetkibesitcf.
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.