Channel
Trade With Jp Group
@tradewithjpgroup
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,844subscribers
-151 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002114222380 |
|---|---|
| Type | Channel |
| Username | @tradewithjpgroup |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 5 September 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/tradewithjpgroup |
Topic
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 10:21 | 3,844 | -15 |
| 14 Sept 2026, 19:58 | 3,859 | -8 |
| 10 Sept 2026, 20:38 | 3,867 | -40 |
| 5 Sept 2026, 23:38 | 3,907 | no change |
| 5 Sept 2026, 20:17 | 3,907 | -17 |
| 1 Sept 2026, 08:17 | 3,924 | +3 |
| 29 Aug 2026, 04:08 | 3,921 | +2 |
| 26 Aug 2026, 14:53 | 3,919 | -14 |
| 23 Aug 2026, 18:45 | 3,933 | -9 |
| 20 Aug 2026, 07:37 | 3,942 | -12 |
| 17 Aug 2026, 12:28 | 3,954 | -23 |
| 14 Aug 2026, 06:13 | 3,977 | -18 |
| 10 Aug 2026, 18:30 | 3,995 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Appears in Telegram’s recommendations for other channels
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.
@tradingtimesofficial · 45,740
Telegram ranks this channel #2 of 71 here — alongside 70 others — read 27 August 2026
@ftafatjobs · 26,407
Telegram ranks this channel #10 of 53 here — alongside 52 others — read 12 September 2026
@tradewithvikasofficial · 25,932
Telegram ranks this channel #12 of 59 here — alongside 58 others — read 14 September 2026
@tradermannugupta · 86,257
Telegram ranks this channel #14 of 81 here — alongside 80 others — read 18 August 2026
@tradewithsunilfreegroup · 265,721
Telegram ranks this channel #19 of 82 here — alongside 81 others — read 10 August 2026
@thetradingprofessor · 43,939
Telegram ranks this channel #76 of 78 here — alongside 77 others — read 28 August 2026
This channel appears in 6 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Trade With Jp Group” (@tradewithjpgroup), 3,844 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/tradewithjpgroup.
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.