Telegram RegisterThe public register of Telegram
Telegram profile photo for Musor

Channel

Musor

@musorsupport

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry

34,406subscribers

+34,171 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1004447304710
TypeChannel
Username@musorsupport
Descriptionmusor.win
Created28 July 2026 — measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live15 November 2026
Measurements held54
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/musorsupport

Topic

Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 83% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

23541,28920,7626 August 2026 — 235 subscribers7 August 2026 — 235 subscribers7 August 2026 — 249 subscribers14 August 2026 — 559 subscribers22 August 2026 — 5,995 subscribers25 August 2026 — 15,139 subscribers26 August 2026 — 20,690 subscribers27 August 2026 — 24,400 subscribers28 August 2026 — 26,864 subscribers29 August 2026 — 28,964 subscribers30 August 2026 — 31,361 subscribers31 August 2026 — 34,290 subscribers1 September 2026 — 36,556 subscribers2 September 2026 — 38,013 subscribers3 September 2026 — 38,898 subscribers4 September 2026 — 39,748 subscribers7 September 2026 — 41,289 subscribers10 September 2026 — 40,938 subscribers12 September 2026 — 40,911 subscribers14 September 2026 — 41,005 subscribers15 September 2026 — 40,981 subscribers17 September 2026 — 39,762 subscribers29 September 2026 — 38,769 subscribers5 October 2026 — 38,269 subscribers9 October 2026 — 37,829 subscribers13 October 2026 — 37,487 subscribers14 October 2026 — 37,381 subscribers16 October 2026 — 37,258 subscribers17 October 2026 — 37,157 subscribers18 October 2026 — 37,040 subscribers19 October 2026 — 36,912 subscribers20 October 2026 — 36,830 subscribers21 October 2026 — 36,753 subscribers22 October 2026 — 36,630 subscribers23 October 2026 — 36,566 subscribers24 October 2026 — 36,490 subscribers25 October 2026 — 36,367 subscribers26 October 2026 — 36,290 subscribers27 October 2026 — 36,192 subscribers28 October 2026 — 36,096 subscribers29 October 2026 — 36,005 subscribers30 October 2026 — 35,906 subscribers31 October 2026 — 35,810 subscribers1 November 2026 — 35,720 subscribers2 November 2026 — 35,628 subscribers3 November 2026 — 35,479 subscribers4 November 2026 — 35,416 subscribers5 November 2026 — 35,294 subscribers6 November 2026 — 35,203 subscribers7 November 2026 — 35,091 subscribers8 November 2026 — 34,973 subscribers10 November 2026 — 34,828 subscribers12 November 2026 — 34,641 subscribers15 November 2026 — 34,406 subscribers34,4066 August 202615 November 2026
54 measurements spanning 101 days, net +34,171. 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”.
Measurement log — every subscribers count we have recorded, most recent 20 of 54
Measured (UTC)SubscribersChange
15 Nov 2026, 22:0534,406-235
12 Nov 2026, 12:0934,641-187
10 Nov 2026, 06:4134,828-145
8 Nov 2026, 21:5634,973-118
7 Nov 2026, 11:0735,091-112
6 Nov 2026, 12:3935,203-91
5 Nov 2026, 11:5535,294-122
4 Nov 2026, 11:4035,416-63
3 Nov 2026, 15:0535,479-149
2 Nov 2026, 13:1035,628-92
1 Nov 2026, 15:4535,720-90
31 Oct 2026, 17:3535,810-96
30 Oct 2026, 15:3135,906-99
29 Oct 2026, 16:5536,005-91
28 Oct 2026, 14:4436,096-96
27 Oct 2026, 15:5536,192-98
26 Oct 2026, 15:0636,290-77
25 Oct 2026, 15:1636,367-123
24 Oct 2026, 12:3636,490-76
23 Oct 2026, 12:1036,566first reading

Engagement

29 posts held, back to 28 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 160 pages of 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 29 posts for this entry, the most recent from 16 September 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
1

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

5,881 reactions across 28 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤5,881100.0%

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

Measured over the 29 most recent posts we hold, published 28 July 2026 to 16 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

16 Sept 2026, 13:18 UTC≈30,200 views258 reactionsread 17 November 2026
Forwarded from @musor_tiktok

📢 Обновили оплату за контент Мы снизили оплату за cs2 контент. 🎮 CS2-контент • 1 000 просмотров — $0.7 • 100 000 просмотров — $70 • 1 000 000 просмотров — $700 👨‍🎨 Не CS2-контент • 1 000 просмотров — $0.25 • 100 000 просмотров — $25 • 1 000 000 просмотров — $250 👩‍🎨 Креативы (даже если вставлен баннер) • 1 000 просмотров — $0.1 • 100 000 просмотров — $10 • 1 000 000 просмотров — $100

❤258

8 Sept 2026, 10:04 UTC≈52,000 views387 reactionsread 17 November 2026
Forwarded from @musor_tiktok

📢 Обновили оплату за контент Мы снизили оплату за cs2 контент. 🎮 CS2-контент • 1 000 просмотров — $1 • 100 000 просмотров — $1000 • 1 000 000 просмотров — $1 000 👨‍🎨 Не CS2-контент • 1 000 просмотров — $0.3 • 100 000 просмотров — $30 • 1 000 000 просмотров — $300 👩‍🎨 Креативы (даже если вставлен баннер) • 1 000 просмотров — $0.1 • 100 000 просмотров — $10 • 1 000 000 просмотров — $100

❤387

27 Aug 2026, 22:16 UTC≈120,000 views759 reactionsread 17 November 2026

Если вы считаете, что баннер испортит видео и видео или звук и так про нас - можно не вставлять баннер, но не злоупотребляйте этим, если на видео все таки можно установить баннер и смысл видео от этого не изменится - вставляйте, удачной работы и приятных съемок! Если видео не креативное баннер обязателен, это относится только к креативным роликам! мы значительно ускорили проверку видео и выплат, скоро это будет еще…

❤759

25 Aug 2026, 11:46 UTC≈135,000 views568 reactionsread 17 November 2026

Для начала сотрудничества Вы должны: 1) Прочитать все правила в @musorsupport 2) Скачать баннер тут @musor_tiktok 3) Начать выкладывать видео P.S. СПРАШИВАТЬ РАЗРЕШЕНИЕ НИ У КОГО НЕ НУЖНО, НАЧИНАТЬ МОЖНО С НУЛЕВЫХ АККАУНТОВ.

❤568

25 Aug 2026, 10:54 UTC≈127,000 views475 reactionsread 17 November 2026

Теперь минимальный порог для получения выплаты - 30000 просмотров, отправленные до изменения правил примутся от 5000 просмотров

❤475

24 Aug 2026, 07:28 UTC≈134,000 views456 reactionsread 17 November 2026

🔥 Дополнительные выплаты за игровой контент Если вы снимаете, как играете в Upgrade или открываете кейсы, выплата увеличивается в 3 раза! P.S. Играть можно только на сайте MUSORDROP - musor1.win 🎮 Это будет считаться за CS2-контент — $4.50 за 1 000 просмотров Важно: мы не выдаём фантики для съёмок — вы должны играть на свои деньги.

❤456

23 Aug 2026, 10:44 UTC≈123,000 views301 reactionsread 17 November 2026

Дорогие друзья. Мы с командой приняли решение что принимать Ваши видео будем с 12:00 до 21:00 по МСК , после этого времени личные сообщения будут закрыты. Это будет сделано для более оперативной работы и быстрой проверки Ваших видео. Единственная кто выдает выплаты - @vip_musor

❤301

23 Aug 2026, 01:30 UTC≈115,000 views371 reactionsread 17 November 2026

Баннер теперь можно ускорять до 1.4х по скорости Ждем от Вас результатов львы и львицы❤️ Единственная кто выдает выплаты - @vip_musor

❤371

22 Aug 2026, 15:14 UTC≈115,000 views72 reactionsread 17 November 2026

Поддержка - @musor_support Выплаты - @vip_musor

❤72

22 Aug 2026, 09:54 UTC≈115,000 views116 reactionsread 17 November 2026

ВАЖНАЯ ИНФОРМАЦИЯ!‼️‼️‼️ Ваши TikTok и Shorts видео подавайте теперь на аккаунт данного саппорта! @vip_musor @vip_musor @vip_musor Те кто подавал заявки на выплату - переподавайте на @vip_musor

❤116

22 Aug 2026, 02:17 UTC≈106,000 views124 reactionsread 17 November 2026

Запись статистики принимается теперь строго с телефона.

❤124

21 Aug 2026, 20:29 UTC≈105,000 views97 reactionsread 17 November 2026

Поданные видео на модерацию оплачиваются по 0.5$ Кто не успел подать - 0.3$

❤97

Showing the 12 most recent of 29 posts we hold for @musorsupport. 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.

Posts edited after publishing

@musorsupport edited 3 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
4 September 2026
Most recent edit
8 September 2026

Posts recorded as deleted after publishing

We recorded 1 post on @musorsupport as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
26 August 2026
Most recent seen missing
26 August 2026
Median time before seen missing
7 days
Seen missing in the last 30 days
0

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.

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

“Musor” (@musorsupport), 34,406 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/musorsupport.

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.