Sticker, posted without a caption
Signed dm .ray

Channel
@mpclifs
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
98subscribers
+25 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003872854939 |
|---|---|
| Type | Channel |
| Username | @mpclifs |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/mpclifs |
Other / unclassifiable — 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 27 September 2026 and assigned it the closest of 31 fixed categories, at 74% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 19:54 | 98 | +6 |
| 9 Sept 2026, 10:19 | 92 | +2 |
| 1 Sept 2026, 02:08 | 90 | +13 |
| 24 Aug 2026, 10:46 | 77 | -1 |
| 16 Aug 2026, 15:14 | 78 | +5 |
| 9 Aug 2026, 22:16 | 73 | no change |
| 9 Aug 2026, 08:30 | 73 | first reading |
20 posts held, back to 6 August 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.
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 August 2026. An engagement rate over an empty window would be a number about nothing.
16 reactions across 10 posts, in 5 distinct kinds. The most used accounts for 31.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5994453058656931434 | 5 | 31.3% | |
| custom 5967688845397855939 | 4 | 25.0% | |
| custom 5924719252379537729 | 3 | 18.8% | |
| custom 5927052244254986343 | 2 | 12.5% | |
| custom 5942913498349571809 | 2 | 12.5% |
Custom emoji. Every row above is a 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 are Telegram’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 10 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 16 reactions 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 6 August 2026 to 9 August 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.
Sticker, posted without a caption
Signed dm .ray
ㅤㅤ ㅤ ㅤ⌨︎︎ 𝗆𝗉𝖼 · 𝗌𝗁𝗂𝗍𝗉𝗈𝗌𝗍 𝐃. 𝐑𝖺𝗍𝗂𝗈 — быстро поздравлять Анаксу в комментариях под постом выше. ЖивОоооОООО!!!!! С днем рождения лучшего владельца🎉
custom 59944530586569314342
Signed dm .ray
Sticker, posted without a caption
Signed dm .ray
😀#HPBRAY — جي & mpc Conflicts, champagne | think tanks ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Желаю всем спокойного сна и докидываю спойлер к ближайшей нью-эре. Хочу снова от души поблагодарить всех, кто поддерживал MPC. Этот проект дожил до моего дня рождения. Удивительно. Надеюсь, вместе со мной этот чат будет расти и приносить свои плоды, ведь я действительно его люблю и готова двигать дальше сквозь выгорание, апатию…
custom 59676888453978559391
Signed Sovereign Ierihon.
Sticker, posted without a caption
Signed Sovereign Ierihon.
ㅤㅤ ㅤ💬 𝗆𝗉𝖼 · 𝗌𝗁𝗂𝗍𝗉𝗈𝗌𝗍 🌟🌟 — рацио приказал выложить #𝐏азвлекательное · @mpclifs
custom 59944530586569314341
Signed Sovereign Ierihon.
Sticker, posted without a caption
Signed Sovereign Ierihon.
ㅤㅤ ㅤ 𝗆𝗉𝖼 · 𝗌𝗁𝗂𝗍𝗉𝗈𝗌𝗍 — квадракилл #𝐏азрыв · @mpclifs
custom 59247192523795377291
Signed Sovereign Ierihon.
Sticker, posted without a caption
Signed Sovereign Ierihon.
оу шііт
custom 59676888453978559392
Signed @ruawka-chan : ( #arlet )
Sticker, posted without a caption
Signed Sovereign Ierihon.
ㅤㅤ ㅤ 𝗆𝗉𝖼 · 𝗌𝗁𝗂𝗍𝗉𝗈𝗌𝗍 — триплкилл #𝐏азрыв · @mpclifs
custom 59247192523795377292
Signed Sovereign Ierihon.
Showing the 12 most recent of 20 posts we hold for @mpclifs. 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.
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.
Named by 8 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“𝟎𝟓 · 𝐌𝐏𝐂 ☬ 𝐋'𝐈𝐅𝐄 · 𝟓𝟎” (@mpclifs), 98 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/mpclifs.
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.