Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝐁𝐞𝐡𝐫𝐨𝐨𝐳 𝐓𝐫𝐚𝐝𝐞

Channel

𝐁𝐞𝐡𝐫𝐨𝐨𝐳 𝐓𝐫𝐚𝐝𝐞

@Behrooz_Trade

Not marked by Telegram, checked 21 August 2026

On this record: Topic · Observations · Growth · Engagement · What this channel posts · View velocity · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Cite this entry

1,969,209subscribers

-344,049 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among the largest entries.

Register entry

Telegram ID-1001699462137
TypeChannel
Username@Behrooz_Trade
Description💎 ما عجله نداریم؛ دقیق حرکت می‌کنیم 📊 هر سیگنال نتیجه فکره، نه حدس 🤝 اینجا رفیقی، نه «فالوئر» 🧠 نظم، آرامش و سودِ تمیز 🚀 بلند نمیگیم؛ ولی بلند میریم Support : @BehroozTrad_Support
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live16 November 2026
Measurements held66
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/Behrooz_Trade

Topic

Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 63% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Views and reactions moved apart

On 40 of the 95 posts we watched over 30 days, the view counter climbed while the reaction counter stayed where it was — by more than this channel’s own reactions-per-view rate can account for. That rate, measured on this entry, is 0.1636 reactions per view.

Each interval, as we read it — views and reactions before and after
PostOverViewsReactionsExpected
/254228 Oct 2026, 12:50 UTC48 minutes1,530 → 1,790at least +250918 → 918at most +1+40.9
/254228 Oct 2026, 12:50 UTC55 minutes1,830 → 2,160at least +320918 → 918at most +1+52.4
/254228 Oct 2026, 12:50 UTC4 days3,910 → 5,220at least +1,300919 → 919at most +1+212.7
/253227 Oct 2026, 13:29 UTC35 minutes1,410 → 1,760at least +340331 → 333at most +3+55.6
/253227 Oct 2026, 13:29 UTC30 minutes1,760 → 2,080at least +310333 → 333at most +1+50.7
/254128 Oct 2026, 12:10 UTC55 minutes1,960 → 2,270at least +300815 → 815at most +1+49.1
/254128 Oct 2026, 12:10 UTC4 days4,230 → 5,400at least +1,160816 → 816at most +1+189.8
/254328 Oct 2026, 13:33 UTC55 minutes1,360 → 1,740at least +370755 → 755at most +1+60.5
/254328 Oct 2026, 13:33 UTC4 days3,420 → 4,030at least +600756 → 756at most +1+98.2
/254428 Oct 2026, 14:43 UTC35 minutes1,380 → 1,610at least +220675 → 675at most +1+36.0
/254428 Oct 2026, 14:43 UTC4 days3,440 → 4,030at least +580677 → 677at most +1+94.9
/254628 Oct 2026, 16:41 UTC30 minutes1,210 → 1,430at least +210840 → 840at most +1+34.4
/254628 Oct 2026, 16:41 UTC35 minutes1,430 → 1,800at least +360840 → 840at most +1+58.9
/256630 Oct 2026, 12:03 UTC35 minutes1,300 → 1,550at least +240502 → 502at most +1+39.3
/256630 Oct 2026, 12:03 UTC20 minutes1,550 → 1,800at least +240502 → 502at most +1+39.3
/256730 Oct 2026, 12:46 UTC35 minutes1,190 → 1,460at least +260716 → 716at most +1+42.5
/256730 Oct 2026, 12:46 UTC20 minutes1,460 → 1,720at least +250716 → 716at most +1+40.9
/260314 Nov 2026, 17:01 UTC34 minutes1,550 → 1,810at least +250768 → 768at most +1+40.9
/260314 Nov 2026, 17:01 UTC35 minutes1,810 → 2,220at least +400768 → 768at most +1+65.4
/260414 Nov 2026, 17:01 UTC34 minutes1,700 → 2,000at least +290949 → 950at most +2+47.4
/260414 Nov 2026, 17:01 UTC35 minutes2,000 → 2,400at least +390950 → 950at most +1+63.8

Expected is the view gain multiplied by this channel’s own prior reactions-per-view rate over the same post — not a corpus average, so a channel whose audience never reacts is compared only against itself. Every interval is credited in the direction that makes the observation harder to record, never easier: t.me renders views and reactions to three significant figures above ~1,000, so a raw delta can be a rendering step. Every delta below is at least 4 x the coarser reading's step, the view gain is discounted by a full step and the reaction gain credited with one. Measured by tgregister velocity.py (our own t.me/s/ readings).

What this does and does not say. It says the two counters moved apart, by more than rounding and more than this channel’s own history predicts. It asserts no cause. Views arriving from outside Telegram, an embedded or forwarded copy of the post, and a burst of readers who simply do not react all produce this shape. This detector has recorded very few observations across the whole register, and its precision has not been measured; treat it as an anomaly worth looking at, not as a finding.

Recorded under the key view_reaction_decoupling, last confirmed 18 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

1,969,2092,654,2182,311,713.57 August 202616 November 2026
66 measurements spanning 101 days, net -344,049. 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,866,458–2,756,969 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 66
Measured (UTC)SubscribersChange
16 Nov 2026, 17:561,969,209-16,612
13 Nov 2026, 05:071,985,821-10,301
10 Nov 2026, 23:481,996,122-6,782
9 Nov 2026, 11:412,002,904-5,989
8 Nov 2026, 02:202,008,893-5,609
6 Nov 2026, 20:472,014,502-4,759
5 Nov 2026, 20:262,019,261-5,566
4 Nov 2026, 18:462,024,827-4,853
3 Nov 2026, 16:092,029,680-3,760
2 Nov 2026, 18:012,033,440-3,593
1 Nov 2026, 20:482,037,033-5,546
31 Oct 2026, 17:382,042,579-4,754
30 Oct 2026, 17:362,047,333-7,776
29 Oct 2026, 14:362,055,109-6,857
28 Oct 2026, 12:372,061,966-6,005
27 Oct 2026, 12:052,067,971-5,465
26 Oct 2026, 10:282,073,436-4,041
25 Oct 2026, 12:552,077,477-5,850
24 Oct 2026, 11:342,083,327-7,360
23 Oct 2026, 07:562,090,687first reading

Engagement

485 posts held, back to 5 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 216 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.28%
avg views ÷ 1,969,209 subscribers
Avg views / post
5,510
87 posts measured
Reaction rate
13.8%
reactions ÷ views · ER floor
Posts in window
87
of 485 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 17 November 2026
Posts held485 (5 August 2026 – 17 November 2026)
Views total479,650
Reactions total66,207
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Nov 2026, 12:10 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.

What this channel posts

Photos
466
Videos
14
Links
68

Lifetime counters from Telegram’s own channel header, read 18 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
16s
Average length
16s

Measured directly from 1 video 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.

View velocity

How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.

Computed from 95 of this channel’s own posts over the last 30 days: across 89 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 10.0 hours of being posted; a typical post has already reached 39.5% of its 24-hour view count within the first hour, and 72.7% within the first six; the median 24-hour reach across those posts is 2,980 views — 0.151% of this channel’s own subscriber count (90th percentile 3,720).

8 most recently posted, with a view-velocity reading
PostReadingsLatest readingCurve24h reachHalf of last-observed views by
/261317 Nov 2026, 13:36 UTC3714 minutes – 23 hours old1,740 views ~12 reactions60 minutes: 496 interp. → 3.0 hours: 832 → 6.0 hours: 1,180 → 12 hours: 1,410still climbing at last readingnot yet at 24h3.2 hoursprovisional — final view count still climbing
/261217 Nov 2026, 09:44 UTC4311 minutes – 26 hours old2,470 views ~47 reactions60 minutes: 548 interp. → 3.0 hours: 955 interp. → 6.0 hours: 1,620 → 12 hours: 2,150 → 24 hours: 2,390still climbing at last reading2,390measured4.0 hours
/261117 Nov 2026, 09:43 UTC4112 minutes – 26 hours old2,550 views ~121 reactions60 minutes: 636 interp. → 3.0 hours: 1,020 interp. → 6.0 hours: 1,710 → 12 hours: 2,240 → 24 hours: 2,470still climbing at last reading2,470measured3.9 hours
/261016 Nov 2026, 11:48 UTC3623 minutes – 22 hours old2,280 views ~56 reactions60 minutes: 551 → 3.0 hours: 933 interp. → 6.0 hours: 1,380 → 12 hours: 1,910still climbing at last readingnot yet at 24h4.3 hoursprovisional — final view count still climbing
/260814 Nov 2026, 21:10 UTC12824 minutes – 4 days old5,970 views ~721 reactions60 minutes: 983 → 3.0 hours: 1,140 → 6.0 hours: 1,230 → 12 hours: 1,710 → 24 hours: 2,280 → 2 days: 4,040still climbing at last reading2,280measured39 hours
/260714 Nov 2026, 19:59 UTC12431 minutes – 4 days old5,900 views ~820 reactions60 minutes: 1,500 → 3.0 hours: 1,862 interp. → 6.0 hours: 1,970 interp. → 12 hours: 2,340 → 24 hours: 2,850 → 2 days: 4,270still climbing at last reading2,850measured28 hours
/260614 Nov 2026, 19:27 UTC12127 minutes – 4 days old5,340 views ~708 reactions60 minutes: 1,560 → 3.0 hours: 1,993 interp. → 6.0 hours: 2,103 interp. → 12 hours: 2,360 → 24 hours: 2,780 → 2 days: 3,880still climbing at last reading2,780measured20 hours
/260514 Nov 2026, 17:02 UTC1099 minutes – 4 days old4,400 views ~880 reactions60 minutes: 1,313 interp. → 3.0 hours: 1,930 → 6.0 hours: 2,668 interp. → 12 hours: 2,850 → 24 hours: 3,230 → 2 days: 3,750still climbing at last reading3,230measured3.3 hours

Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.

Reaction mix

190,738 reactions across 484 posts, in 7 distinct kinds. The most used accounts for 26.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤50,50426.5%
👍35,48418.6%
🔥33,99117.8%
🎉32,55317.1%
🐳26,32813.8%
💋10,5295.52%
⚡1,3490.707%

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 484 of the 485 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 190,738 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 485 most recent posts we hold, published 5 August 2026 to 17 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.

Recent posts

Telegram’s own ‘edited’ marker: 2 of 87 posts held from the last 30 days (2.30%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

17 Nov 2026, 13:36 UTC≈1,740 views12 reactionsread 18 November 2026
Photo

بیت کوین تایم فریم پانزده دقیقه ببینم پولبک باشه می‌تونه بره برای باکس قرمز

❤12

17 Nov 2026, 09:44 UTC≈2,470 views47 reactionsread 18 November 2026

استارت کنیم ؟

👍30❤12🔥4🎉1

17 Nov 2026, 09:43 UTC≈2,550 views121 reactionsread 18 November 2026

بِسْمِ ٱللَّٰهِ ٱلرَّحْمَٰنِ ٱلرَّحِيمِ

🐳109❤12

14 Nov 2026, 21:10 UTC≈5,970 views721 reactionsread 18 November 2026
Photo

💵Magic 👆واچ لیست بزارین تایید بده میزارم تریگرشو

🐳201👍121❤117🔥116🎉114💋52

14 Nov 2026, 19:59 UTC≈5,900 views820 reactionsread 18 November 2026
Photo

🪙BTC ⏰15m

🔥180❤170🎉152👍142🐳118💋58

14 Nov 2026, 19:27 UTC≈5,340 views708 reactionsread 18 November 2026
Photo

🧲این کجا و آن کجا! 🔴 ۲۰۲۱ در مقابل ۲۰۲۶ ۵ سال گذشته، اما به قیمت‌ها نگاه کنید! 🪙 بیت‌کوین: ۶۷ هزار ← ۶۶ هزار دلار 🔽 اتریوم: ۴,۸۰۰ ← ۱,۹۰۰ دلار 🔽 سولانا: ۲۶۰ ← ۷۵ دلار 🔽 دوج‌کوین: ۰.۷۲ ← ۰.۰۷ دلار 🔽 کاردانو: ۳ ← ۰.۱۸ دلار 🔽 آوالانچ: ۱۴۰ ← ۶ دلار ⚠️ بعضی آلت‌کوین‌ها نسبت به سقف‌های تاریخی‌شون بیش از ۹۰٪ سقوط کردن! 🗣️ یه حقیقت تلخ: 🔼اینکه یه ارز ۹۰٪ ریخته، دلیل نمی‌شه ارزون باشه یا حتماً به سقف قبلیش برگرده! …

👍150🎉141❤124🔥119🐳107💋67

14 Nov 2026, 17:02 UTC≈4,400 views880 reactionsread 18 November 2026

🛒 نباشم انگار حال نمیده

🐳197🎉160❤148🔥140👍138💋97

14 Nov 2026, 17:01 UTC≈4,510 views955 reactionsread 18 November 2026

❔سیگنال بزنیم الان یا تحلیل ؟ سیگنال ناب ⚡️ تحلیل خوشگل ❤️

👍213🐳170🔥165❤164🎉146💋97

14 Nov 2026, 17:01 UTC≈4,260 views770 reactionsread 18 November 2026

بِسْمِ ٱللَّٰهِ ٱلرَّحْمَٰنِ ٱلرَّحِيمِ

🐳196👍131🔥122❤117🎉106💋98

12 Nov 2026, 19:57 UTC≈5,740 views533 reactionsread 18 November 2026

🥂 سیگنال امروز – ویژه 💰 ارز: BAT / USDT 👇شورت 🛍 لوریج: 15X ⬅️ نرخ ورود: 0.1275 , 0.1238 💵اهداف : 0.1232 – 0.1195 –0.1157 🔠حد ضرر: 0.1325 ⚡ نکته: عجله نکن، با صبر و تمرکز حرکت کن؛ مدیریت سرمایه همیشه اولویت است

🐳156❤103🔥82🎉78👍69💋45

12 Nov 2026, 15:11 UTC≈5,110 views874 reactionsread 18 November 2026
Photo

💵ATOM 📎خط روند نزولی رو نصفه نیمه شکسته 📈اگر تثبیت بده میتونه رشد خوبی داشته باشه

👍166🎉159❤154🐳152🔥143💋100

12 Nov 2026, 15:07 UTC≈4,390 views753 reactionsread 18 November 2026
Photo

💵GRAM 📈گرام تایم فریم چهار ساعته

🐳206❤125🎉125👍117🔥108💋72

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

Posts edited after publishing

@Behrooz_Trade edited 6 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
21 September 2026
Most recent edit
30 October 2026

Posts recorded as deleted after publishing

We recorded 11 posts on @Behrooz_Trade as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
14 August 2026
Most recent seen missing
17 November 2026
Median time before seen missing
28 hours
Seen missing in the last 30 days
8

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

“𝐁𝐞𝐡𝐫𝐨𝐨𝐳 𝐓𝐫𝐚𝐝𝐞” (@Behrooz_Trade), 1,969,209 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/Behrooz_Trade.

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.