Telegram RegisterThe public register of Telegram

Channel

MUMU | СЕТКА ♪

@mumuset

On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

63subscribers

+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-1002009932817
TypeChannel
Username@mumuset
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/mumuset

Growth

6312 Aug 2026, 21:46 — 63 subscribers12 Aug 2026, 21:58 — 63 subscribers12 Aug 2026, 21:4612 Aug 2026, 21:58
2 measurements taken within a single 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 62–64 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 21:5863no change
12 Aug 2026, 21:4663first reading

Engagement

20 posts held, back to 23 August 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 20 posts for this entry, the most recent from 9 September 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

46 reactions across 12 posts, in 12 distinct kinds. The most used accounts for 23.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1123.9%
custom 53998670933928301771021.7%
🍓510.9%
🕊510.9%
custom 520889296600906478524.35%
custom 545396984723277977624.35%
🍾24.35%
🎉24.35%
👍24.35%
💘24.35%
🔥24.35%
😨12.17%

Custom emoji. 3 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 12 of the 20 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 46reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 23 August 2025 to 9 September 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

9 Sept 2025, 19:12 UTC200 views2 reactionsread 12 August 2026

🦌: Спешим вам сообщить, что для всеобщего удобства была создана папка со всеми каналами. Папка будет пополняться при новых приходах. ❌А так же теперь, если у вас есть какой либо вопрос или жалоба, то вы можете написать всё в специального бота, а администрация ответит вам в ближайшее время! С нетерпением ждём ваших анкет! 💭

2

9 Sept 2025, 13:23 UTC193 viewsread 12 August 2026
Forwarded from @ohhmSTLOVEEEEPhoto

🎮🌟 〰️🌟🌟lcome to . 🔘 🌟 🐇 фд осд любят ! 🌟 𝆹𝅥‌ 𝆺𝅥 🌟🌟 . ‌ ⏝ ‎ ׄ ʾʿ ❲ 🌟 : ❤️не так нравится наблюдать за контентом этого художника ! 🤩 🌟 : 🤍 я бы хотел ( а ) поделиться мнением о своём любимом пейринге, без осуждений !! 🤩 поделись же своей любовью с нами. ㅤ 🎉 ࣭ administration : 🌟 hackeromantik . ‹‹ 🌟 . she / they fell /

9 Sept 2025, 07:57 UTC126 viewsread 12 August 2026
Forwarded from @yokunerukocfPhoto

➿➿➿ · · 🌟🤩🌟· · ➿➿➿ > искали канал, посвящённый такому уталоиду, как Руко? > хочется шарить за все войсбанки в мире? > может, хотите поделиться своими идеями и находками с единомышленниками? 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 🌟🌟🌟🌟 🌟🌟🌟🌟 🌟🌟🌟🌟🔠🤩🤍🎀🔡🤍 🌟🌟🌟🌟 🔤🔠🤍🤩 🌟🌟🌟🌟 🌟🌟🌟🌟 🤩🤍 & 🌟 🌟🌟🌟 🔡🤩🔠🌟🔡 🌟🌟🌟🌟🌟🌟🌟🌟 「Вп пост」 「Навигация」 「🎀: база + хейтеры руко」 Cr: Sierra_x0x on 🤩 & 🤩 ➿➿➿ · ·🌟🤩🌟· · ➿➿➿

9 Sept 2025, 07:46 UTC88 viewsread 12 August 2026
Forwarded from @misykxsPhoto

НАБОР В АДМ ПО ТЕЙКАМ любишь ру-реп, и люди тебя из-за этого считают фриком?😐 ➿➿➿➿➿➿➿➿➿➿➿➿ не с кем поделиться своей любимой песней? или написал свою песню и не знаешь с кем поделиться? ➿➿➿➿➿➿➿➿➿➿➿➿ хочешь рассказать про свою любимую группу?☦️ ➿➿➿➿➿➿➿➿➿➿➿➿ нашел малоизвестную группу и хочешь, чтобы о ней много кто узнал и ее форсили в тт?☦️ ➿➿➿➿➿➿➿➿➿➿➿➿ хочешь поделиться малоизвестной песней от популярной группы? ➿➿

9 Sept 2025, 06:12 UTC84 viewsread 12 August 2026
Forwarded from @RhythmGamesConfessionPhoto

ㅤㅤ𝗐𝗅𝖼𝗆 𝗍 . 𝗇𝖾𝗇𝖽o͟͞𝗋𝗈𝗂𝖽 𝖼𝗈𝗇𝖿𝖾𝗌𝗌𝗂𝗈𝗇 • 𝘣𝗈𝗍 𝟦 𝗍𝖺𝗄𝖾𝗌 ㅤ ﹠ㅤ 𝘮𝖺𝗂𝗇 𝗇𝖺𝗏𝗂𝗀𝖺𝗍𝗂𝗈𝗇

31 Aug 2025, 13:34 UTC114 views2 reactionsread 12 August 2026
Photo

❌👤 🎀ew 🎀haracter 🤩🤩🤩 ❌🔤rong, wrong, lock her away🤩 Mike Teavee is changing up the USA Майк создал свой канал! Давайте поддержим его своей подпиской! ❌ @MikeTeavee_MUMU ; @MikeTeavee_MUMU ; ❌❌❌❌🤍🤍🤍🤍🤍🤍 #new 🤩 @mumuset

custom 53998670933928301772

31 Aug 2025, 12:43 UTC159 views5 reactionsread 12 August 2026

⚠️Друзья, хотим торжественно сообщить, что сетка с 1 сентября переезжает в мессенжер Max! Max — это цифровая платформа, которую планируют развивать в VK на базе одноименного мессенджера. В дальнейшем компании смогут создавать свои мини-приложения на базе Max Bot API — например, финансовые сервисы, онлайн-магазины, меню для ресторанов, сервисы поддержки и т. п. У нового мессенджера удобный интерфейс, отличная синхро

🍾2custom 52088929660090647852😨1

27 Aug 2025, 18:07 UTC177 views2 reactionsread 12 August 2026
Photo

❌👤 🎀ew 🎀haracter 🤩🤩🤩 ❌🔤on't worry, don't worry,🤩🤩 ❌❌don't lose your head Анна Болейн создала свой канал! Давайте поддержим её своей подпиской! ❌ @anneboleyn_mumu ; @anneboleyn_mumu ; ❌❌❌❌🤍🤍🤍🤍🤍🤍 #new 🤩 @mumuset

🍓2

Showing the 12 most recent of 20 posts we hold for @mumuset. 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,048,563 of 1,169,250entries 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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

“MUMU | СЕТКА ♪” (@mumuset), 63 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/mumuset.

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.