Telegram RegisterThe public register of Telegram
Telegram profile photo for ᴾᵒˢᵗᶦᶰᵍ"ᴡɪɴᴇ ᴄʟᴜᴅ,,🥤

Channel

ᴾᵒˢᵗᶦᶰᵍ"ᴡɪɴᴇ ᴄʟᴜᴅ,,🥤

@bsd_1_2

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

4subscribers

+0 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1002389411279
TypeChannel
Username@bsd_1_2
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live13 August 2026
Measurements held2
On Telegramt.me/bsd_1_2

Growth

412 Aug 2026, 01:01 — 4 subscribers13 Aug 2026, 10:03 — 4 subscribers12 Aug 2026, 01:0113 Aug 2026, 10:03
2 measurements spanning 1 day. 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 3–5 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 10:034no change
12 Aug 2026, 01:014first reading

Engagement

15 posts held, back to 5 July 2025the 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 15 posts for this entry, the most recent from 17 July 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
23
Links
6

Lifetime counters from Telegram’s own channel header, read 13 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

14 reactions across 4 posts, in 5 distinct kinds. The most used accounts for 35.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
535.7%
🔥535.7%
💘214.3%
🍓17.14%
💋17.14%

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

Measured over the 15 most recent posts we hold, published 5 July 2025 to 17 July 2025, 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

17 Jul 2025, 17:45 UTC41 views2 reactionsread 13 August 2026
Photo

🔠🔠🔠🔠🔠*️⃣ 💮🔤 🔠🌟🌟🌟 🌟🌟🌟🔠🌟🌟🌟🌟🌟🌸💋 С светлым праздником вас, Осаму Дазай! Очень сильно извиняюсь если опоздал (( От лица администрации желаем вам всего самого наилучшего. Чтобы дни были именно такими какие должны быть на ваш взгляд! Главное будьте здоровы и находитесь только там где чувствуете себя супер! Бесконечное спасибо за то что вы с нами, надеямся что это не последнее ваше день рождение с wine clud. 🤍🤍🤍🤍

💘1🔥1

12 Jul 2025, 17:49 UTC47 views1 reactionsread 13 August 2026
Photo

✨🤩🤩🤩⭐⭐⭐⭐ 🔤🔤🔤 — Не ждали??? Да не ждали. Поль Верлен отметил что вы у нас любите Бинго и всякие тестики! И мы решили провести вам такого рода 🪡🧦🎂🌲🪟🍉🐮🎂🪡🧑‍🦰!! 🤍🤍🤍 ☺️🥬🥬🥬🥬🥬🎚️: 1. Вы можете написать о любом участнике он/она 10/10 , но.... Обязательно когда пишем негативное ниже написать положительное. 2. Можно написать и о себе. 3. Можно написать о нескольких участниках. Время интерактива : с 15 июля 18.50 д

1

12 Jul 2025, 10:19 UTC10 viewsread 13 August 2026
Forwarded from @exlife00Photo

💓Здᴩᴀʙᴄᴛʙуй, ʍᴏй ʍиᴧый дᴩуᴦ, ᴋᴀᴋ ᴛы ᴄᴇбя чуʙᴄᴛʙуᴇɯь?) нᴇ бᴏиɯьᴄя, чᴛᴏ ᴛʙᴏй нᴏʙый ɜнᴀᴋᴏʍый нᴇ ᴏбычный чᴇᴧᴏʙᴇᴋ.. хᴇхᴇ, нᴇ бᴏйᴄя, я ᴨᴩᴏᴄᴛᴏ ɯучу! Иᴄᴨуᴦᴀᴧᴄя? Ꮋу ччᴛᴏ wine club ᴛᴇᴨᴇᴩь ʍы ᴄ ᴛᴏбᴏй ᴄʙяɜᴀны ᴄᴀʍᴏй ᴋᴩᴏʙью и ᴨᴧᴏᴛью, ни чᴛᴏ нᴀᴄ нᴇ ᴩᴀɜᴧучиᴛ.. ᴛᴀᴋ ʙᴇдь? Ꭼᴄᴧи ᴛы ʍᴇня бᴩᴏᴄиɯь, ᴛᴏ бᴏйᴄя ᴨᴏᴄᴧᴇдᴄᴛʙий.. ɯучу! Ꮚучу! Инɸᴏ-@info_bsd_Roleyplay_flood Ꮧᴀйɸ-@bsd_1_2

12 Jul 2025, 09:27 UTC21 views3 reactionsread 13 August 2026
Photo

У нас с вами заключён первый союз. - с - 𝐄𝐱𝐪𝐮†𝐬𝐢𝐭𝐞 𝐒𝐭𝐚𝐫 Надеюсь, на то что обе стороны получат выгоду от Союза.

1🍓1🔥1

9 Jul 2025, 22:23 UTC31 views8 reactionsread 13 August 2026
Photo

Внимание у нас есть некоторые изменения в проекте "wine cloud" 1. Убрали как обязательный пункт в анкете личный канал. 2. Информация : день рождения, часовой пояс и канал в одном. 3. Поправлен пост о соролах, внесён с саморолами и теми кто ещё не определился/ждёт кого-то конкретного. 4. Правила и сюжет открываются с помощью тыка в навигаторе без баннера и места в инфо. В виде телеграф. 5. Норма и чистка под ним

3🔥3💋1💘1

7 Jul 2025, 10:29 UTC36 views0 reactionsread 13 August 2026
Photo

⬇️ 🔤🔤🔤🔤 🔤🔤🔤🎀⭐🎀 Я знаю, что прошлая игра вам довольно понравилась, и это не может не радовать! ^^ Итак. Правила игры на сегодня. Представим что мы с вами оказались в бесконечном поезде. Что-то вроде аномалии, многие друг друга не знают, или знают о других очень мало. Чтобы выжить мы с вами должны закрепить знания друг о друге и не дать существам из вне нас обмануть. Сначало отвечаем на вопросы и предполагаем

5 Jul 2025, 17:11 UTC32 viewsread 13 August 2026
Photo

Наша игра оконченна. На голосование был выбран - Гоголь и он был мирным. Победили предатели. Мори и Коё. Умерли так два предателя - Поль и Чуя. Остальные были мирными изначально.

5 Jul 2025, 16:58 UTC39 viewsread 13 August 2026

Элис находилась в медпункте недалеко от Шибусавы. Её убили. Возможно Шибу видел кто это сделал.

5 Jul 2025, 16:53 UTC38 viewsread 13 August 2026

В ходе голосования, был выбран Артюр Рембо! Как оказалось позднее он не был предателем. Зато убитый Поль Верлен, был предателем. Погибших 3. Чуя, Поль, Рембо

Showing the 12 most recent of 15 posts we hold for @bsd_1_2. 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 — 1,385,118 of 1,550,220entries 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

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.

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.

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.

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

“ᴾᵒˢᵗᶦᶰᵍ"ᴡɪɴᴇ ᴄʟᴜᴅ,,🥤” (@bsd_1_2), 4 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/bsd_1_2.

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.