Telegram RegisterThe public register of Telegram
Telegram profile photo for ОППО МЦПБ

Channel

ОППО МЦПБ

@MCPB_vmeste

On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Telegram's recommendations · Cite this entry

1,337subscribers

+18 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001764164826
TypeChannel
Username@MCPB_vmeste
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 September 2026
Measurements held11
Confirmed unchanged2 times, most recently 15 September 2026
On Telegramt.me/MCPB_vmeste

Topic

Local community — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 56% 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.

Growth

1,3161,3371,326.57 August 2026 — 1,319 subscribers7 August 2026 — 1,319 subscribers8 August 2026 — 1,320 subscribers11 August 2026 — 1,319 subscribers14 August 2026 — 1,320 subscribers17 August 2026 — 1,317 subscribers20 August 2026 — 1,316 subscribers24 August 2026 — 1,317 subscribers30 August 2026 — 1,320 subscribers2 September 2026 — 1,323 subscribers11 September 2026 — 1,337 subscribers7 August 202611 September 2026
11 measurements spanning 35 days, net +18. 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 1,313–1,340 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 16:171,337+14
2 Sept 2026, 16:061,323+3
30 Aug 2026, 21:041,320+3
24 Aug 2026, 14:481,317+1
20 Aug 2026, 21:151,316-1
17 Aug 2026, 19:041,317-3
14 Aug 2026, 21:151,320+1
11 Aug 2026, 17:421,319-1
8 Aug 2026, 12:361,320+1
7 Aug 2026, 22:311,319no change
7 Aug 2026, 16:391,319first reading

Engagement

4 posts held, back to 31 July 2026the 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 4 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

35 reactions across 4 posts, in 4 distinct kinds. The most used accounts for 45.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1645.7%
🔥1131.4%
👍617.1%
🤩25.71%

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

Measured over the 4 most recent posts we hold, published 31 July 2026 to 7 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.

Telegram Stars

Stars received
2
across the posts below
Posts paid on
2
of 4 we hold a reading for · 50%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @MCPB_vmeste. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 4 most recent posts we hold for this entry, published 31 July 2026 to 7 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

7 Aug 2026, 09:24 UTC123 views12 reactions1 Starread 7 August 2026
Photo

🌈 Лето — это не только работа, но и яркие впечатления! 30 и 31 июля 2026 года работники-члены профсоюза ООО «ЛУКОЙЛ-МЦПБ Пермского региона сменили офисные кресла на сапборды. На городском пляже прошла масштабная прогулка по воде, собравшая более 5️⃣0️⃣ участников. ☺️ Такие встречи помогают не только перезагрузиться, но и стать еще дружнее вне рабочих задач! Пестерева Елена (Ведущий экономист): Все было очень орга

5👍4🔥3

4 Aug 2026, 11:56 UTC224 views12 reactions1 Starread 7 August 2026
Photo

25 июля 2026 года работники-члены профсоюза ООО «ЛУКОЙЛ-МЦПБ» Пермской площадки совершили увлекательное путешествие по уникальным природным достопримечательностям региона. 🤩 Организованную экскурсию в Каменный город и Шухминские скалы посетили около 2️⃣0️⃣0️⃣ человек, включая членов семей сотрудников. 🔴Целью поездки стало укрепление корпоративного духа, поддержка семейных ценностей и организация активного отдыха дл

🔥64🤩2

3 Aug 2026, 06:19 UTC261 views8 reactionsread 7 August 2026
Photo

18 июля 2026 года работники-члены профсоюза ООО «ЛУКОЙЛ-МЦПБ» Нижегородского региона отправились в однодневную увлекательную экскурсию в город Арзамас. 👣 🤩Вместо обычной путевой информации в дороге участники экскурсии услышали настоящий аудио-спектакль от виртуальных попутчиков — тревел-блоггер Настя Дорожкина и писатель-краевед Аристарх Кержаков. Насыщенная программа дня включала посещение нескольких знаковых лока

4👍2🔥2

31 Jul 2026, 15:16 UTC292 views3 reactionsread 7 August 2026
Photo

Конкурс стихов к 35-летию ЛУКОЙЛ♥️ Совет Молодых Специалистов при поддержке ОППО ООО «ЛУКОЙЛ-МЦПБ» объявляет о старте конкурса стихов, посвященного 35-летию нашей Компании. 35 лет - это история успеха, написанная трудом и талантом каждого из Вас. Приглашаем всех сотрудников принять участие, выразив свои чувства в самом искреннем и душевном формате! Номинации: ∙ «ЛУКОЙЛ-это мы» - стихи, подчеркивающие единст

3

Showing the 4 most recent of 4 posts we hold for @MCPB_vmeste. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

ПАО «ЛУКОЙЛ»
@lukoilofficial · 81,691
Telegram ranks this channel #5 of 74 here — alongside 73 others — read 21 August 2026
Enjoy Squad
@takemyhumor · 42,345
Telegram ranks this channel #45 of 68 here — alongside 67 others — read 29 August 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“ОППО МЦПБ” (@MCPB_vmeste), 1,337 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/MCPB_vmeste.

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.