یه ستاپ سووینگی خوب رو ZEC هست با اهرم ۷ همینجا سل بزنید ۲۰٪ اکانت معاملاتی تارگت ها 980 - 950 - 930 استاپ 1100 مدیریت سرمایه رعایت بسه
❤232😭78💔17🐳5👍1😍1

Channel
@javadtrade
On this record: Topic · Growth · Engagement · What this channel posts · View velocity · Reactions · Stars · Posts · Posts edited after publishing · Citations · Cite this entry
1,019,333subscribers
-58,482 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1001062811517 |
|---|---|
| Type | Channel |
| Username | @javadtrade |
| Description | من جواد حیدری ام ، بالای ۵ سال دارم تو حوزه ترید فعالیت میکنم و از کشاورزی به موفقیت رسیدم میخوام هر چیزی که بلدم و بهت رایگان یاد بدم 💰 بازار مالی ریسک داره و برای فعالیت باید حرفه ای یادش بگیری ❤️ @Goldentradervip_bot |
| Created | Between 1 May 2016 and 28 February 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 32 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/javadtrade |
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 92% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 09:19 | 1,019,333 | -1,989 |
| 15 Sept 2026, 11:19 | 1,021,322 | -1,662 |
| 13 Sept 2026, 20:38 | 1,022,984 | -2,171 |
| 12 Sept 2026, 01:01 | 1,025,155 | -3,013 |
| 9 Sept 2026, 14:56 | 1,028,168 | -3,975 |
| 6 Sept 2026, 04:59 | 1,032,143 | -3,545 |
| 4 Sept 2026, 00:57 | 1,035,688 | -2,549 |
| 2 Sept 2026, 14:18 | 1,038,237 | -1,426 |
| 1 Sept 2026, 12:34 | 1,039,663 | -967 |
| 31 Aug 2026, 14:53 | 1,040,630 | -1,290 |
| 30 Aug 2026, 17:55 | 1,041,920 | -1,890 |
| 29 Aug 2026, 19:26 | 1,043,810 | -1,491 |
| 28 Aug 2026, 17:08 | 1,045,301 | -1,482 |
| 27 Aug 2026, 19:13 | 1,046,783 | -987 |
| 26 Aug 2026, 20:18 | 1,047,770 | -1,112 |
| 25 Aug 2026, 20:52 | 1,048,882 | -1,519 |
| 24 Aug 2026, 19:04 | 1,050,401 | -2,325 |
| 23 Aug 2026, 02:57 | 1,052,726 | -2,697 |
| 21 Aug 2026, 15:06 | 1,055,423 | -2,301 |
| 20 Aug 2026, 12:22 | 1,057,724 | first reading |
67 posts held, back to 26 July 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 97 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.
| Window | Rolling 30 days · latest post in window 5 September 2026 |
|---|---|
| Posts held | 67 (26 July 2026 – 5 September 2026) |
| Views total | 166,430 |
| Reactions total | 5,944 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 22 Sept 2026, 06:54 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 22 September 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.
Measured directly from 2 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.
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 37 of this channel’s own posts over the last 30 days: across 36 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 18 hours of being posted; a typical post has already reached 25.8% of its 24-hour view count within the first hour, and 60.2% within the first six; the median 24-hour reach across those posts is 4,645 views — 0.444% of this channel’s own subscriber count (90th percentile 5,505).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /174028 Aug 2026, 09:32 UTC | 119 minutes – 19 minutes old | 853 views76 reactions | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /173924 Aug 2026, 09:29 UTC | 10642 minutes – 2 days old | 6,210 views ~393 reactions | 60 minutes: 1,730 → 3.0 hours: 2,750 → 6.0 hours: 3,420 → 12 hours: 4,200 → 24 hours: 4,920 → 2 days: 5,840still climbing at last reading | 4,920measured | 4.6 hours |
| /173824 Aug 2026, 09:28 UTC | 10542 minutes – 2 days old | 6,250 views ~317 reactions | 60 minutes: 1,770 → 3.0 hours: 2,760 → 6.0 hours: 3,440 → 12 hours: 4,220 → 24 hours: 4,930 → 2 days: 5,880still climbing at last reading | 4,930measured | 4.6 hours |
| /173722 Aug 2026, 04:11 UTC | 15523 minutes – 5 days old | 12,900 views ~380 reactions | 60 minutes: 1,340 interp. → 3.0 hours: 2,980 → 6.0 hours: 4,400 → 12 hours: 5,840 → 24 hours: 6,980 → 2 days: 8,390still climbing at last reading | 6,980measured | 16 hours |
| /173621 Aug 2026, 14:00 UTC | 2066 minutes – 5 days old | 6,380 views ~302 reactions | 60 minutes: 468 interp. → 3.0 hours: 758 → 6.0 hours: 1,040 → 12 hours: 1,250 → 24 hours: 1,920 → 2 days: 2,430still climbing at last reading | 1,920measured | 3 days |
| /173521 Aug 2026, 14:00 UTC | 2167 minutes – 5 days old | 8,660 views ~486 reactions | 60 minutes: 1,268 interp. → 3.0 hours: 2,040 → 6.0 hours: 2,660 → 12 hours: 3,060 → 24 hours: 4,430 → 2 days: 5,270still climbing at last reading | 4,430measured | 22 hours |
| /173421 Aug 2026, 13:59 UTC | 2147 minutes – 5 days old | 8,500 views ~281 reactions | 60 minutes: 1,320 interp. → 3.0 hours: 2,100 → 6.0 hours: 2,710 → 12 hours: 3,120 → 24 hours: 4,470 → 2 days: 5,310still climbing at last reading | 4,470measured | 21 hours |
| /173321 Aug 2026, 13:59 UTC | 2097 minutes – 5 days old | 8,130 views ~256 reactions | 60 minutes: 1,319 interp. → 3.0 hours: 2,090 → 6.0 hours: 2,710 → 12 hours: 3,110 → 24 hours: 4,460 → 2 days: 5,270still climbing at last reading | 4,460measured | 19 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.
23,686 reactions across 66 posts, in 6 distinct kinds. The most used accounts for 81.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 19,192 | 81.0% | |
| 👍 | 2,005 | 8.46% | |
| 💔 | 1,094 | 4.62% | |
| 😭 | 667 | 2.82% | |
| 🐳 | 438 | 1.85% | |
| 😍 | 290 | 1.22% |
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 66 of the 67 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 23,686 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 67 most recent posts we hold, published 26 July 2026 to 5 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @javadtrade. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 67 most recent posts we hold for this entry, published 26 July 2026 to 5 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
یه ستاپ سووینگی خوب رو ZEC هست با اهرم ۷ همینجا سل بزنید ۲۰٪ اکانت معاملاتی تارگت ها 980 - 950 - 930 استاپ 1100 مدیریت سرمایه رعایت بسه
❤232😭78💔17🐳5👍1😍1
فرصت عضویت کلاب 2X به پایان رسید ❤️
💔117❤93😭28👍10🐳6😍5
Video message, posted without a caption
❤143😭14💔4🐳1
بیداری ؟
👍477❤197💔24😍20🐳19😭13
لینک دو جلسه سبک 2X و کد های 207 👇 قسمت اول 👇 https://t.me/javadtrade11/3842 قسمت دوم 👇 https://t.me/javadtrade11/3875
❤229🐳10💔9👍3😍3😭1
اسمان منطقه داره کلیر میشه!
❤334😭80💔32🐳8👍4
بیانه سپاه ⚠️
❤241💔43👍10😍7🐳3😭2
🔴حتما تا آخر وویس رو گوش بده در مورد دریافت 207 و سبک معاملاتی 2X⚠️ با ریئکت ❤️ بهم انرژی بدید @javadtrade11
❤576👍13🐳11😭8
بیداری ؟
❤838👍145💔23🐳22😭15
⚠️⚠️⚠️برای شرکت در قرعه کشی 207 صفر سریع فرم زیر و پر کنید که اسمتون تو لیست باشه 👇👇👇 https://survey.porsline.ir/s/zpO7SNzT 🎁🎁🎁
❤422👍25💔12🐳10😭2
تورم نقطه به نقطه مواد غذایی
❤255💔64😭43😍5🐳2
واقعا شرایط داره از کنترل خارج میشه
👍259💔120❤69😭49🐳11😍3
Showing the 12 most recent of 67 posts we hold for @javadtrade. 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.
@javadtrade edited 1 post 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.
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 1 registered channel — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Javad Trade💰” (@javadtrade), 1,019,333 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/javadtrade.
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.