Channel
@kavex_ir
On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
4,178subscribers
+71 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001549420437 |
|---|---|
| Type | Channel |
| Username | @kavex_ir |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 August 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/kavex_ir |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 05:17 | 4,178 | -6 |
| 2 Sept 2026, 18:19 | 4,184 | -12 |
| 27 Aug 2026, 07:45 | 4,196 | +6 |
| 24 Aug 2026, 17:36 | 4,190 | +14 |
| 21 Aug 2026, 06:38 | 4,176 | +21 |
| 18 Aug 2026, 06:42 | 4,155 | +55 |
| 15 Aug 2026, 16:47 | 4,100 | -7 |
| 15 Aug 2026, 01:45 | 4,107 | first reading |
20 posts held, back to 8 August 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 1 page 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.
| Window | Rolling 30 days · latest post in window 14 August 2026 |
|---|---|
| Posts held | 20 (8 August 2026 – 14 August 2026) |
| Views total | 886 |
| Reactions total | 15 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Aug 2026, 01: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.
61 reactions across 20 posts, in 2 distinct kinds. The most used accounts for 82.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 50 | 82.0% | |
| 👍 | 11 | 18.0% |
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 20 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 61 reactions 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 8 August 2026 to 14 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.
🟠 #بیت_کوین 📉 همونطور که در تحلیل قبل گفتیم روند بیت کوین نزولیه و حتی اعلام کردیم برای لانگ گرفتن مناسب نیست! 📊 بیت کوین حمایت مهم خودش رو از دست داد و الان در حرکت به سمت اولین حمایت خودش یعنی ناحیه ۶۲۴۰۰ دلار هست. 🔻مادامیکه بیت کوین زیر مقاومت ۶۳۶۰۰ قرار داره اصلاح تا حمایت ۶۱۸۰۰ دلار هم میتونه ادامه دار باشه. 📲 Telegram 📲 Instagram
❤2
تحلیل بیت کوین در استوری اینستاگرام منتشر شد روی لینک زیر بزن و استوری رو ببین https://instagram.com/kavex.ir
❤4
🔴#شیبا در تایم فریم ۴ ساعته درون کانال نزولیه و ناحیه مهمی رو از دست داده یعنی محدوده 0.0000045$ 📉 درصورتی که طی ساعات آینده این ناحیه رو پس بگیره یک جهش قیمت رو تا ناحیه 0.0000050$ میتونه تجربه بکنه در غیر اینصورت روند نزولی تا محدوده 0.0000042$ ادامه دار خواهد بود که البته سناریو ریزشی فعلا برای این میم کوین محتمل تر هست. 📲 Telegram 📲 Instagram
👍3
🟠 #بیت_کوین متاسفانه بیس های صعودی ( حمایت های کلیدی ) خودش رو از دست داد و فعلا نزولی شده... 📈 در حال حاضر حمایت ۶۳۳۰۰ برای بیت کوین کلیدی هستش و باید به این ناحیه برسه و واکنشش رو ببینیم. در صورت حفظ این ناحیه به سمت بالا پولبک خواهد زد و بعد باید روند بررسی بشه که ببینیم روند نزولی ادامه دار خواهد بود یا نه؟! اگر این حمایت از دست بره اصلاح تا ۶۲۲۸۰ ادامه دار خواهد بود. همچنین مقاومتی که روند فعلی رو با شکستش تغی…
❤3
⚪️ #اتریوم لگ های صعودی (حمایت های کلیدی )خودش رو از دست داد و روندش نزولی شد و موفق به عبور از خط روند نزولی بلند مدتی هم نشد. 📈در حال حاضر حمایت ۱۸۵۰ بسیار مهمه و درصورتی که کندل یک یا ۴ ساعته زیرش بسته بشه اتریوم به سمت ۱۸۰۰ دلار حرکت نزولی خودش رو ادامه میده. فعلا باید منتظر واکنش به باکس حمایتی ۱۸۵۰ دلار باشیم. هر حرکت روبه بالا هم فعلا پولبک به بیس نزولی ( نقطه ای که آخرین حرکت نزولی آغاز شده ) هست مگر اینکه م…
👍3
تحلیل هر رمزارزی رو میخواین تو دایرکت اینستاگرام بهمون بگید به پیج زیر پیام بدید https://instagram.com/kavex.ir
❤3
همستر همون طور که اشاره شد ضعف روند داشت و ریخت.... روند صعودی رو از دست داده و فعلا چارت خوبی نداره!
❤3
✅ تحلیل #شاخص کل در استوری اینستاگرام منتشر شد. روی لینک زیر بزنید و استوری رو مشاهده کنید👇 👉https://instagram.com/kavex.ir
❤2
بیت کوین کانال نزولی یکساعته و مقاومت ها
❤2
بیت کوین کانال نزولی بلندمدت
❤2
🟠 #بیت_کوین در تایم فریم یکساعته کانال نزولی تشکیل داده بود که سقف کانال شکسته شد. 📈 در حال حاضر دوتا ناحیه مهم بیت کوین سر راه خودش داره که اگر موفق به عبور از این نواحی بشه روند میانمدتی هم میتونه عوض بشه!!! 📊 بیت کوین با شکست ۶۷۰۰۰ دلار میتونه روند روزانه رو تغییر بده و به سمت تارگت اول یعنی ۷۲۰۰۰ دلار حرکت بکنه. مقاومتی که بیت کوین برای رسیدن به ۶۷۰۰۰ دلار درگیرش هست محدوده ۶۵۳۰۰ دلاره که مقاومت تایم فریم های س…
❤7
اتریوم (تایم فریم روزانه)
❤2
Showing the 12 most recent of 20 posts we hold for @kavex_ir. 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.
Named by 3 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.
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 2 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 7 September 2026 — this entry's latest reading, not the date you are reading this.
“KAVEX” (@kavex_ir), 4,178 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/kavex_ir.
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.