Telegram RegisterThe public register of Telegram

Channel

CFO

@CFO_Club

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

1,276subscribers

-3 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001391935152
TypeChannel
Username@CFO_Club
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/CFO_Club

Growth

1,2761,2791,277.56 August 2026 — 1,279 subscribers7 August 2026 — 1,279 subscribers10 August 2026 — 1,276 subscribers6 August 202610 August 2026
3 measurements spanning 3 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 1,276–1,279 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 08:401,276-3
7 Aug 2026, 12:171,279no change
6 Aug 2026, 22:451,279first reading

Engagement

17 posts held, back to 15 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
26.0%
avg views ÷ 1,276 subscribers
Avg views / post
331
16 posts measured
Reaction rate
1.05%
reactions ÷ views · ER floor
Posts in window
17
of 17 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 15 of 16 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 4 August 2026
Posts held17 (15 July 20264 August 2026)
Views total5,301
Reactions total53
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 22:45 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

53 reactions across 15 posts, in 9 distinct kinds. The most used accounts for 39.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍2139.6%
1222.6%
🔥713.2%
👌47.55%
custom 534149808840823450435.66%
💯35.66%
🆒11.89%
👀11.89%
🤔11.89%

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 15 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 53reactions 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 15 July 2026 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, 11:29 UTC205 views4 reactionsread 6 August 2026
Photo

MOEX / Московская биржа 🕯ВАЛЮТНЫЙ РЫНОК Сегодня валютные торги проходили на фоне продолжающегося умеренного ослабления рубля, до 11,9970 (уровень 12 пока не был пробит) На текущий момент на рынке проторгованы объёмы расчетами: Tod: 1,1 млрд CNY Tom: 5,2 млрд CNY С учетом снижения стоимости нефти и юаневых ставок на рынке, вероятно ослабление рубля ограничится уровнем 12,15 🛍ДЕНЕЖНЫЙ РЫНОК РУБЛЁВЫЕ СТАВКИ на денеж

2👌1👍1

3 Aug 2026, 10:15 UTC249 views4 reactionsread 6 August 2026

⚠️Налоговые выплаты в августе 2026 28 августа Страховые взносы: 1.386 млрд руб. Выплата НДС: 1.066 млрд руб. Выплата НДПИ: 656 млрд руб. Выплата акцизов: 304 млрд руб. Выплата налога на прибыль: 721 млрд руб. Обратный акциз на нефтепродукты с демпфером: -226 млрд руб. Объем экспортных пошлин газ, нефть, нефтепродукты, которые выплачиваются в течение всего календарного месяца и не суммируются с другими налогами сос

2👍2

3 Aug 2026, 10:01 UTC250 viewsread 6 August 2026
Photo

👏MOEX / Московская биржа 🕯ВАЛЮТНЫЙ РЫНОК Сегодня валютные торги проходили на фоне ослабления рубля. На текущий момент на рынке проторгованы объёмы расчетами: Tod: 3,3 млрд CNY Tom: 0,4 млрд CNY С учетом текущей стоимости нефти и юаневых ставок на рынке, вероятно ослабление рубля ограничится уровнем 11,90 🛍ДЕНЕЖНЫЙ РЫНОК РУБЛЁВЫЕ СТАВКИ на денежном рынке маркируются на уровнях: O/n 13,92% 1W 14% 2W 13,98% 1M 14,04

28 Jul 2026, 08:08 UTC345 views3 reactionsread 6 August 2026
Photo

👏Московская биржа / MOEX Денежный рынок Сегодня последний день уплаты налогов. Совокупные налоговые платежи составят ~5.269 млрд руб., детали здесь. ⚠️В моменте спрос на рубли o/n в 2 раза превышает предложение (в видимой части, без учета айсбергов). -Совокупный объём спроса (в видимой части) составляет: 81,4 млрд руб. -Совокупный объём предложения (в видимой части): 39,7 млрд руб. Ставки денежного рынка маркир

👍2🔥1

24 Jul 2026, 16:46 UTC384 views6 reactionsread 6 August 2026
Photo

Среднесрочный прогноз ЦБ После сегодняшнего опорного заседания, ЦБ обновил среднесрочный прогноз. Важные изменения отмечены красным (в скобках предыдущие значения среднесрочного прогноза от 24.04.2026): 📍1. Прогноз по инфляция повышен до 6-7% декабрь к декабрю (ранее 4,5-5,5%) 📍2. Инфляция в среднем за год 5,9-6,2% (ранее 5,1-5,6%) 📍3. Ключевая ставка в среднем за год 14,5-14,6% (ранее 14-14,5%) 🔖4. Счет текущи

4👀1👍1

24 Jul 2026, 10:30 UTC361 views9 reactionsread 6 August 2026
Photo

Ключевая ЦБ 14% На сегодняшнем заседании (24.07.2026) ЦБ снизил КС на 25 b.p., до 14% Источник: ЦБ P.S. Мнение верховного важно! #Ключевая #ЦБ #ЦБР #ЦБРФ

👍3💯3🔥2🆒1

23 Jul 2026, 19:02 UTC374 views10 reactionsread 6 August 2026
Photo

Ключевая ставка ЦБ - мнение участников рынка. 63% проголосовавших считают ЦБ оставит КС без изменения (14,25%) 23% считают, что будет cut 25 b.p. Ну что ж дамы и господа, завтра проверим наши с Вами теории. P.s. Я за flat

👍5custom 53414980884082345043👌2

23 Jul 2026, 18:37 UTC302 views1 reactionsread 6 August 2026
Photo

Максимальная депозитная ставка в RUB десяти банков, крупнейших по объему депозитов, на II декаде июля составила 12,826% (в I декаде июля 12,79%) Источник: ЦБ 👏MOEX 📍На бирже рублевые ставки находятся в диапазоне 13,90%-14,11% P.s. На ОТС размещения проходят на уровнях 14,55%-14,60%👍 #ставка

👍1

23 Jul 2026, 18:23 UTC288 views1 reactionsread 6 August 2026
Photo

👏MOEX / Московская биржа Сегодня валютные торги проходили на достаточно тонком рынке. Объёмы расчетами: Tod: 1,34 млрд CNY Tom: 5,99 млрд CNY Похоже, экспортеры не достаточно активно продают валюту перед уплатой крупных налогов 28 июля, что привело к росту юаневых ставок o/n на MOEX до 8% 📍Данные по инфляционным ожиданиям населения РФ на год вперед в июле показали рост сразу на 2,3 п. п. до 14,7%, что является ма

1

22 Jul 2026, 17:15 UTC342 views1 reactionsread 6 August 2026
Photo

Инфляция в России🇷🇺 Подъехали принты по инфляции. 📍Недельная инфляция в России с 14.07.2026 по 20.07.2026 составила 0,17% (неделей ранее 0,17%) Инфляция с начала года выросла до 4,82% (неделей ранее 4,64%). Источник: Росстат 📍Годовая инфляция в России на 20.07.2026 выросла до 5,84% (неделей ранее 5,62%) 📍Годовая инфляция в России за неделю с 14.07.2026 по 20.07.2026 выросла до 5,84% (неделей ранее 5,62%) Источни

👍1

20 Jul 2026, 09:22 UTCviews —

CFO pinned «Ключевая ЦБ🇷🇺 Какое, по вашему мнению, решение примет ЦБ по ключевой ставке на заседании в эту пятницу (24.07.2026)? Последние принты по инфляции 5,62%»

20 Jul 2026, 09:22 UTC403 views2 reactionsread 6 August 2026
Poll

Ключевая ЦБ🇷🇺 Какое, по вашему мнению, решение примет ЦБ по ключевой ставке на заседании в эту пятницу (24.07.2026)? Последние принты по инфляции 5,62%

  1. 🩸🩸🩸🩸 +50 b.p., до 14,75%2%
  2. 🩸🩸🩸🩸 +25 b.p., до 14,50%6%
  3. 🟡NO CHANGE, 14,25%63%
  4. 🟢Cut 25 b.p., до 14,0%24%
  5. 🟢Cut 50 b.p., до 13,75%2%
  6. 🟢Cut 75 b.p., до 13,50%1%
  7. Не знаю, интересно посмотреть результат👀5%

The shares total 103%, 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.

👍1🔥1

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

20 Jul 2026, 09:22 UTCFinal Results136 voters

Ключевая ЦБ🇷🇺 Какое, по вашему мнению, решение примет ЦБ по ключевой ставке на заседании в эту пятницу (24.07.2026)? Последние принты по инфляции 5,62%

  1. 🩸🩸🩸🩸 +50 b.p., до 14,75%2%
  2. 🩸🩸🩸🩸 +25 b.p., до 14,50%6%
  3. 🟡NO CHANGE, 14,25%63%
  4. 🟢Cut 25 b.p., до 14,0%24%
  5. 🟢Cut 50 b.p., до 13,75%2%
  6. 🟢Cut 75 b.p., до 13,50%1%
  7. Не знаю, интересно посмотреть результат👀5%

The shares total 103%, 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 17 most recent posts we hold, published 15 July 2026 to 4 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.

Citation-graph rank

Citation-graph rank — 850,329 of 1,151,006entries 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.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

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

“CFO” (@CFO_Club), 1,276 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/CFO_Club.

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.