Channel
@nerkhe_r0uz
On this record: Topic · Previous handles · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
26,542subscribers
+7,581 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001311212974 |
|---|---|
| Type | Channel |
| Username | @nerkhe_r0uz |
| Description | 🔺کارگزاری خدمات مالی و ارزی نرخ روز” 🔺انجام کلیه امور تبادلات ارزی و مالی بیش از ۱۲۰ کشور جهان✔️ 🔺حواله های ارزی به حساب ها شرکتی #دلار🇺🇸 #یورو🇪🇺 #یوان🇨🇳 #درهم🇦🇪 #پوند🇬🇧 #لیر🇹🇷 🔹خرید فروش USDT ( تتر ) 🔹حواله های یوآن با Alipay🔹 🔹یوآن |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 August 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 47 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/nerkhe_r0uz |
Other / unclassifiable — 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 79% 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 the other topics.
@nerkhe_r0uz was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Nov 2026, 04:28 | 26,542 | -6 |
| 2 Nov 2026, 06:31 | 26,548 | -65 |
| 1 Nov 2026, 03:50 | 26,613 | -8 |
| 31 Oct 2026, 06:07 | 26,621 | -82 |
| 30 Oct 2026, 08:06 | 26,703 | -105 |
| 29 Oct 2026, 05:39 | 26,808 | -291 |
| 28 Oct 2026, 00:48 | 27,099 | -62 |
| 26 Oct 2026, 23:38 | 27,161 | -79 |
| 26 Oct 2026, 00:54 | 27,240 | -41 |
| 25 Oct 2026, 00:45 | 27,281 | -109 |
| 23 Oct 2026, 21:45 | 27,390 | -340 |
| 22 Oct 2026, 18:40 | 27,730 | -511 |
| 21 Oct 2026, 12:40 | 28,241 | -148 |
| 20 Oct 2026, 06:20 | 28,389 | -141 |
| 19 Oct 2026, 02:55 | 28,530 | -91 |
| 18 Oct 2026, 02:56 | 28,621 | +25 |
| 17 Oct 2026, 02:55 | 28,596 | -122 |
| 16 Oct 2026, 03:55 | 28,718 | -46 |
| 15 Oct 2026, 02:31 | 28,764 | -179 |
| 13 Oct 2026, 19:40 | 28,943 | first reading |
1,589 posts held, back to 15 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 123 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 135 of 631 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 3 November 2026 |
|---|---|
| Posts held | 1,589 (15 August 2026 – 3 November 2026) |
| Views total | 198,525 |
| Reactions total | 152 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Nov 2026, 05:13 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.
Lifetime counters from Telegram’s own channel header, read 3 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
262 reactions across 186 posts, in 17 distinct kinds. The most used accounts for 51.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 136 | 51.9% | |
| 👎 | 53 | 20.2% | |
| 🤣 | 22 | 8.40% | |
| 😁 | 15 | 5.73% | |
| 👍 | 9 | 3.44% | |
| custom 5210952531676504517 | 7 | 2.67% | |
| 🤬 | 5 | 1.91% | |
| custom 5206607081334906820 | 3 | 1.15% | |
| 😇 | 3 | 1.15% | |
| 😐 | 2 | 0.763% | |
| custom 5956331298304824285 | 1 | 0.382% | |
| 🔥 | 1 | 0.382% | |
| 😱 | 1 | 0.382% | |
| 🤩 | 1 | 0.382% | |
| 🤯 | 1 | 0.382% | |
| 🥰 | 1 | 0.382% | |
| 🥴 | 1 | 0.382% |
Custom emoji. 3 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 are 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 209 of the 1,000 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 262 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 19 September 2026 to 3 November 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.
🌐💱 کلیه خدمات ارزی و مالی فردوسی ارائه خدمات تخصصی حواله ارزی، انتقال وجه و تسویه بینالمللی برای اشخاص، بازرگانان و شرکتها: 1️⃣ انجام کلیه حوالجات ارزی شامل یورو، دلار و پوند 2️⃣ اعلام نرخ دقیق و بهروز درهم، حواله دلار، یورو و یوان چین 3️⃣ ارائه درهم نقدی و تحویل در کشور امارات 🇦🇪 4️⃣ واریز درهم به حساب بانکی در بانکهای امارات متحده عربی 5️⃣ تحویل حضوری یورو در اتریش، مجارستان و آلمان 🇪🇺 6️⃣ انجام حوالجات …
❤1
🇴🇲 خدمات حواله ریال عمان 🔹 نرخ رقابتی و بهروز 🔹 تسویه سریع 🔹 هماهنگی دقیق و مطمئن
🌐💱 خرید و فروش تتر (USDT) 💵 خرید و فروش با نرخ رقابتی و قیمت بهروز بازار ⚡ تسویه سریع و مطمئن 🤝 اعلام شفاف نرخ و شرایط قبل از معامله
حواله چین 💸 یوان چین با بهترین قیمت روزانه موجود است ✅
🇨🇦 خدمات تخصصی حواله کانادا انجام حواله به حسابهای شخصی و شرکتی در کانادا انجام حواله و پرداخت به دانشگاههای کانادا💸 مناسب برای پرداختهای شخصی،تجاری و شهریه دانشگاه
حواله دستی و واریز به حساب ✅💸 دلار امریکا سویفت با کمترین کارمزد و سریع ترین زمان ✅
دوستانی که درهم برای فروش دارند اعلام کنن به بالا ترین قیمت خریداریم ✅
لیر ، دلار ، پوند ، یورو شما را به بالاترین قیمت خریداریم ✅
صبح سهشنبهتون بخیر 🌿💚 ۱۲ آبان ۱۴۰۵ | ۳ نوامبر ۲۰۲۶ 📅 امروزتون پر از آرامش، رزق و برکت و خبرهای خوب ✨🌱 #صبح_بخیر
▫️ نرخ تتر: 273,611 تومان ــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــ تاریخ: 1405/08/11 ساعت: 18:05
▫️ پـایـان معـاملات امـروز صـرافی خسته نباشیـد 🌺
ا🇦🇪 خرید و فروش روزانه درهم امارات (AED)🇦🇪 🔸 خرید نقدی و حواله درهم با نرخ منصفانه و تسویه آنی 🔸 فروش درهم و امکان تسویه روزانه و فردایی 🔸 تسویه به حسابهای شخصی و شرکتی 💱 نرخ روزانه، آماده ارائه خدمات خرید و فروش درهم امارات میباشد. 💰📲 جهت انجام معامله: https://wa.me/971527166669
👎1
Showing the 12 most recent of 1,589 posts we hold for @nerkhe_r0uz. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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 41 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
@nerkhe_r0uz named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 16 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 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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“نرخ روزانه 💰” (@nerkhe_r0uz), 26,542 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/nerkhe_r0uz.
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.