Telegram RegisterThe public register of Telegram

Channel

•𝙈𝙪 𝘽𝙖𝙗𝙖𝙪"ᶜᵒˢᵖˡᵃʸ" >×<

@MUBABAUU

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

272subscribers

+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-1002277411236
TypeChannel
Username@MUBABAUU
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 7 August 2026
On Telegramt.me/MUBABAUU

Growth

271272271.57 Aug 2026, 03:03 — 271 subscribers7 Aug 2026, 15:37 — 272 subscribers7 Aug 2026, 03:037 Aug 2026, 15:37
2 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 271–272 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 15:37272+1
7 Aug 2026, 03:03271first reading

Engagement

18 posts held, back to 26 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
98.8%
avg views ÷ 272 subscribers
Avg views / post
269
6 posts measured
Reaction rate
11.3%
reactions ÷ views · ER floor
Posts in window
6
of 18 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 4 August 2026
Posts held18 (26 June 20264 August 2026)
Views total1,612
Reactions total182
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 03:03 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

603 reactions across 18 posts, in 27 distinct kinds. The most used accounts for 19.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 518829440593667528611519.1%
8714.4%
custom 52962778337425910497612.6%
custom 5296780289081648188538.79%
🏆315.14%
custom 5312259114993231275294.81%
custom 5296309251428361706284.64%
custom 5327980679571482200284.64%
custom 5242262503961947418254.15%
💔162.65%
custom 5285365666168215964152.49%
custom 5242539701151233647142.32%
🎉142.32%
custom 5451888841088596737111.82%
custom 5309809029424378170101.66%
custom 5336957917134351876101.66%
custom 523995224105343161681.33%
81.33%
custom 528100777330635471771.16%
custom 542280792676502962760.995%
7 further kinds121.99%

Custom emoji. 15 of the rows above are 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 areTelegram’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 18 of the 18 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 603reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 26 June 2026 to 4 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.

Telegram Stars

Stars received
20
across the posts below
Posts paid on
1
of 18 we hold a reading for · 6%
Most on one post
20
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @MUBABAUU. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 18 most recent posts we hold for this entry, published 26 June 2026 to 4 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

4 Aug 2026, 12:50 UTC75 views22 reactionsread 7 August 2026
Video message

Video message, posted without a caption

custom 533695791713435187610custom 54518888410885967376custom 51882944059366752862custom 542280792676502962721custom 52963150324543423331

3 Aug 2026, 11:19 UTC103 views33 reactionsread 7 August 2026
Photo

: 🔤[🪻] 🔹рупповая депрессия отменяется, у Бабая заявку приняли на Сусукон 🙈😏🔤 #МиБабайЛох🤩

custom 5188294405936675286177custom 54518888410885967375custom 54228079267650296274

30 Jul 2026, 08:48 UTC191 views13 reactionsread 7 August 2026

С днем рождения Лисёну!!🤩

112

26 Jul 2026, 15:50 UTC297 views24 reactionsread 7 August 2026

:🔤➖ука мои дорогие, рассказываем что да как было на Банкай×Томодачи и что я упустил не поехав🤩🤩🔤 Я жалею очень #МиБабайЛох😀

💔16custom 529678028908164818843custom 51882944059366752861

22 Jul 2026, 14:56 UTC386 views32 reactionsread 7 August 2026

: 🔤Простите, извините Бабая за не актив , я проста в дубаях своих ахуел совсем🤩🤩🔤 Буду признателен реакциям🥺 (Дада ахуел)👀 ➖➖🔤➖➖ #МиБабайЛох🤩

custom 529627783374259104914custom 52967802890816481888🏆6custom 531225911499323127521custom 51882944059366752861

22 Jul 2026, 14:00 UTC560 views58 reactionsread 7 August 2026
Photo

🤩😄🌟🔤➖➖➖➖➖🙂😄👀 🖤🖤🤩🔡➖➖🤩🤩🖤🖤 💠🌟🌟🌟🌟🌟🤩🤩🤩🧷🌟🏴 😄🤩 - 🤩ы убил твиксела! 😞ᵗᵐ 🖤- Oн хотел уничтожить меня 😄🖤 - 🤩н был моим другом. 🤩🤩 — 🔹 Я РАЗВЕ НЕ ТВОЙ ДРУГ?! Но ты вернулся..🤩 Никто не возвращался. Ты хоть представляешь что это значит для меня? Это многое значит ведь я жил больше 100 лет . Я Не просил чтоб меня создали..К черту..Я не просил этим стать. И ПОТЕРЯТЬ ВСЕХ НИКОГДА 😄🖤ThatMobʸᵘʳⁱ 🤩Verityᵗ

custom 52962778337425910492116custom 529630925142836170611custom 51882944059366752864custom 529678028908164818831🏆1custom 53122591149932312751

11 Jul 2026, 17:40 UTC387 views24 reactionsread 7 August 2026

: 🔤Подробности и контент от туда скоро.🍓🔤 #МиБабайЛох ☺️

custom 518829440593667528695custom 52967802890816481885🏆2custom 52962778337425910492custom 53122591149932312751

11 Jul 2026, 17:39 UTC381 views41 reactionsread 7 August 2026

: 🔤➖так. Что вам сказать. Бабай покорил Пятигорск и забрал первое место на одиночном дефиле😳🔤 #МиБабайЛох 😚

custom 518829440593667528615🏆128custom 52962778337425910494custom 52967802890816481882

9 Jul 2026, 17:18 UTC455 views42 reactionsread 7 August 2026
Photo

: 🔤🔤авайте пока Бабай пишет пост, представим что он не навоздуханил и не пропал на 4 дня 🤩🤩🤩 🔤 😄#МиБабайЛох😄

custom 529627783374259104920custom 529630925142836170687🏆3custom 51882944059366752862custom 52967802890816481882

5 Jul 2026, 09:38 UTC361 views22 reactionsread 7 August 2026

: 🔤➖езумно благодарен всем кто помогал мои дорогие!⭐️⭐️🔤 #МиБабайЛох🤩🤩

custom 5188294405936675286145🏆3

5 Jul 2026, 09:36 UTC309 views29 reactionsread 7 August 2026
Forwarded from @GoodKosKm

Итоги интерактива! Обьявляем победителя В тяжёлой схватке За понравившийся косплей Побеждает:МИ БАБАЙ Набрав 169 реакции! Примечание: это первый и последний раз когда засчитываем премиум Реакции в следующих Активностях премиум засчитывается не будет 1 человек = 1 реакция Так будет честно.

custom 5188294405936675286167🏆3custom 52962778337425910492custom 52963092514283617061

1 Jul 2026, 16:36 UTC436 views24 reactionsread 7 August 2026
Video message

Video message, posted without a caption

custom 529678028908164818814custom 52962778337425910494custom 52963092514283617064custom 53122591149932312752

Showing the 12 most recent of 18 posts we hold for @MUBABAUU. 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 — 223,728 of 1,176,251entries 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 5 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.

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

“•𝙈𝙪 𝘽𝙖𝙗𝙖𝙪"ᶜᵒˢᵖˡᵃʸ" >×<” (@MUBABAUU), 272 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/MUBABAUU.

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.