Telegram RegisterThe public register of Telegram
Telegram profile photo for Juzpips | TRD

Channel

Juzpips | TRD

@juzpips

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

1,189subscribers

-52 since we began measuring on 19 September 2026

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

Register entry

Telegram ID-1002048346738
TypeChannel
Username@juzpips
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded3 October 2026
Last confirmed live1 November 2026
Measurements held12
Confirmed unchanged1 time, most recently 1 November 2026
On Telegramt.me/juzpips

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 4 October 2026 and assigned it the closest of 31 fixed categories, at 54% 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

1,1891,2411,21519 September 2026 — 1,241 subscribers25 September 2026 — 1,237 subscribers3 October 2026 — 1,237 subscribers4 October 2026 — 1,220 subscribers11 October 2026 — 1,214 subscribers14 October 2026 — 1,206 subscribers17 October 2026 — 1,217 subscribers20 October 2026 — 1,210 subscribers23 October 2026 — 1,202 subscribers26 October 2026 — 1,199 subscribers29 October 2026 — 1,193 subscribers1 November 2026 — 1,189 subscribers19 September 20261 November 2026
12 measurements spanning 43 days, net -52. 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 1,181–1,249 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Nov 2026, 03:591,189-4
29 Oct 2026, 12:011,193-6
26 Oct 2026, 16:161,199-3
23 Oct 2026, 21:151,202-8
20 Oct 2026, 15:461,210-7
17 Oct 2026, 22:271,217+11
14 Oct 2026, 18:101,206-8
11 Oct 2026, 02:381,214-6
4 Oct 2026, 22:221,220-17
3 Oct 2026, 04:401,237no change
25 Sept 2026, 14:021,237-4
19 Sept 2026, 15:171,241first 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.

CryptoCopy
@cryptocopy · 100,929
Telegram ranks this channel #52 of 63 here — alongside 62 others — read 19 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 1 November 2026 — this entry's latest reading, not the date you are reading this.

“Juzpips | TRD” (@juzpips), 1,189 subscribers as measured 1 November 2026. Telegram Register, tgregister.com/channel/juzpips.

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.