🏷 SILVER // 15 мин

Channel
Берёзовый TRADING | IMOEX
@birch_trading
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,485subscribers
+4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002421102617 |
|---|---|
| Type | Channel |
| Username | @birch_trading |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/birch_trading |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 03:17 | 1,485 | +1 |
| 11 Aug 2026, 07:21 | 1,484 | -1 |
| 8 Aug 2026, 03:30 | 1,485 | +4 |
| 7 Aug 2026, 08:48 | 1,481 | first reading |
Engagement
20 posts held, back to 28 July 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 2 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 47.9%
- avg views ÷ 1,485 subscribers
- Avg views / post
- 711
- 20 posts measured
- Reaction rate
- 1.77%
- 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 19 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 20 (28 July 2026 – 7 August 2026) |
| Views total | 14,218 |
| Reactions total | 245 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 18:15 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
245 reactions across 19 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5438496463044752972 | 245 | 100.0% |
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 245reactions 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 28 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
в серебре тест не дали. на будущее буду иметь ввиду, что такие наклонки глобальные видят все и от них врубают даже институционалы покупку, поэтому там лететь можно долго и сильно вверх нефть соплю вниз дала, откупили, да и всё пока. наш рынок решил на перехай идти. по 2м точкам-хаям (от 30.07 и 06.08) наклонка аж до 2330 спокойно рисуется, поэтому после задерга (перехай) жду небольшой откат, потом еще один финальны…
custom 543849646304475297218
стоп за 2281 (-0,05%) лишним не будет сейчас. пришли снова к наклонке/каналу и отскочили, мб что-то V-образное или ПГИП нарисует индекс и где-то на текущих заторгуется вправо сидеть и ждать палку на % на каком-то вбросе и по новой шарманка пойдет у пастухов, не хочется движение основное как будто уже случилось сегодня на мамбе вариант с ускорением вниз на вечерке не исключаю, но там лучше перезайду не пересылайт…
custom 543849646304475297212
вернул 1х плечо в шорте микса плечо: 2,5х средняя: 2280
custom 543849646304475297211
✅ фикс 1х по 2268 (+0,5%)
custom 543849646304475297214
добрал на 0,5х по цене средней плечо: 2,5х средняя: 2279
custom 543849646304475297211
думаю, одной палкой прошьют наклонку и потащат ниже сильно с плечами тоже разгоняться пока не стоит, но походу тут всем всё очевидно уже становится
custom 543849646304475297211
🏦 IMOEXF SHORT: 2279 leverage: 2х stop-market: ручной take-profit: ручной
custom 543849646304475297213
🏦 все шорты прикрыл, фул будку не грузил, но на хае добрал MIX 2,5х плеча в (+2,1%) SMLT 1х плечо в (+3,2%) раздал в ближайший час как будто нечего делать в рынке, пилиться надо
custom 543849646304475297211
🏦 зря Дед в самый хай сигу на покупку микса дает, будем ниже 2300 сегодня кто пока не видит нормальные точки входа, рекомендую обратить внимание на шорт серебра, там есть пространство с короткими стопами вниз покатать
custom 543849646304475297215
🏦 хочется нагрузить фул будку шорта в каждой второй акции, но могут подвынести до обеда, мб даже перехай по индексу (15% оценил бы вероятность), поэтому аккуратно пока
custom 543849646304475297218
🏦 фон негативный (удары по нпз в ярославле), нефть ниже 80$ зажимали вчера целый день на перехай, сделали к/на вечерке движение, утром по пустыми стаканам ещё пробросили и вот мы на 2305-2315 нефтянка в нуле, газпром в небольшом плюсе, он растёт последним думаю, это где-то тут хороший уровень, чтобы искать точку на шорт коррекция будет буквально за 2-3 дня и резко. такого вымученного роста как сейчас, зеркально в…
custom 543849646304475297214
Showing the 12 most recent of 20 posts we hold for @birch_trading. 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 — 955,948 of 1,478,351entries 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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“Берёзовый TRADING | IMOEX” (@birch_trading), 1,485 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/birch_trading.
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.