Telegram RegisterThe public register of Telegram

Channel

VISION | Арбитраж

@arbvision

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

1,445subscribers

-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-1002188951087
TypeChannel
Username@arbvision
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/arbvision

Growth

1,4451,4481,446.56 August 2026 — 1,448 subscribers7 August 2026 — 1,447 subscribers13 August 2026 — 1,445 subscribers6 August 202613 August 2026
3 measurements spanning 7 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,445–1,448 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 04:561,445-2
7 Aug 2026, 09:061,447-1
6 Aug 2026, 16:071,448first reading

Engagement

19 posts held, back to 24 June 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
31.4%
avg views ÷ 1,445 subscribers
Avg views / post
453
11 posts measured
Reaction rate
3.63%
reactions ÷ views · ER floor
Posts in window
12
of 19 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 9 of 11 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 3 August 2026
Posts held19 (24 June 20263 August 2026)
Views total4,986
Reactions total153
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 16:07 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

284 reactions across 15 posts, in 7 distinct kinds. The most used accounts for 33.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53323082370792889879633.8%
🏆6021.1%
💘4816.9%
👏279.51%
😁248.45%
💯165.63%
custom 5427067443400950650134.58%

Custom emoji. 2 of the rows above are 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 counts beside them areTelegram’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 19 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 284reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 24 June 2026 to 3 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

3 Aug 2026, 19:22 UTC326 views14 reactionsread 6 August 2026
Photo

$CATE пролили на дексе продав токенов на 500к баксов, была возможность зашортить на мексе и хорошенько отфлипать Вижен все оперативно отколил самым первым 🤝 Приобрести подписку | Документация проекта

custom 53323082370792889877🏆4💘2💯1

2 Aug 2026, 17:52 UTC353 views14 reactionsread 6 August 2026

Второй эфир — done! Уже намного сильнее почувствовалась та атмосфера, ради которой мы решили сделать эту движуху ежемесячной. Ребята стали заметно открытее, больше включались в разговор, задавали вопросы и делились мнениями. Пока не все до конца врубились, что эфиры будут проходить каждый месяц и что здесь важен голос каждого. Многие всё ещё слушают в записи, но со временем, уверены, участников в лайве станет больше

custom 53323082370792889878🏆3👏3

30 Jul 2026, 20:42 UTC427 views18 reactionsread 6 August 2026
Photo

Если вы все ещё следите за фэир прайсами, то сегодня была возможность забрать $IQV

👏6🏆5custom 53323082370792889875💘1custom 54270674434009506501

30 Jul 2026, 17:33 UTC404 viewsread 6 August 2026

🎉 Результаты розыгрыша: 🏆 Победитель: 1. Dmytro (@dirtyspeculator) ✔️Проверить результаты

30 Jul 2026, 17:13 UTC368 viewsread 6 August 2026

Фаст розыгрыш на подписку на вижен от Рутины @R00tina

30 Jul 2026, 13:00 UTC390 views13 reactionsread 6 August 2026

😁😆😁 Эфир уже сегодня в 20:00 МСК Скидки выключаем сразу после начала, успевайте 👍 Хочу уточнить что эфир проводится именно в приватке, много было вопросов в личке Приобрести подписку по скидке -30%

custom 53323082370792889878💘4💯1

29 Jul 2026, 09:42 UTC397 views24 reactionsread 6 August 2026
Photo

Все постоянно говорят про фомо. Якобы самый большой страх — упустить возможность. — Да фигня это. Мы каждый день что-то упускаем. Не купили какой-то токен нн токен по совету инфла который ничем не подкреплен, не зашли в спредик, не начали чем-то заниматься. И ничего, живем дальше. Мне кажется, куда страшнее другое Проснуться через несколько лет и понять, что ты просто постоянно боялся и поэтому проиграл, ты не р

😁10💯6custom 53323082370792889875🏆2custom 54270674434009506501

28 Jul 2026, 13:44 UTC448 views21 reactionsread 6 August 2026
Photo

Всем привет, у нас тут новый эфир — 30 июля 😮 Как и говорили ранее, эфиры в Vision Community будут проводиться каждый месяц. Этот эфир будет более техническим, нежели прошлый. Месяц был не самый рыбный, но арбитражи были. На эфире разберем ситуации, которые были за месяц, и, что немаловажно, разберем отдельные кейсы ребят. Каждый желающий может скинуть на хелпер свой сетап отработки, где он не может разобраться в

🏆9custom 53323082370792889877custom 54270674434009506504👏1

25 Jul 2026, 16:59 UTC519 views16 reactionsread 6 August 2026
Photo

Откупили? Признавайтесь 😡

custom 53323082370792889879👏4🏆3

22 Jul 2026, 17:47 UTC685 views18 reactionsread 6 August 2026
Photo

ЧТО ТАМ ПО $B2 На дексе произошел крупный слив токенов (сливали по 500к токенов в минуту) Можно было откупать и забрать вкусный профит, потому что токен безумно быстро откупали. Сигнал в Vision пришёл одним из первых — в 19:25:14 Приобрести подписку | Документация проекта

🏆10custom 53323082370792889876👏2

19 Jul 2026, 18:51 UTC669 views15 reactionsread 6 August 2026

Allbridge дали заработать перед финалом чемпионата мира по футбику Кто смог — грац! 👍 https://core.allbridge.io/explorer?page=47

👏7🏆4custom 53323082370792889873💘1

Showing the 12 most recent of 19 posts we hold for @arbvision. 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 — 323,398 of 1,160,990entries 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

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

“VISION | Арбитраж” (@arbvision), 1,445 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/arbvision.

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.