. ᯏ𓂃 › ›SɆT TØ ᑕᕼᗩ₮.ׅ ׁ .ׅ ׁ .֗ .ׅ ׁ НАБОР В ЧАТ .֗ .ׅ ׁ GØᒪᗪEᑎ GᗩᖇĐɆᑎ.ׅ ׁ .ׅ ׁ 32/60 как попасть на нашу вечеринку? все очень просто! отправьте запрос нашему владелецу->> @BrightHaven_bot на нашей вечеринке действует возрастное ограничение 14+ шаблон для запроса:: 1.желаемая роль+ бронь|вступ 2. дата рождения 3. ваш юзернейм 4. подписки на лайф и инфо обязательны 5. короткие ответы…

Channel
ᵐᵉᶫᶫᵒʷᗷᖇIGᕼ₮ ᕼᗩᐯɆᑎ||IᑎᖴO
@mellInfoBH
On this record: Previous handles · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
290subscribers
+8 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002624388489 |
|---|---|
| Type | Channel |
| Username | @mellInfoBH |
| Created | 14 April 2025 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/mellInfoBH |
Previous handles
@mellInfoBH was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
held 8 August 2026 – 8 August 2026
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 07:40 | 290 | -1 |
| 14 Sept 2026, 10:22 | 291 | no change |
| 14 Sept 2026, 09:47 | 291 | -5 |
| 29 Aug 2026, 14:42 | 296 | -1 |
| 23 Aug 2026, 13:36 | 297 | +16 |
| 15 Aug 2026, 05:23 | 281 | -1 |
| 8 Aug 2026, 08:32 | 282 | no change |
| 8 Aug 2026, 02:52 | 282 | first reading |
Engagement
21 posts held, back to 14 April 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 32.9%
- avg views ÷ 290 subscribers
- Avg views / post
- 95.4
- 10 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 10
- of 21 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.
| Window | Rolling 30 days · latest post in window 6 September 2026 |
|---|---|
| Posts held | 21 (14 April 2025 – 6 September 2026) |
| Views total | 954 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Sept 2026, 10:22 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
46 reactions across 10 posts, in 4 distinct kinds. The most used accounts for 47.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5357470741069603023 | 22 | 47.8% | |
| custom 5355075991859405420 | 12 | 26.1% | |
| custom 5357551941721301688 | 11 | 23.9% | |
| custom 5357271845429098469 | 1 | 2.17% |
Custom emoji. Every row above is a 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 10 of the 21 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 46 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 21 most recent posts we hold, published 14 April 2025 to 6 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.
Recent posts
ઇ𑠂 ׅ 𓈒 OɄᖇ SᕼØᑭ ֹ ᜔ ﹘ Заметили прекрасную вещицу на прилавке? Забирай её с радостью! Вас ждет-полезный ассортимент для вашего участия, низкие цены так и манят вас! Бот для покупки|> @shopBHbot ||> что такое тыковки? ||> ТОВАРЫ ||> посмотреть зачисления .ׅ ׁ .ׅ ׁ .֗ .ׅ БАЛАНС .֗ .ׅ ׁ.ׅ ׁ .ׅ ׁ Сяо:: 360 Кли:: 150 Ху Тао:: 150 Сандроне:: 450 Авантюрин:: 1.000 ཐི ׁ ۪ ⊹ ۫ ࣭ …
⭑ׅ ּ .֗ .ׅ ׁ── .ׅ GᗩᗰɆS .ׅ ── .ׅ ׁ .ׅ ׁ ⭑ּ .֗ ||>КТО Я? ||>НЕВЕСТА ||>ТРУДНЫЙ ПЕРЕВОД ||>ИНТУИЦИЯ ||>ВЫБОР ЛИДЕРА ||>ПРАВДА ИЛИ ЛОЖЬ ||>МЕМОПИСАНИЕ ||>ПАЛИТРА ||>НАЙДИ ЛИШНЕГО ||>УГАДАЙ ГЕРОЯ ||>ПОЛЕ ЧУДЕС ཐི ׁ ۪ ⊹ ۫ ࣭ ❋࣭ ۫ ⊹ ׁ ۪ ཋྀ
. ᯏ 𓂃 › ›ᑌ₦łØᑎS.ׅ ׁ .ׅ ׁ .֗ .ׅ ׁ ROBIN:;: 19|25 || 1|10 PHAINON 22|22 || 2|10 ᡴꪫ . . ᯏ УСЛОВИЯ 𓂃 ꧦ 𝆹𝅥 › › ᒪIST Ø₣ ᑌᑎIOᑎS:: @UnionsBH ᗷØT ᖴØᖇ ᑌᑎIØᑎS:: @UnionsBH_bot пример для заявки:: 1. название в моно 2. ссылки на инфо и лайф 3. условия союза 4. ваш следящий 5. следящий с нашей стороны для сотрудничества присылайте письмо нашему боту! Письма принимаются с 12:00 по. 21:00 письма в лс или другого нашего бота…
ઇ𑠂 ׅ 𓈒 ᖇɆSTS ֹ ᜔ ﹘͟ ̵ ̵ . ᯏ 𓂃 › ›ᖇEST ᗷEᖴØᖇE .֗ .ׅ ׁ ||/Воскресенье до 18.09 ||/Весна до 18.09 ||/Алеша до 18.09 .֗ .ׅ ׁ ᗷᗩᑎᑎɆᗪ ᑌᑎ₮łᒪ.ׅ ׁ .ׅ ׁ ཐི ׁ ۪ ⊹ ۫ ࣭ ❋࣭ ۫ ⊹ ׁ ۪ ཋྀ
୭⊹ 𓂃 ᗩᗪᗰI₦łSTᖇᗩ₮łØᑎ 𓂃 ⊹ৎ ───────────────────── 𝆺𝅥 𝆭 . ° 𝆹𝅥𝆹𝅥 ⟡ . 𝆹𝅥 𝆭 ⊹ !! | 𝑅𝑂𝐵𝐼𝑁 | OwNeR | @BHownerbot принятие жалоб, слежка за чатом и каналами, принятие нью, следящий ¡¡| 𝑃𝐻𝐴𝐼𝑁𝑂𝑁 | Co-OwNeR |@wwinsenttt следит за каналами, принимает нью, монтажёр, следящий, проводит чистку, продавец !¡| 𝐴𝐿𝐼𝑂𝑆𝐻𝐴 | SenIoR ActIviSt |@k_1rix_s проводит интерактивы, помогает нью …
︵♡︵⏜︵୨ ୧︵⏜︵♡︵ 𝐿𝐼₴S₮ Ø𝐹 𝑅Ø𝐿𝐸S 𝐻OᑎKᗩ𝐼 S₮ᗩ𝑅 𝑅ᗩ𝐼𝐿 🤩занято– 👌 🤩бронь– 🤩 🤩свободно– ЗВеЗДнЫЙ ЭКсПРеСс Вельт– Дань Хэн– Март 7–👌 Химеко– КоСМиЧЕСКаЯ СТАнЦИя "ГЕРТА" Аста– Арлан– Великая Герта– Герта– Жуань Мэй– БеЛоБОг Броня– Гепард – Зеле– Клара– Лука– Наташа– Пела– Рысь– Сампо– Хук– Сервал– АлЬяНс СяНЬчЖоУ Байлу– Гуйнайфэй– Дань Хэн(Пожиратель луны)– Линша– Лоча— Моцзэ— Сушан— Сюзи— Тиньюнь…
︵♡︵⏜︵୨ ୧︵⏜︵♡︵ 𝐿𝐼S₮ Ø𝐹 𝑅Ø𝐿𝐸S ₲𝐸ᑎS𝐻𝐼𝒩 𝐼𝑀₱ᗩᑕT 🤩занято– 👌 🤩бронь– 🤩 свободно– МоНДштаДТ Джинн— Лиза— Кли—👌 Фишль— Эмбер— Барбара— Мона—👌 Ноэлль— Розария— Сахароза— Диона— Эола— Дилюк— Кейа— Беннет- Дурин— Варка— Альбедо— Рейзор— Далия— Тома— Лоэн—👌 Ли Юэ Бэй Доу— Нин Гуан— Кэ Цин— Лань Янь— Ху Тао— Ци Ци— Гань Юй— Шэнь Хэ— Юнь Цзинь— Янь Фэй— Яо Яо— Е Лань— Ху Тао—👌 Цзы Бай— Бай Чжу— Ка М…
Photo, posted without a caption
ཐི ׁ ۪ ⊹ ۫ ࣭ ❀ ۫ ⊹ ׁ ۪ ཋྀ ₦ᗩ𝘝𝐼₲ᗩTIOᑎ ⭑ׅ ּ 𝐼𝑀₱Ø𝑅Tᗩᑎ₮ 𝐼ᑎ𝐹Ø𝑅𝑀ᗩTIOᑎ .֗ 〣 ,, ꒰ Ɽᑌ𝐿𝐸S 𝑅O𝐿𝐸S ₲.𝐼 // 𝐻S𝑅 ᗩᗪᗰI₦𝐼ST𝑅ᗩTIOᑎ 〣 ,, ꒰ S𝐸T . ࿐𝇄 ׄ 𝅄 ▸ ⭑ׅ ּ .Ø𝑅ⱧɆ𝑅 𝐼ᑎ₣Ø𝑅𝑀ᗩTIOᑎ .֗ ׁ ⭑ּ . ࿐𝇄 ׄ 𝅄 ▸ ₲ᗩ𝑀ɆS ᑌ₦𝐼ОᑎS 〣 ,, 𝐵𝐼𝑅₮𝐻ĐᗩYS ⊹ ۫ ࣭ 𝑅𝐸STS ۫ ⊹ S𝐻ØP ཐི ׁ ۪ ⊹ ۫ ࣭ ❀ ۫ ⊹ ׁ ۪ ཋྀ 𝑖𝑛𝑖𝑡𝑖𝑎𝑙𝑠:: #฿𝐻 …
🥩🥩𝘚𝘌𝘛 𝘛𝘖 𝘊𝘏𝘈𝘛🥩🥩 НАБОР В ЧАТ:: 𝘎𝘰𝘭𝘥𝘦𝘯 𝘎𝘢𝘳𝘥𝘦𝘯 31|60 открыт Как пройти через снежные ворота? все очень просто! отправьте письмо нашему почтальону— @BrightHaven_bot в нашем флуде действует возрастное ограничение 14+ учитывайте это при подаче письма. шаблон для подачи письма:: 1. желаемая роль+бронь|вступ 2. дата рождения 3. ваш юзернейм 4. подписки на лайф и инфо обязательны 5. короткие ответы на вопросы: А. как…
custom 53574707410696030233custom 53550759918594054201custom 53575519417213016881
🥩🥩𝘖𝘜𝘙 𝘚𝘏𝘖𝘗🥩🥩 Желаете приобрести классные вещички? заходи в нашу ледяную лавку! Вас ждет—полезный ассортимент для вашего участия и низкие цены! Бот для покупки–° @shopBHbot •~Что такое сноугрифы? •~Товары •~Посмотреть зачисления 🤩🤩🤩🤩🤩🤩 Баланс участников 𝘎𝘖𝘓𝘋𝘌𝘕 𝘎𝘈𝘙𝘋𝘌𝘕 Скарамучча:: 830 Сяо:: 360 Кли:: 150 Ху Тао:: 150 Сандроне:: 450 Авантюрин:: 1.000 Яо Гуан:: 200 𝘈𝘋𝘔𝘐𝘕𝘐𝘚𝘛𝘙𝘈𝘛𝘐𝘖𝘕 Царица:: 12.100 Флинс:: …
custom 53574707410696030232custom 53550759918594054201custom 53575519417213016881
Showing the 12 most recent of 21 posts we hold for @mellInfoBH. 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.
Mentions
Named by 15 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.
Named by
Channels on the register whose posts name this channel's handle.
@amesuni · 71 post𝖀𝐍𝐈𝕺𝐍𝕾 || 𝐁𝐍𝐍𝐎𝟕
@bnnosevunions · 221 post🔒. 𝗘𝘃𝗲𝗿𝘄𝗶𝗹𝗱 [𝗟𝗜𝗙𝗘] .
@EverwildLife · 1131 post「 𝐂𝐥𝐨𝐬𝐞𝐝 」14+ || 𝙻𝙸𝙵𝙴 || ᅠ⃟ ⃟🍷⫶𝗘𝗩𝕴𝗟 𝗖𝕬𝗧 𓏼˙₊ || #𝙴𝚅𝙻
@EVL_LIFE · 1271 post𝐔.ۨ𝐍ۧ𝐈ۜ𝐎𝐍۪𝐒 𝐄.ۨ𝐕ۧ𝐎ۜ𝐈𝐑۪𝐄
@evorAMOR · 111 post𝙞𝙣𝙛𝙞𝙣𝙞𝙩𝙮'𝙨 𝙡𝙚𝙜𝙖𝙘𝙮 // life
@finitysleg · 3631 post˖ ֹ˗ˏˋ𝕲𝓸𝓽𝓽𝓪𝓭𝓸𝓻𝓾 ִ´ˎ˗ ࣪«𝟏𝟐+»
@GottoDoru · 6421 post𝗛𝗔𝗧𝗥𝗘𝗗ᵘⁿⁱᵒⁿˢ
@HDR_unions · 81 post𝐊𝐎𝐑𝐃𝐇𝐄𝐋𝐋 𝐔𝐍𝐈𝐎𝐍𝐒
@Kordhell_unions · 111 post[closed] 𝗯𝗲𝗿𝗹𝗶𝗴𝗵𝘁 𝗹𝗶𝗳𝗲.
@lifeberlight · 651 post|𝑳𝑰𝑭𝑬| 𝑴𝒐𝒐𝒏 𝑪𝒉𝒂𝒓𝒕 𝑭𝒍𝒐𝒐𝒅
@LIFEMoonChartFlood · 531 post• ^'| храм Квёпл |°•
@lqw0wpl · 1621 post𝗹𝗼𝗻𝗲’𝘀 𝘂𝗻𝗶𝗼𝗻𝘀
@pantalones_unions · 31 post𝗕𝗿𝗶𝗴𝗵𝘁 𝗛𝗮𝘃𝗲𝗻|𝗨𝗻𝗶𝗼𝗻𝘀
@unionsBH · 31 postᴜɴɪᴏɴs 𝐐-𝐒𝐈𝐍𝐆𝐔𝐋𝐀𝐑𝐈𝐒
@unionsQ_SIN · 101 post
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.
Handles this channel named that no longer answer
- Dead references
- 2
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 1
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@mellInfoBH named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
named in 1 post, 9 August 2026 – 9 August 2026 · confirmed gone 13 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 9 August 2026 – 9 August 2026
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“ᵐᵉᶫᶫᵒʷᗷᖇIGᕼ₮ ᕼᗩᐯɆᑎ||IᑎᖴO” (@mellInfoBH), 290 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/mellInfoBH.
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.