Channel
Jymback
@jymback
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,219subscribers
-237 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001681643462 |
|---|---|
| Type | Channel |
| Username | @jymback |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 September 2026 |
| Last confirmed live | 31 October 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 31 October 2026 |
| On Telegram | t.me/jymback |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Oct 2026, 01:56 | 4,219 | -7 |
| 27 Oct 2026, 19:26 | 4,226 | -5 |
| 25 Oct 2026, 04:48 | 4,231 | -7 |
| 22 Oct 2026, 14:58 | 4,238 | -14 |
| 19 Oct 2026, 08:55 | 4,252 | -8 |
| 16 Oct 2026, 12:46 | 4,260 | -9 |
| 13 Oct 2026, 14:56 | 4,269 | -28 |
| 7 Oct 2026, 11:20 | 4,297 | -17 |
| 30 Sept 2026, 06:56 | 4,314 | -29 |
| 19 Sept 2026, 12:57 | 4,343 | -11 |
| 14 Sept 2026, 17:56 | 4,354 | -4 |
| 11 Sept 2026, 06:57 | 4,358 | -10 |
| 6 Sept 2026, 12:36 | 4,368 | -15 |
| 3 Sept 2026, 22:45 | 4,383 | no change |
| 1 Sept 2026, 20:27 | 4,383 | -8 |
| 29 Aug 2026, 19:25 | 4,391 | -11 |
| 27 Aug 2026, 05:11 | 4,402 | -10 |
| 23 Aug 2026, 23:06 | 4,412 | -16 |
| 20 Aug 2026, 05:52 | 4,428 | -12 |
| 17 Aug 2026, 12:35 | 4,440 | 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.
@shahaberfaniking · 20,210
Telegram ranks this channel #8 of 67 here — alongside 66 others — read 25 September 2026
@mehdiw_vibe · 50,541
Telegram ranks this channel #14 of 74 here — alongside 73 others — read 27 August 2026
@bodybuilding_IFBB · 41,524
Telegram ranks this channel #27 of 74 here — alongside 73 others — read 5 September 2026
@prorimixI · 247,658
Telegram ranks this channel #39 of 72 here — alongside 71 others — read 11 August 2026
@WanTbeVoice · 26,228
Telegram ranks this channel #42 of 79 here — alongside 78 others — read 11 September 2026
This channel appears in 5 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 31 October 2026 — this entry's latest reading, not the date you are reading this.
“Jymback” (@jymback), 4,219 subscribers as measured 31 October 2026. Telegram Register, tgregister.com/channel/jymback.
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.