Telegram RegisterThe public register of Telegram
Telegram profile photo for CrypTrox

Supergroup

CrypTrox

@cryptotrox

On this record: Topic · Growth · Engagement · Citations · Cite this entry

2,026members

-94 since we began measuring on 7 August 2026

54 online right now

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

Register entry

Telegram ID-1001766889505
TypeSupergroup
Username@cryptotrox
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded20 September 2026
Last confirmed live12 October 2026
Measurements held17
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/cryptotrox

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 20 September 2026 and assigned it the closest of 31 fixed categories, at 53% 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

2,0262,1202,0737 August 2026 — 2,120 members11 August 2026 — 2,117 members14 August 2026 — 2,110 members17 August 2026 — 2,108 members20 August 2026 — 2,099 members24 August 2026 — 2,098 members27 August 2026 — 2,097 members30 August 2026 — 2,094 members2 September 2026 — 2,093 members6 September 2026 — 2,085 members11 September 2026 — 2,081 members14 September 2026 — 2,074 members18 September 2026 — 2,064 members20 September 2026 — 2,064 members28 September 2026 — 2,055 members6 October 2026 — 2,043 members12 October 2026 — 2,026 members7 August 202612 October 2026
17 measurements spanning 66 days, net -94. 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 2,012–2,134 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
12 Oct 2026, 10:542,026-17
6 Oct 2026, 03:012,043-12
28 Sept 2026, 16:362,055-9
20 Sept 2026, 02:162,064no change
18 Sept 2026, 19:382,064-10
14 Sept 2026, 16:212,074-7
11 Sept 2026, 04:392,081-4
6 Sept 2026, 15:552,085-8
2 Sept 2026, 01:322,093-1
30 Aug 2026, 06:042,094-3
27 Aug 2026, 03:342,097-1
24 Aug 2026, 10:032,098-1
20 Aug 2026, 12:362,099-9
17 Aug 2026, 20:132,108-2
14 Aug 2026, 16:142,110-7
11 Aug 2026, 13:322,117-3
7 Aug 2026, 10:162,120first 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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

“CrypTrox” (@cryptotrox), 2,026 members as measured 12 October 2026. Telegram Register, tgregister.com/channel/cryptotrox.

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.