Telegram RegisterThe public register of Telegram
Telegram profile photo for RIRAVEX | FxPro Persian

Channel

RIRAVEX | FxPro Persian

@RIRAVEX

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

16,008subscribers

-286 since we began measuring on 26 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1004351187362
TypeChannel
Username@RIRAVEX
CreatedBetween 1 June 2026 and 21 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded26 August 2026
Last confirmed live4 September 2026
Measurements held10
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/RIRAVEX

Growth

16,00816,30516,156.526 August 2026 — 16,294 subscribers27 August 2026 — 16,291 subscribers28 August 2026 — 16,305 subscribers29 August 2026 — 16,246 subscribers30 August 2026 — 16,220 subscribers31 August 2026 — 16,167 subscribers1 September 2026 — 16,112 subscribers2 September 2026 — 16,101 subscribers3 September 2026 — 16,083 subscribers4 September 2026 — 16,008 subscribers26 August 20264 September 2026
10 measurements spanning 9 days, net -286. 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 15,963–16,350 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Sept 2026, 20:5716,008-75
3 Sept 2026, 07:0516,083-18
2 Sept 2026, 03:2616,101-11
1 Sept 2026, 00:5516,112-55
31 Aug 2026, 00:0716,167-53
30 Aug 2026, 03:0816,220-26
29 Aug 2026, 03:3516,246-59
28 Aug 2026, 02:4416,305+14
27 Aug 2026, 05:5516,291-3
26 Aug 2026, 15:0016,294first reading

Engagement

92 posts held, back to 21 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 15 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.44%
avg views ÷ 16,008 subscribers
Avg views / post
551
89 posts measured
Reaction rate
0.552%
reactions ÷ views · ER floor
Posts in window
92
of 92 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 81 of 89 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 September 2026
Posts held92 (21 August 20263 September 2026)
Views total49,001
Reactions total266
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 10:09 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

266 reactions across 81 posts, in 7 distinct kinds. The most used accounts for 68.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍18268.4%
🔥4015.0%
3312.4%
👌72.63%
👏20.752%
😁10.376%
🙏10.376%

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 81 of the 92 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 266 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 92 most recent posts we hold, published 21 August 2026 to 3 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.

Recent posts

3 Sept 2026, 08:53 UTC24 views1 reactionsread 3 September 2026

📊 RIRAVEX SIGNAL #72 EURUSD — BUY Entry: 1.1608 Stop Loss: 1.156 Take Profit 1: 1.166 Take Profit 2: 1.1705 Status: LIVE 🌐 افتتاح حساب FxPro در RIRAVEX.com

👍1

3 Sept 2026, 08:46 UTC24 views1 reactionsread 3 September 2026

📊 RIRAVEX SIGNAL #71 CADJPY — SELL Entry: 113.68 - 113.95 Stop Loss: 114.55 Take Profit 1: 113.2 Take Profit 2: 112.5 Status: LIVE 🌐 افتتاح حساب FxPro در RIRAVEX.com

👍1

3 Sept 2026, 08:03 UTC29 views1 reactionsread 3 September 2026

📊 RIRAVEX SIGNAL #70 — RESULT XAUUSD — SELL ❌ STOP LOSS HIT 🎯 Stop loss hit before any target Status: CLOSED 🌐 افتتاح حساب FxPro در RIRAVEX.com

👍1

3 Sept 2026, 07:06 UTC41 views3 reactionsread 3 September 2026

📊 RIRAVEX SIGNAL #70 XAUUSD — SELL Entry: 4427.68 Stop Loss: 4437.68 Take Profit: 4407.68 Status: LIVE 🌐 افتتاح حساب FxPro در RIRAVEX.com

👍2👏1

3 Sept 2026, 06:52 UTC43 views2 reactionsread 3 September 2026

📊 RIRAVEX SIGNAL #66 — RESULT AUDJPY — SELL ✅ TAKE PROFIT HIT 🎯 All 2 target(s) reached Status: CLOSED 🌐 افتتاح حساب FxPro در RIRAVEX.com

👍2

2 Sept 2026, 21:51 UTC188 views3 reactionsread 3 September 2026

📊 RIRAVEX SIGNAL #69 GBPNZD — BUY Entry: 2.3046 Stop Loss: 2.2996 Take Profit: 2.3146 Status: LIVE 🌐 افتتاح حساب FxPro در RIRAVEX.com

👍2😁1

2 Sept 2026, 16:06 UTC188 views3 reactionsread 3 September 2026

📊 RIRAVEX SIGNAL #68 EURUSD — SELL STOP Entry: 1.1554 Stop Loss: 1.1578 Take Profit: 1.1508 Status: PENDING 🌐 افتتاح حساب FxPro در RIRAVEX.com

👍21

2 Sept 2026, 14:02 UTC185 views2 reactionsread 3 September 2026

📊 RIRAVEX SIGNAL #67 — RESULT EURCAD — BUY ❌ STOP LOSS HIT 🎯 Stop loss hit before any target Status: CLOSED 🌐 افتتاح حساب FxPro در RIRAVEX.com

👍2

2 Sept 2026, 13:44 UTC170 views2 reactionsread 3 September 2026

📊 RIRAVEX SIGNAL #67 EURCAD — BUY Entry: 1.6115 Stop Loss: 1.6085 Take Profit 1: 1.615 Take Profit 2: 1.6185 Status: LIVE 🌐 افتتاح حساب FxPro در RIRAVEX.com

👍2

2 Sept 2026, 13:42 UTC154 views2 reactionsread 3 September 2026

📊 RIRAVEX SIGNAL #66 AUDJPY — SELL Entry: 114.15 Stop Loss: 114.75 Take Profit 1: 113.5 Take Profit 2: 112.55 Status: LIVE 🌐 افتتاح حساب FxPro در RIRAVEX.com

👍2

2 Sept 2026, 13:40 UTC104 views2 reactionsread 3 September 2026

📊 RIRAVEX SIGNAL #65 USDJPY — SELL Entry: 159.55 Stop Loss: 160.05 Take Profit 1: 159.0 Take Profit 2: 158.1 Status: LIVE 🌐 افتتاح حساب FxPro در RIRAVEX.com

👍2

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

Forward network

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 6 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.

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

“RIRAVEX | FxPro Persian” (@RIRAVEX), 16,008 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/RIRAVEX.

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.