Telegram RegisterThe public register of Telegram
Telegram profile photo for JTT weekly (the one and only channel)

Channel

JTT weekly (the one and only channel)

@jttweekly

On this record: Growth · Engagement · Telegram's recommendations · Cite this entry

3,874subscribers

-63 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001327962069
TypeChannel
Username@jttweekly
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 September 2026
Last confirmed live10 September 2026
Measurements held13
Confirmed unchanged1 time, most recently 10 September 2026
On Telegramt.me/jttweekly

Growth

3,8743,9373,905.56 August 2026 — 3,937 subscribers7 August 2026 — 3,935 subscribers10 August 2026 — 3,927 subscribers13 August 2026 — 3,924 subscribers16 August 2026 — 3,918 subscribers19 August 2026 — 3,915 subscribers22 August 2026 — 3,910 subscribers25 August 2026 — 3,905 subscribers29 August 2026 — 3,898 subscribers1 September 2026 — 3,888 subscribers5 September 2026 — 3,882 subscribers6 September 2026 — 3,882 subscribers10 September 2026 — 3,874 subscribers6 August 202610 September 2026
13 measurements spanning 34 days, net -63. 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 3,865–3,946 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 06:203,874-8
6 Sept 2026, 00:083,882no change
5 Sept 2026, 09:363,882-6
1 Sept 2026, 07:463,888-10
29 Aug 2026, 00:353,898-7
25 Aug 2026, 17:543,905-5
22 Aug 2026, 18:233,910-5
19 Aug 2026, 18:063,915-3
16 Aug 2026, 21:163,918-6
13 Aug 2026, 18:073,924-3
10 Aug 2026, 19:213,927-8
7 Aug 2026, 16:573,935-2
6 Aug 2026, 23:313,937first 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.

KJo Academy FREE Crypto Channel
@kjoacademy · 28,858
Telegram ranks this channel #43 of 76 here — alongside 75 others — read 9 September 2026
www.rikopedia.com
@rikopedia · 27,400
Telegram ranks this channel #60 of 79 here — alongside 78 others — read 11 September 2026
The Whale
@WhaleDV · 28,931
Telegram ranks this channel #71 of 74 here — alongside 73 others — read 9 September 2026

This channel appears in 3 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 10 September 2026 — this entry's latest reading, not the date you are reading this.

“JTT weekly (the one and only channel)” (@jttweekly), 3,874 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/jttweekly.

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.