Channel
@projectmylive
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
22subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002719636663 |
|---|---|
| Type | Channel |
| Username | @projectmylive |
| Description | Какое бы дело мы ни затевали, время всегда кажется неподходящим, и никогда не бывает абсолютно благоприятных обстоятельств. Тот, кто ждёт идеального случая, так никогда и не начнёт дела, а если и начнёт, то зачастую его ожидает печальный конец. Макиавелли |
| Created | Between 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/projectmylive |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 13:30 | 22 | no change |
| 7 Aug 2026, 18:36 | 22 | first reading |
17 posts held, back to 1 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 pageof Telegram’s post history, 20 posts per page.
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 1 of 6 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 10 August 2026 |
|---|---|
| Posts held | 17 (1 May 2026 – 10 August 2026) |
| Views total | 98 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Aug 2026, 13:30 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.
Lifetime counters from Telegram’s own channel header, read 11 August 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.
7 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 85.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 6 | 85.7% | |
| 🔥 | 1 | 14.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 3 of the 17 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 7reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 1 May 2026 to 10 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.
🛠 Как внедрить: практические шаги Ввести обязательный блок «Что мы ещё не знаем / что может пойти не так» в каждый статус-отчёт. Без этого блок отчёт считается неполным. Разделить отчётность на три слоя: операционный (ежедневно/еженедельно), тактический (раз в 2–4 недели), стратегический (ежемесячно/по вехам). Форматы разные. Зафиксировать правило: любое отклонение фиксируется в момент обнаружения, а не в момент подг…
📌 СТАТЬЯ 2: Почему отчёты врут — и почему всем это удобно 🚨 Всё выглядит контролируемым. Графики зелёные. KPI в норме. Статус «без отклонений». Заказчик спокоен. Подрядчик отчитывается вовремя. А потом — внезапно — срыв сроков на 4–6 месяцев, перерасход CAPEX на 15–25 %, дефекты, которые «не могли быть выявлены ранее». Проблема не в том, что люди плохо считают. Проблема в том, что система отчётности построена так, чт…
Проектное управление по стандартам PMI: основа системного успеха Эффективное управление проектами - это не набор разрозненных действий, а дисциплинированный, воспроизводимый процесс, основанный на проверенных методологиях. Project Management Institute (PMI) определяет проектное управление как применение знаний, навыков, инструментов и методов к проектной деятельности для удовлетворения требований проекта. Согласно ст…
Channel name was changed to «Моя жизнь и проекты 📈»
Photo, posted without a caption
Posted without readable text
📊 Информационные панели (Dashboards) в управлении проектами: Как превратить данные в решения Сбором метрик и данных об исполнении работ сегодня никого не удивишь. Однако сами по себе измерения и KPI не имеют практической пользы, если они не помогают принимать своевременные управленческие решения. В соответствии с принципами PMI и домена исполнения «Измерение» (Measurement Performance Domain), ключевой вызов руководи…
🔥1
Погнали творить!))
👍3
Photo, posted without a caption
👍3
#Пятничное Посадил генерал Репку. Не то чтобы очень хотел — просто вышел приказ о цифровой трансформации оборонного контура, выделили бюджет, провели совещание, нарисовали дорожную карту в PowerPoint и в конце первого слайда написали: «Задача — вырастить собственную ИИ-систему поддержки принятия решений.» Репке присвоили секретный код «AIDA» — Artificial Intelligence Decision Accelerator. Система обещала всё: ана…
Первый раз такое вижу. МО расписалось под такой статьей! Тектонический сдвиг в объективной оценке. Товарищи! С правды начинаются грандиозные проекты! (Если это не хитрый план)
В № 1 за 2026 год официального журнала Министерства обороны Российской Федерации «Военная Мысль» опубликована небезынтересная статья «Тактика применения авиационных управляемых ракет «воздух — воздух» большой дальности в ходе СВО», авторами которой являются кандидаты военных наук полковник А.Ю. Стёпкин, подполковник А.А. Гвозденко и Ю.Г. Кравцов. Статья раскрывает некоторые особенности воздушной войны над территорией…
Showing the 12 most recent of 17 posts we hold for @projectmylive. 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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“Моя жизнь и проекты 📈” (@projectmylive), 22 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/projectmylive.
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.