Telegram RegisterThe public register of Telegram
Telegram profile photo for FG Consulting

Channel

FG Consulting

@fgconsulting

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

126subscribers

+2 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001607235383
TypeChannel
Username@fgconsulting
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live22 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/fgconsulting

Growth

1241261257 August 2026 — 124 subscribers8 August 2026 — 125 subscribers9 August 2026 — 125 subscribers22 August 2026 — 126 subscribers7 August 202622 August 2026
4 measurements spanning 15 days, net +2. 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 124–126 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 13:35126+1
9 Aug 2026, 02:46125no change
8 Aug 2026, 14:03125+1
7 Aug 2026, 21:07124first reading

Engagement

20 posts held, back to 27 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
14.9%
avg views ÷ 126 subscribers
Avg views / post
18.8
20 posts measured
Reaction rate
5.95%
reactions ÷ views · ER floor
Posts in window
20
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. It is computed over the 4 of 20 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held20 (27 July 20267 August 2026)
Views total376
Reactions total5
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 02:46 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

5 reactions across 4 posts, in 2 distinct kinds. The most used accounts for 80.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥480.0%
👍120.0%

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 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 5reactions 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 27 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.

Recent posts

7 Aug 2026, 15:00 UTC11 viewsread 9 August 2026

Когда сотрудники сами просят ужесточить правила — это почти всегда тревожный сигнал. К нам обратилась B2B-компания. Руководитель отдела продаж предложил мягкий формат: короткий еженедельный созвон и свободная фиксация сделок. Ответ команды шокировал всех. Люди сами настояли на ежедневных детальных отчётах, двойных согласованиях и жёстком регламенте. Формально — идеальная управляемость. На самом деле — панический ст

6 Aug 2026, 15:00 UTC17 viewsread 9 August 2026

Пять лет вместе — и ошибка прошла незамеченной, потому что все были абсолютно уверены. Знакомая сцена? Чем дольше люди работают вместе, тем быстрее приходят к согласию. И тем реже это согласие означает, что они правы. Опыт совместной работы создаёт слепые зоны. За годы накапливается пласт негласных договорённостей: «мы же знаем, как ведёт себя этот клиент», «этот подход у нас всегда срабатывал», «тут и обсуждать не

5 Aug 2026, 15:00 UTC20 views1 reactionsread 9 August 2026

70% команд воспринимают смену руководителя как предательство — потому что их просто не спросили. Передача проекта — это момент, когда доверие проверяется на прочность. Люди задают себе вопрос: «Нас бросили или нас передали в надёжные руки?» Ответ зависит не от приказа, а от того, что вы скажете. Вот что работает: 1. Сообщите команде первыми — раньше, чем узнают из рассылки или слухов. Люди прощают решения, но не п

🔥1

4 Aug 2026, 15:00 UTC17 viewsread 9 August 2026

Открытость — не значит вываливать на команду всё подряд. Некоторые руководители делятся абсолютно всем: планами, сомнениями, сырыми цифрами, рисками, о которых сами ещё не подумали. Они верят, что чем больше информации, тем выше доверие. Результат — команда напрягается и работает медленнее. Проблема не в честности, а в подмене. Вы путаете прозрачность с откровенностью. Прозрачность — когда людям понятны ваши решени

3 Aug 2026, 15:00 UTC17 viewsread 9 August 2026
Poll

Когда вы в последний раз отменили встречу, потому что она была не нужна?

  1. На этой неделе — регулярно чищу календарь50%
  2. Пару месяцев назад, редко такое делаю50%
  3. Не помню — почти никогда не отменяю0%
  4. Никогда — встреча в календаре = встреча состоится0%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

3 Aug 2026, 15:00 UTC16 views1 reactionsread 9 August 2026

71% руководителей сидят на совещаниях, которые можно отменить — и всё равно приходят. Вы, скорее всего, тоже. Встреча стоит в календаре — и она обязательно состоится. Даже без повестки. Даже если вопрос решили в чате. Даже если половина зашла просто послушать. Собираемся ради самого факта встречи. Это создаёт иллюзию работы: собрались, обсудили, галочка. А решения, как и раньше, принимают в коридоре за две минуты.

🔥1

31 Jul 2026, 15:00 UTC22 views1 reactionsread 9 August 2026

Директор в 23:00 — это не забота, это воспитание беспомощности. К нам обратился руководитель отдела продаж — человек с репутацией «всегда на связи». Отвечал мгновенно, в выходные, в отпуске, ночью. Гордился этим. Но пришёл с неожиданной проблемой: «Команда перестала думать». Разбор показал парадокс. Чем доступнее был руководитель, тем меньше решений принимала команда. Зачем напрягаться и брать риск, если готовый от

🔥1

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

Polls

The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

3 Aug 2026, 15:00 UTCAnonymous Poll2 voters

Когда вы в последний раз отменили встречу, потому что она была не нужна?

  1. На этой неделе — регулярно чищу календарь50%
  2. Пару месяцев назад, редко такое делаю50%
  3. Не помню — почти никогда не отменяю0%
  4. Никогда — встреча в календаре = встреча состоится0%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

27 Jul 2026, 15:00 UTCAnonymous Poll2 voters

Какой «мёртвый ритуал» живёт в вашей команде?

  1. Лишние согласования по мелочам0%
  2. Копии письма ненужным людям0%
  3. Свои ритуалы — расскажу в комментариях0%

Shares as published, totalling 0%. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 27 July 2026 to 7 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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

“FG Consulting” (@fgconsulting), 126 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/fgconsulting.

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.