Telegram RegisterThe public register of Telegram
Telegram profile photo for JALWE TRADER

Channel

JALWE TRADER

@JalweTrader

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

19,186subscribers

-572 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002394725305
TypeChannel
Username@JalweTrader
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live3 November 2026
Measurements held57
Confirmed unchanged1 time, most recently 3 November 2026
On Telegramt.me/JalweTrader

Topic

Crypto & trading — 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 88% 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.

Growth

19,18319,82119,5027 August 2026 — 19,758 subscribers7 August 2026 — 19,758 subscribers8 August 2026 — 19,757 subscribers9 August 2026 — 19,752 subscribers10 August 2026 — 19,726 subscribers11 August 2026 — 19,689 subscribers12 August 2026 — 19,682 subscribers13 August 2026 — 19,668 subscribers14 August 2026 — 19,660 subscribers16 August 2026 — 19,668 subscribers17 August 2026 — 19,641 subscribers18 August 2026 — 19,662 subscribers19 August 2026 — 19,733 subscribers20 August 2026 — 19,808 subscribers22 August 2026 — 19,821 subscribers23 August 2026 — 19,816 subscribers25 August 2026 — 19,792 subscribers26 August 2026 — 19,787 subscribers27 August 2026 — 19,761 subscribers28 August 2026 — 19,772 subscribers29 August 2026 — 19,759 subscribers30 August 2026 — 19,746 subscribers31 August 2026 — 19,737 subscribers1 September 2026 — 19,711 subscribers1 September 2026 — 19,691 subscribers3 September 2026 — 19,668 subscribers4 September 2026 — 19,649 subscribers7 September 2026 — 19,607 subscribers10 September 2026 — 19,549 subscribers12 September 2026 — 19,532 subscribers14 September 2026 — 19,525 subscribers15 September 2026 — 19,494 subscribers18 September 2026 — 19,487 subscribers29 September 2026 — 19,441 subscribers5 October 2026 — 19,347 subscribers9 October 2026 — 19,351 subscribers13 October 2026 — 19,433 subscribers15 October 2026 — 19,409 subscribers16 October 2026 — 19,394 subscribers16 October 2026 — 19,380 subscribers17 October 2026 — 19,368 subscribers18 October 2026 — 19,353 subscribers19 October 2026 — 19,336 subscribers20 October 2026 — 19,317 subscribers21 October 2026 — 19,303 subscribers22 October 2026 — 19,287 subscribers23 October 2026 — 19,267 subscribers24 October 2026 — 19,249 subscribers25 October 2026 — 19,240 subscribers26 October 2026 — 19,226 subscribers27 October 2026 — 19,202 subscribers28 October 2026 — 19,200 subscribers29 October 2026 — 19,216 subscribers31 October 2026 — 19,203 subscribers1 November 2026 — 19,183 subscribers2 November 2026 — 19,195 subscribers3 November 2026 — 19,186 subscribers19,1867 August 20263 November 2026
57 measurements spanning 88 days, net -572. 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 19,087–19,917 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 57
Measured (UTC)SubscribersChange
3 Nov 2026, 04:3819,186-9
2 Nov 2026, 02:3819,195+12
1 Nov 2026, 02:0119,183-20
31 Oct 2026, 01:3819,203-13
29 Oct 2026, 22:5419,216+16
28 Oct 2026, 21:4519,200-2
27 Oct 2026, 23:4919,202-24
26 Oct 2026, 20:0019,226-14
25 Oct 2026, 19:5619,240-9
24 Oct 2026, 23:1519,249-18
23 Oct 2026, 22:4819,267-20
22 Oct 2026, 23:2119,287-16
21 Oct 2026, 22:5919,303-14
20 Oct 2026, 17:5019,317-19
19 Oct 2026, 16:3619,336-17
18 Oct 2026, 18:1619,353-15
17 Oct 2026, 20:3619,368-12
16 Oct 2026, 23:1519,380-14
16 Oct 2026, 01:5719,394-15
15 Oct 2026, 00:1819,409first reading

Engagement

98 posts held, back to 24 July 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 56 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
14.0%
avg views ÷ 19,186 subscribers
Avg views / post
2,690
19 posts measured
Reaction rate
0.992%
reactions ÷ views · ER floor
Posts in window
19
of 98 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 2 November 2026
Posts held98 (24 July 2026 – 2 November 2026)
Views total51,100
Reactions total507
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Nov 2026, 02:57 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

Video runtime
46s
Average length
46s

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.

Reaction mix

3,364 reactions across 98 posts, in 9 distinct kinds. The most used accounts for 43.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1,47443.8%
🔥43512.9%
👏38511.4%
🫡2387.07%
🙏2186.48%
😍2126.30%
👌1975.86%
🥰1253.72%
💯802.38%

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

Measured over the 98 most recent posts we hold, published 24 July 2026 to 2 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

2 Nov 2026, 23:01 UTC520 views11 reactionsread 3 November 2026
Photo

نتائج طرح اليوم اجمالي نسب الهدف الاول 67%

😍8👍2🥰1

29 Oct 2026, 16:09 UTC≈3,460 views20 reactionsread 3 November 2026
Photo

1.76 مساره السريع الله يطرح فيه البركة لا احد يدخل اذا مادخل من مناطقنا 1.56 - 1.50

👍16👏2🥰2

29 Oct 2026, 16:02 UTC≈2,930 views19 reactionsread 3 November 2026
Photo

داخلينه من مناطق 1.50 - 1.56 كما تم التنبيه منطقة طلبنا وهذه الاسهم الاسبوعية المناسبة لكم مثل اسهمكم السابقه الي انفجرت للاسف اسهم التجاوز الاسبوعية اذا طرحت لكم مباشرة البعض يشتري ويرتفع السهم بسيولة افراد مما يجعل السهم يتجاوز لان السهم اسبوعي ومافيه زخم وقت التنبيه عليه ، بالعادة ننتظر تجاوز حقيقي لذلك سيتم الاكتفاء فيها بالقناة الخاصة وطرح اسهم الطلب لكم

👍11👏7🔥1

29 Oct 2026, 15:41 UTC≈2,460 views13 reactionsread 3 November 2026

السهم اسبوعي لازال صالح بالتجاوز بالماركت فقط هذي مشكلة الاسهم الاسبوعية عندما نطرحها بالتجاوز السهم اسبوعي يعني خالي من الزخم اللحظي والدخول بالتجاوز " مع دخول الزخم " ولكن الواقع ان السهم ارتفع بسيولة البعض ممن يشتري قبل التجاوز ويرتفع السهم من سيولة بعضكم وبالتالي الكثير يدخل بالتجاوز لذلك الفترة الاخيره قليل نطرح فرص اسبوعية بالقناة العامة لهالسبب .. واوقات نضطر طرحها بالطلب وليس بالتجاوز

👍12🔥1

29 Oct 2026, 06:06 UTC≈2,490 views12 reactionsread 3 November 2026

https://x.com/jalwetrader/status/2115685062243213804?s=52

👍11🔥1

28 Oct 2026, 08:25 UTC≈2,660 views26 reactionsread 3 November 2026

انتبه له اذا حقق دخول

👍21🔥3👌2

28 Oct 2026, 08:12 UTC≈2,690 views102 reactionsread 3 November 2026

تبون تشوفون الاسهم المرشحه للصعود من التطبيق ؟ حالياً جاهزه 5 اسهم 😁 اي لحظة تنطلق

👍60🔥21🙏13👏4🥰4

28 Oct 2026, 08:09 UTC≈2,720 views18 reactionsread 3 November 2026
Photo

ELPW رغم ان توقعنا انه يكسر دعمه الا انه ماكسر وحقق مستهدف التطبيق كان دقيق بالتوقع

👍15🔥3

28 Oct 2026, 07:11 UTC≈2,540 views20 reactionsread 3 November 2026

PGY سهم السوينق محقق دخول

👍18🔥2

28 Oct 2026, 06:11 UTC≈2,670 views28 reactionsread 3 November 2026
Photo

WORX للمراقبة اليوم بتجاوز 2.00 وقف 1.85

👍16🔥12

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

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

“JALWE TRADER” (@JalweTrader), 19,186 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/JalweTrader.

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.