Channel
@rezinv
On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cite this entry
19,839subscribers
-306 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001340914456 |
|---|---|
| Type | Channel |
| Username | @rezinv |
| Created | 10 October 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 29 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 29 September 2026 |
| On Telegram | t.me/rezinv |
Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 73% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Sept 2026, 21:00 | 19,839 | -92 |
| 17 Sept 2026, 22:18 | 19,931 | -8 |
| 15 Sept 2026, 20:56 | 19,939 | -7 |
| 14 Sept 2026, 07:41 | 19,946 | -6 |
| 12 Sept 2026, 13:01 | 19,952 | -6 |
| 10 Sept 2026, 09:17 | 19,958 | -23 |
| 7 Sept 2026, 01:22 | 19,981 | -15 |
| 4 Sept 2026, 10:00 | 19,996 | -16 |
| 2 Sept 2026, 23:55 | 20,012 | -6 |
| 1 Sept 2026, 19:16 | 20,018 | -5 |
| 31 Aug 2026, 20:35 | 20,023 | -3 |
| 30 Aug 2026, 19:26 | 20,026 | +2 |
| 29 Aug 2026, 19:14 | 20,024 | -3 |
| 28 Aug 2026, 18:34 | 20,027 | -2 |
| 27 Aug 2026, 21:54 | 20,029 | +2 |
| 26 Aug 2026, 19:24 | 20,027 | -3 |
| 25 Aug 2026, 22:49 | 20,030 | -2 |
| 25 Aug 2026, 02:05 | 20,032 | -8 |
| 23 Aug 2026, 16:06 | 20,040 | -4 |
| 22 Aug 2026, 01:36 | 20,044 | first reading |
104 posts held, back to 3 August 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 57 pages of 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 3 of 12 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 104 (3 August 2026 – 2 September 2026) |
| Views total | 20,468 |
| Reactions total | 20 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 00:57 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.
524 reactions across 58 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5427107837568360763 | 524 | 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 is Telegram’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 59 of the 104 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 524 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 104 most recent posts we hold, published 3 August 2026 to 2 September 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @rezinv. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 104 most recent posts we hold for this entry, published 3 August 2026 to 2 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
💳Какие акции обгонят рынок РФ? Посмотри обзор: imoex, rtsi, sbgb, ставка в рф, sber, gazp, vtbr, lkoh, gmkn, nvtk, afks, t, rosn, ydex, rual moex, ozon, aflt, vkco, smlt. Акции РФ с Резаном: https://boosty.to/rezaninv/posts/77d39175-4b35-4121-8ee4-e7d461d49f8d
custom 54271078375683607635
Подробнее в видео.
Текущие позиции в товарке, за которыми я слежу и участвую.
#pfe лонг гип с целью 36.
custom 54271078375683607633
💳Обвал золота лишь начало. Мы уже вложились в другие активы. Смотрим обзор gold, silver, gldrub, slvrub, platinum, palladium, nickel, zinc, aluminium, gas, brent, gasoline, copper, wheat, coffee. Товарные рынки с Резаном: https://boosty.to/rezaninv/posts/96c3ab32-6739-4c98-bdcb-24a67c397aa3
Лонгуем Мосбиржу с самого дна в разгоне. А вы ? 😎
custom 542710783756836076312
2.98% x8 🐂🤑😎
Чудесно
Был рост все выходные и утром гэп вверх.
8% прибыли зв выходные есть
Классика гип. В этот раз сработает.
Наращиваем MX. Все выходные будет рост.
Showing the 12 most recent of 104 posts we hold for @rezinv. 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.
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.
Named by 7 registered channels — 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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 29 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 13 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 29 September 2026 — this entry's latest reading, not the date you are reading this.
“Rezan Invest” (@rezinv), 19,839 subscribers as measured 29 September 2026. Telegram Register, tgregister.com/channel/rezinv.
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.