Telegram RegisterThe public register of Telegram
Telegram profile photo for [MSC] Team* Moscow Lineage 2

Channel

[MSC] Team* Moscow Lineage 2

@MSCstream

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

9subscribers

+0 since we began measuring on 24 October 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003952872541
TypeChannel
Username@MSCstream
DescriptionЗалетайте на стрим старой доброй L2 Ламповая атмосфера с нашим кланом!
CreatedBetween 1 April 2026 and 17 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded24 October 2026
Last confirmed live31 October 2026
Measurements held2
On Telegramt.me/MSCstream

Growth

924 Oct 2026, 02:47 — 9 subscribers24 Oct 2026, 03:22 — 9 subscribers24 Oct 2026, 02:4724 Oct 2026, 03:22
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 8–10 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Oct 2026, 03:229no change
24 Oct 2026, 02:479first reading

Engagement

16 posts held, back to 17 May 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 1 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
5975.9%
avg views ÷ 9 subscribers
Avg views / post
538
6 posts measured
Reaction rate
0.098%
reactions ÷ views · ER floor
Posts in window
10
of 16 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. It is computed over the 2 of 6 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 23 October 2026
Posts held16 (17 May 2026 – 23 October 2026)
Views total3,227
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken24 Oct 2026, 03: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.

What this channel posts

Photos
9
Videos
2
Links
2

Lifetime counters from Telegram’s own channel header, read 24 October 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
34s
Average length
34s

Measured directly from 1 video 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

3 reactions across 2 posts, in 3 distinct kinds. The most used accounts for 33.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤133.3%
🍾133.3%
👍133.3%

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

Measured over the 16 most recent posts we hold, published 17 May 2026 to 23 October 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

23 Oct 2026, 12:47 UTC13 views2 reactionsread 24 October 2026

Почему вам нужно стартовать с нами⁉️ Ответ прост: ✅Самая дружная команда ребят, поддержат подскажут в любую секунду ✅Честная дележка по дропу. Каждый получит равную часть ✅Мы не прыгаем по серверам, задерживаемся на долго, пускаем корни и развиваем клан. Если ты ещё не с нами пиши - @moscow378

❤1🍾1

23 Oct 2026, 06:22 UTC≈3,060 views1 reactionsread 24 October 2026
Photo

🔥 РОДИНА | ВоН ПТС x20 | СКОРО СТАРТ! 🔥 Совсем скоро открытие ВоН ПТС x20 — и мы врываемся в игру! ⚔️ Биг вар, драки за споты, эпики и море эмоций в компании опытных игроков. Ищем тех, кто хочет играть командой и добиваться результата! 🔥 ВЕДЁМ ДОБОР В: ⚔️ Глад-пак 🛡️ Стоп-пак 🔮 Маг-пак 🏹 Луко-пак Ждём готовые КП, полупаки и соло-игроков. У нас стабильный, дружный и адекватный коллектив! 📩 Пиши: @moscow378 РОДИН…

👍1

23 Oct 2026, 06:19 UTC73 viewsread 24 October 2026
Photo

🔥 РОДИНА | ВоН ПТС x20 | СКОРО СТАРТ! 🔥 Ну что, друзья, уже совсем скоро! 😈 Открытие долгожданного ВоН ПТС x20 — и мы врываемся показывать, что такое РОДИНА! ⚔️ Биг вар, драки за споты, эпики и море эмоций. Всё это в компании опытных ребят, которые знают, зачем собираются в пак и как добиваться результата. Хочешь прочувствовать всю прелесть командной игры? Тогда залетай к нам! Будем вместе фармить, дефать свои сп…

17 Oct 2026, 08:38 UTC27 viewsread 24 October 2026
Forwarded from @bohptsPhoto

⚡ Dark & Light | 20.11 | Interlude to High - Five 20-го ноября проект BoHpts.net вновь будет писать историю. Первый раз за всю историю проекта, будет открываться сразу 2 сервера с рейтами х20! Краткое описание: 🎥Открытие: 20 ноября 2026, 20:00 (UTC+3) 🎥Хроники: Interlude с плавным переходом на High Five 🎥Окна: 2+1 (при наличии ПА) — возможны изменения 🎥Клиент: Salvation или Samurai (Main Version) — на выбор ⚔️Гл…

10 Oct 2026, 16:10 UTC24 viewsread 24 October 2026

Как же круто пацаны подходят к работе! Молодцы же не? П. С. Нет нет)) мы продолжаем игру на Вон ПТС))

23 Jul 2026, 16:19 UTC30 viewsread 24 October 2026
Photo

Вчера подрались за епики, но варов оказалось чуть чуть больше. В любом случае АК за нами 💪🏻 Сегодня выйдем уже с другими мыслями, и настроением!

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

Forward network

Republished by

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

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.

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

“[MSC] Team* Moscow Lineage 2” (@MSCstream), 9 subscribers as measured 24 October 2026. Telegram Register, tgregister.com/channel/MSCstream.

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.