Telegram RegisterThe public register of Telegram
Telegram profile photo for Project Russia - Управление проектами в России и в мире

Channel

Project Russia - Управление проектами в России и в мире

@projectru

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

958subscribers

-3 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001007305730
TypeChannel
Username@projectru
CreatedBetween 1 September 2015 and 31 December 2015— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/projectru

Growth

958961959.55 August 2026 — 961 subscribers6 August 2026 — 961 subscribers13 August 2026 — 958 subscribers5 August 202613 August 2026
3 measurements spanning 8 days, net -3. 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 958–961 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 18:27958-3
6 Aug 2026, 13:37961no change
5 Aug 2026, 22:08961first reading

Engagement

20 posts held, back to 19 November 2025the 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.

ERR · 30 days
11.6%
avg views ÷ 958 subscribers
Avg views / post
111
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 20 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 4 August 2026
Posts held20 (19 November 20254 August 2026)
Views total111
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 13:37 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.

Reaction mix

90 reactions across 18 posts, in 17 distinct kinds. The most used accounts for 25.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁2325.6%
👍1112.2%
910.0%
😢77.78%
🤔55.56%
🤣55.56%
👌44.44%
👎44.44%
🕊44.44%
🙈44.44%
🤷‍♂44.44%
🔥33.33%
💯22.22%
🤝22.22%
💩11.11%
😐11.11%
🤩11.11%

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 18 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 90reactions 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 19 November 2025 to 4 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.

Recent posts

4 Aug 2026, 13:38 UTC111 viewsread 6 August 2026
Photo

🏆Открытый кубок по управлению проектами — 2026 в г. Москве Высшая школа бизнеса НИУ ВШЭ приглашает руководителей и специалистов принять участие в Открытом кубок по управлению проектами — 2026 в г. Москве. 🗓 4–5 сентября 2026 года 🏠Москва 💰 Участие бесплатное, требуется регистрация Кубок — это бизнес-соревнование, созданное для развития компетенций в области проектного менеджмента и управления, формирования управ

9 Jul 2026, 17:29 UTC214 views8 reactionsread 6 August 2026
Photo

А вы слушаете подкасты про управление проектами, проектную деятельность и т.д.? 👍 - если да 🤷‍♂ - если всё равно Я редко слушаю. Только избранное. И только избранных

👍4🤷‍♂4

14 Jun 2026, 12:27 UTC375 views9 reactionsread 6 August 2026

Наблюдая за некоторыми коллегами по тематике проектного управления, которые долго время работали по теме на государственной службе, а после выбрали сферу собственного бизнеса, можно поразиться насколько прозападная идеология глубоко укоренилась в коллегах. Так глубоко, что ни одной капельки чего то собственного ни в методиках, ни в практиках, ни в использовании продуктов. И в трансляции своих идей открытое ожидание,

🕊4😁2🤣1🤩1😢1

2 Apr 2026, 05:33 UTC596 views1 reactionsread 6 August 2026

Часть пятая. Тренды управления проектами -2026. Тренды делятся на: хайповые по заказу - например, "национальная модель управления проектами" технологические - например, как в примерах выше. ситуационные - тоже пример выше, так как в ситуации когда всё ..... приходится вспоминать про бережливость и т.д. и тренды опубликованные 1 апреля любого года #управлениепроектами #тренды

😁1

1 Apr 2026, 20:18 UTC527 views2 reactionsread 6 August 2026

Часть четвертая. Тренды управления проектами -2026. Проектная деятельность - производительная, бережливая, эффективная. Производительность, бережливость, эффективность - вот что должно быть в управлении вашим проектом в 2026 году и после. #управлениепроектами #тренды #эффективность #производительность #бережливость

😁2

1 Apr 2026, 20:12 UTC392 views1 reactionsread 6 August 2026

Часть третья. Квантовые вычисления на службе инвестиционно-проектной деятельности государства. Ни одна внешняя организация не сможет составить конкуренцию гос.планировщикам. #управлениепроектами #тренды

😁1

1 Apr 2026, 19:59 UTC381 views1 reactionsread 6 August 2026

Часть вторая. За последние 25 лет в организации с участием государства: гос организации и гос компании было внедрено много много ПО. Принесло ли это ожидаемые эффекты? Не везде. Там где не принесло - покупатели внедрений и продавцы ПО понесут отложенное возмездие и принесут государству упущенное. В том числе и в части ПО для управления проектами. #управлениепроектами #тренды

😁1

1 Apr 2026, 19:39 UTC346 views7 reactionsread 6 August 2026

Тренды в управлении проектами - 2026. Первая часть Часть российского консалтингового бизнеса в части управления проектами, разработки ПО для управления проектами , в том числе , для календарно-сетевого планирования .... вымрет до конца 2027 года по причине невостребованности этих услуг и продуктов со стороны госкорпораций и частного бизнеса. Период 2022-2026 показал, что существующим в этой сфере организациям нечего

🤔4😢2😁1

24 Mar 2026, 15:44 UTC406 views3 reactionsread 6 August 2026

Если придется Плыть вам по свету, Не забывайте Песенку эту: В каждом деле, Двигаясь к цели. Надо всюду Помнить про мели! Песня из фильма "Верные друзья", 1954 год

👍21

18 Mar 2026, 17:02 UTCviews —

Project Russia - Управление проектами в России и в мире pinned «Страница нашего канала в МАХ: https://max.ru/join/efecYaLy1xSDgtEpOob-xdX4midHAcvPr5hn2BD5fwU»

15 Mar 2026, 15:56 UTC510 views4 reactionsread 6 August 2026

Страница нашего канала в МАХ: https://max.ru/join/efecYaLy1xSDgtEpOob-xdX4midHAcvPr5hn2BD5fwU

👎4

3 Feb 2026, 08:57 UTC756 views2 reactionsread 6 August 2026

Презентация мемуаров Якова Уринсона «Всё пошло не по Госплану» 📆 5 февраля 19:00–20:00 📍 Москва, ул. Малая Никитская, дом 12, стр. 1 Усадьба Долгоруковых-Бобринских. Книжный магазин Пиотровский, 2 этаж ℹ️ https://afisha.timepad.ru/moscow/events/prezentaciya-memuarov-yakova-urinsona-vse-poshlo-ne-po-gosplanu-3777010

💩1🔥1

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

Citation-graph rank — 1,042,014 of 1,480,944entries 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.

Forward network

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.

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

“Project Russia - Управление проектами в России и в мире” (@projectru), 958 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/projectru.

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.