Channel
@MIST_PROJECT
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
212subscribers
+15 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003023603947 |
|---|---|
| Type | Channel |
| Username | @MIST_PROJECT |
| Created | 4 January 2026 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 8 August 2026 |
| On Telegram | t.me/MIST_PROJECT |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 19:22 | 212 | +15 |
| 8 Aug 2026, 11:35 | 197 | no change |
| 8 Aug 2026, 07:46 | 197 | first reading |
7 posts held, back to 4 January 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 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 7 posts for this entry, the most recent from 7 January 2026. An engagement rate over an empty window would be a number about nothing.
26 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 53.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤🔥 | 14 | 53.8% | |
| ❤ | 10 | 38.5% | |
| 🔥 | 2 | 7.69% |
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 6 of the 7 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 26reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 4 January 2026 to 7 January 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.
6.𝑆𝑌𝑆𝑇𝐸𝑀 𝑃𝑇𝑆 —При равном количестве pts-очков у команд, место в итоговой таблице определяется следующим образом: 𝑤𝑤𝑐𝑑|𝑝𝑙𝑎𝑐𝑒|𝑘𝑖𝑙𝑙𝑠 —Рехост катки делается в случае вылета|пинга у более 30% игроков. 𝑡𝑜𝑝 1–10 𝑝𝑡𝑠 𝑡𝑜𝑝 5–3 𝑝𝑡𝑠 𝑡𝑜𝑝 2–6 𝑝𝑡𝑠 𝑡𝑜𝑝 6–2 𝑝𝑡𝑠 𝑡𝑜𝑝 3–5 𝑝𝑡𝑠 𝑡𝑜𝑝 7,8–1 𝑝𝑡𝑠 𝑡𝑜𝑝 4–4 𝑝𝑡𝑠 𝑡𝑜𝑝 (8<)–0 𝑝𝑡𝑠 1 𝑘𝑖𝑙𝑙 = 1 𝑝𝑡𝑠 𝑆𝐶𝐻𝐸𝐷𝑈…
❤5❤🔥3
5.𝐼𝑁𝐹𝑂𝑅𝑀𝐴𝑇𝐼𝑂𝑁 𝑉𝐼𝑃-𝑆𝐿𝑂𝑇 —𝑉𝑖𝑝–𝑠𝑙𝑜𝑡𝑠: 21,22,23,24,25. (количество 𝑉𝑖𝑝–𝑠𝑙𝑜𝑡𝑠 на сессии-неограниченно, в зависимости от наличия свободных) —Разрешены игры в соло,дуо. —Команда, занесённая в бан-лист, при наличии 𝑉𝑖𝑝–𝑠𝑙𝑜𝑡, имеет право отыграть кастомные игры. —Разрешены игры 4 стаком от клана, если 3 стака в фри слотах. —Непосещение игр в приобретенном 𝑉𝑖𝑝–𝑠𝑙𝑜𝑡, не карается трехдневным баном. —Деньги, выплаченные за 𝑉𝑖𝑝–𝑠…
❤🔥3❤1
4.𝐼𝑁𝐹𝑂𝑅𝑀𝐴𝑇𝐼𝑂𝑁 𝐿𝑂𝐵𝐵𝑌 4.1. Минимальный уровень аккаунта — 40 lvl. 4.2. Организатор вправе менять расписание игр, заранее предупредив игроков на канале. 4.3. На сессии от клана|альянса кланов допускается 3 команды в 𝑓𝑟𝑒𝑒 слотах (исключение приобретение 𝑉𝑖𝑝–𝑠𝑙𝑜𝑡𝑠). 4.4. Команда должна состоять не менее, чем из 3 игроков (соло,дуо–кик, за исключением 𝑉𝑖𝑝–𝑠𝑙𝑜𝑡𝑠). 4.5. Исключение с лобби происходит по просьбе капитана сост…
❤🔥2❤1🔥1
3. 𝑇𝐸𝑀𝑃𝑂𝑅𝐴𝑅𝑌 𝐵𝐴𝑁, 𝑃𝐸𝑅𝑀𝐴𝑁𝐸𝑁𝑇 𝐵𝐴𝑁 —Поздний отказ(не менее чем за час)—трехдневный бан клану. —Отсутствие команды на 2|3,3|4—трехдневный бан клану. —При получении команды перманентного или трехдневного бана, администрация вправе не выдавать приз команде, получившей бан. —Грубые оскорбления участников игр, организаторов, администрации — перманентный бан. —Использование программ, не предусмотренных игрой — перманентный …
❤🔥2❤1
2.𝑅𝑈𝐿𝐸𝑆. —Запрещено неуважительное отношение к организаторам и Администрации – (Администрация вправе выдать наказание на свое усмотрение). —Запрещены в названии команды: оскорбительные слова, затрагивание наций, нецензурная лексика – (организатор имеет право не принять вашу регистрацию). —Запрещено занимать входные слоты, чужие слоты–(исключение перед стартом|исключение по просьбе владельца слота). В случае многокра…
❤2❤🔥2
⠀ Вас приветствует организация ⠀⠀⠀⠀⠀ «𝑀𝐼𝑆𝑇 𝑃𝑅𝑂𝐽𝐸𝐶𝑇» Каждая команда до игр обязана ознакомиться с правилами, перечисленными ниже. Незнание правил не освобождает от ответственности. 𝑅𝐸𝐺𝐼𝑆𝑇𝑅𝐴𝑇𝐼𝑂𝑁 𝐺𝐴𝑀𝐸𝑆 Регистрация на кастомные игры открывается ежедневно в 00:00 по московскому времени. Подача заявки на участие: 𝑡𝑒𝑎𝑚 𝑛𝑎𝑚𝑒 | @𝑡𝑔 𝑚𝑎𝑛𝑎𝑔𝑒𝑟 1.𝐼𝑁𝐹𝑂𝑅𝑀𝐴𝑇𝐼𝑂𝑁 1.1. Организатор в праве отказать в регистрации команды|клана…
❤🔥2🔥1
Channel created
Showing the 7 most recent of 7 posts we hold for @MIST_PROJECT. 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 — 879,096 of 1,345,403entries 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.
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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“𝑅𝐸𝐺𝐿𝐴𝑀𝐸𝑁𝑇 𝑀𝐼𝑆𝑇 𝑃𝑅𝑂𝐽𝐸𝐶𝑇” (@MIST_PROJECT), 212 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/MIST_PROJECT.
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.