Telegram RegisterThe public register of Telegram

Channel

MURA

@muramedia

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

19subscribers

+0 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-1001903999920
TypeChannel
Username@muramedia
CreatedBetween 1 March 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/muramedia

Growth

198 August 2026 — 19 subscribers11 August 2026 — 19 subscribers8 August 202611 August 2026
2 measurements spanning 3 days. 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 18–20 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 17:1619no change
8 Aug 2026, 10:0119first reading

Engagement

20 posts held, back to 3 February 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 22 April 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
70
Videos
17
Links
20

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

Video runtime
32s
Average length
11s

Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

56 reactions across 11 posts, in 10 distinct kinds. The most used accounts for 23.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1323.2%
1119.6%
🔥712.5%
🤡712.5%
👏610.7%
😁47.14%
💩35.36%
💯23.57%
🤣23.57%
🤝11.79%

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 11 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 56reactions 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 3 February 2025 to 22 April 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

22 Apr 2025, 12:46 UTC132 views1 reactionsread 11 August 2026

Неожиданно если честно Но приятно, что инфо про наш проект украшает метро Санкт-Петербурга

🔥1

22 Apr 2025, 12:46 UTC116 views3 reactionsread 11 August 2026
Forwarded from @m5mediafootballPhoto

🤩ГОРОДСКОЙ СУПЕРГЕРОЙ 🖼️Совершенно случайно вчера в метро обнаружился вот такой постер с упоминанием Максима и нашего турнира 📸Если вы тоже увидите такое во время своей поездки на метро, то немедленно отправляйте свои фотки и кружочки в комментарии #М5 #Northstein #FitGround #updowndesign #Росмолодёжь #РосмолодёжьГранты

🔥3

9 Mar 2025, 13:50 UTC187 views13 reactionsread 11 August 2026
Photo

👀Смотрю на реакции команд по поводу медийного стыка… Как же я их понимаю! 🤫Приоткрою завесу тайны - когда я накануне увидел ролики, сразу для себя выделил топ-4, в которые Харвест вообще никак не попадал. Для меня это было больно осознавать, учитывая сколько я лично приложил усилий для развития этой команды. Сейчас из-за проекта М5 я полностью передал все процессы парням, и занялся только турниром. И не принимал уча

👍64🤡2🤝1

25 Feb 2025, 11:05 UTC196 views13 reactionsread 11 August 2026

Задают вопрос по поводу Иксов Часто я сталкиваюсь с мнением, что мы не пустили их по каким-то обидам, недомолвкам, личному отношению или еще каким-то причинам, которые со стороны выглядят как целеноправленная неприязнь. ‼️И ЭТО ДЕЙСТВИТЕЛЬНО ТАК Наверное вот это хотят услышать люди, которые распространяют подобные мнения. Но на самом же деле все намного проще - Иксы не прошли отборочный этап, потому что понадеялис

5💩3🤡3🤣2

21 Feb 2025, 14:40 UTC136 viewsread 11 August 2026
Photo

⚡️Стрим прошел ⚡️Жеребьевку на. Event Cup провели ⚡️Готовимся качать людей на танцполе

16 Feb 2025, 16:32 UTC151 viewsread 11 August 2026
Video

👟⚽️Неожиданный удар Даже для меня самого😅

15 Feb 2025, 09:53 UTC138 views2 reactionsread 11 August 2026
Photo

😂Вот такой подарок от моей любимой жены ❤️Мы просто решили, что 14 февраля будет датой начала отношений И сейчас праздновали 6 лет 🕊А че вам подарили на День Святого Валентина?

😁2

14 Feb 2025, 09:03 UTC135 views7 reactionsread 11 August 2026
Video

"В тот же угол!" 🥅Третий удар в серии пенальти Ни любви ни тоски ни жалости @muramedia

💯2🔥2👍1👏1😁1

12 Feb 2025, 10:43 UTC571 views2 reactionsread 11 August 2026
Video message

Video message, posted without a caption

👍2

11 Feb 2025, 16:11 UTC171 viewsread 11 August 2026

Добрался я тут случайно до поста Валеры, и начал рассуждать… Сесть за стол переговоров… 📌 Кореша Мы в рамках проекта М5 устраиваем коллаборации с Ваней Брянцевым и Ваней Трутневым, а также делимся советами и опытом друг сдругом уже второй год. Вроде нормально разговариваем. 📌 ФЛДК Макс Сорокин, главный организатор ФЛДК-медиа, уже является членом орг.команды и важной частью объединения М5. Хватает у нас переговоров

9 Feb 2025, 17:19 UTC135 viewsread 11 August 2026

А гол в послематчевой серии пенальти считается?😅

Showing the 12 most recent of 20 posts we hold for @muramedia. 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,146,827 of 1,336,469entries 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 2 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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“MURA” (@muramedia), 19 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/muramedia.

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.