Telegram RegisterThe public register of Telegram

Channel

Финансы в бизнесе | Шикова Елена

@CFO_consultants

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Handles named that no longer answer · Cite this entry

327subscribers

-1 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-1002578374335
TypeChannel
Username@CFO_consultants
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 8 August 2026
On Telegramt.me/CFO_consultants

Growth

327328327.57 Aug 2026, 18:03 — 328 subscribers8 Aug 2026, 07:18 — 328 subscribers8 Aug 2026, 10:25 — 327 subscribers7 Aug 2026, 18:038 Aug 2026, 10:25
3 measurements taken within a single day, net -1. 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 327–328 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 10:25327-1
8 Aug 2026, 07:18328no change
7 Aug 2026, 18:03328first reading

Engagement

20 posts held, back to 1 May 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
33.3%
avg views ÷ 327 subscribers
Avg views / post
109
3 posts measured
Reaction rate
7.34%
reactions ÷ views · ER floor
Posts in window
3
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 5 August 2026
Posts held20 (1 May 20265 August 2026)
Views total327
Reactions total24
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 07:18 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.

What this channel posts

Video runtime
1m 07s
Average length
34s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

115 reactions across 19 posts, in 12 distinct kinds. The most used accounts for 27.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥3127.0%
👍2521.7%
💯2320.0%
1815.7%
😢76.09%
custom 541340885039921793321.74%
21.74%
😁21.74%
🤬21.74%
🤝10.87%
🤩10.87%
🥴10.87%

Custom emoji. One 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 count beside it isTelegram’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 19 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 115reactions 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 1 May 2026 to 5 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

5 Aug 2026, 18:13 UTC64 views14 reactionsread 8 August 2026

📣 Тема дня 😡Как один отчет чуть не рассорил финансистов и коммерсантов. Хотите знать какой? Почему? И как мы избежали не просто конфликт, а даже стали друзьями? Наберём 10🔥, и я подготовлю всю информацию❤️

🔥14

27 Jul 2026, 18:19 UTC131 views6 reactionsread 8 August 2026

Мысль дня: Нищета от слова не считать! ➡️ Не считаешь себестоимость — работаешь в минус. ➡️ Не считаешь дебиторку — работаешь на клиента. ➡️ Не считаешь оборачиваемость — работаешь на склад. ➡️ Не считаешь кассовый разрыв — работаешь на банк. Богатый считает не потому что жадный. А потому, что деньги любят порядок и счет. И тут не важен уровень и отрасль бизнеса🤎 💡Продаёте ли вы кофе или нефть. 💡Только начали ил

💯3🔥2👍1

23 Jul 2026, 19:10 UTC132 views4 reactionsread 8 August 2026

🎬 Частый вопрос получаю: Как разделить не просто PL проектов/юнитов, а ещё и их фин.потоки в рамках одного ЮЛ? Только через открытие разных счетов или выводом разных статей. Но при этом если есть немало общих расходов, эта история не работает. Важно: не делите общие расходы на разные платежки ради проектов. Это максимальная глупость🫪 Выводы по эффекту нужно вести по PL🥳

👍21💯1

12 Jul 2026, 16:20 UTC155 views4 reactionsread 8 August 2026

Принцип Стокдейла. Слыхали о таком? А он есть. А как он связан с финансами? Прямо! Даже если в жизни вы большой оптимист, как и я💃. Никогда на свои финансы не смотрите также. Особенно в кризис, из которого мы не выйдем никогда, лучшее управление финансами - это всегда держать рядом худший сценарий.

💯21👍1

9 Jul 2026, 19:52 UTC167 views5 reactionsread 8 August 2026

Мысль дня: Есть 2 типа собственника: 1. Те, кто вкладывает в бизнес. Порой, последнее. 2. Те, кто тащат из него больше полученного. Это как купить дорогую вещь и жить на дошираке. Бизнесмен ли последний?

💯3👍1🤩1

6 Jul 2026, 19:09 UTC186 views1 reactionsread 8 August 2026

Все время забываю указывать, что я ещё как могу транслирую все в Max🙈. Финансы в бизнесе

👍1

6 Jul 2026, 18:32 UTC181 views4 reactionsread 8 August 2026
Photo

Пример расчета чувствительности EBITDA к изменению % маржинальности и % выполнения плана продажа. Иными словами, чтобы сохранить Ebitd: Норма - это план. Опустив маржу на 1%, необходимо выполнить выручку не менее чем на 110%. И тд Чтобы хоть что-то не потерять при невыполнении выручки, считать необходимо в обратную сторону и определять, какой маржой в абсолюте вы готовы пожертвовать, чтобы не потерять ее еще больш

2👍1custom 54134088503992179331

6 Jul 2026, 18:20 UTC143 views4 reactionsread 8 August 2026
Photo

❓Недавно в разговоре затронули важную тему: в розничном сетевом бизнесе % маржинальности — это не показатель эффективности🤩И его падение - это нормально. 😶 Ключевой ориентир — это валовая прибыль в деньгах, которая не должна падать ниже плана, независимо от того, как вы выполняете план по выручке. И мое мнение - и ДА, и НЕТ. Здесь очень тонкая грань. И чтобы не уйти в крайности, каждый случай нужно разбирать отдель

2🔥1custom 54134088503992179331

4 Jul 2026, 17:23 UTC128 viewsread 8 August 2026
Poll

К вопросу выше, что думаете друзья?

  1. 100% эффективнее рост выручки7%
  2. В росте выручки и падении маржи нет ничего эффективного47%
  3. Ответ неоднозначный20%
  4. Эффективны оба случая, но нужно смотреть на другие показатели20%
  5. Затрудняюсь с ответом13%

The shares total 107%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

4 Jul 2026, 17:20 UTC123 views1 reactionsread 8 August 2026

Друзья, привет🫸 Недавно у меня был спор. Что важнее или, так сказать, эффективнее: 1. падение % маржи или рост выручки? 2. и на что при таком дисбалансе нужно смотреть ещё? 3. какой KPI ставить ком.диру? Друзья, как думаете? Поделитесь мыслями📣⬇️

1

24 Jun 2026, 18:08 UTC179 views5 reactionsread 8 August 2026
Photo

🪿 Друзья, сегодня разберем, что такое юнит-экономика и зачем ее считать.👍 Раньше к юнит-экономике относили просто себестоимость товара. Сейчас — это всё, что можно разбить на атомы🔄: магазины, услуги, товары, каналы, клиенты… Иными словами - это любой объект дохода. И его обязательно!!!! нужно просчитывать до финансового результата. ❣️Более того, в одном бизнесе их может быть несколько сразу, например: каналы- мага

2👍2💯1

Showing the 12 most recent of 20 posts we hold for @CFO_consultants. 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 poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

4 Jul 2026, 17:23 UTCAnonymous Poll15 voters

К вопросу выше, что думаете друзья?

  1. 100% эффективнее рост выручки7%
  2. В росте выручки и падении маржи нет ничего эффективного47%
  3. Ответ неоднозначный20%
  4. Эффективны оба случая, но нужно смотреть на другие показатели20%
  5. Затрудняюсь с ответом13%

The shares total 107%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not 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 1 May 2026 to 5 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.

Mentions

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.

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

“Финансы в бизнесе | Шикова Елена” (@CFO_consultants), 327 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/CFO_consultants.

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.