Telegram RegisterThe public register of Telegram
Telegram profile photo for Julian Assange

Channel

Julian Assange

@Julian_AssangeWikiLeaks

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

1,992subscribers

-47 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001502089761
TypeChannel
Username@Julian_AssangeWikiLeaks
Description⚠️ Warning: Many users report that this account impersonates a famous person or organisation.
Created15 September 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded21 September 2026
Last confirmed live21 September 2026
Measurements held14
On Telegramt.me/Julian_AssangeWikiLeaks

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

1,9922,0392,015.56 August 2026 — 2,039 subscribers9 August 2026 — 2,036 subscribers12 August 2026 — 2,035 subscribers16 August 2026 — 2,025 subscribers19 August 2026 — 2,023 subscribers22 August 2026 — 2,020 subscribers25 August 2026 — 2,016 subscribers28 August 2026 — 2,015 subscribers31 August 2026 — 2,013 subscribers4 September 2026 — 2,008 subscribers9 September 2026 — 2,001 subscribers13 September 2026 — 1,997 subscribers17 September 2026 — 1,992 subscribers21 September 2026 — 1,992 subscribers6 August 202621 September 2026
14 measurements spanning 46 days, net -47. 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,985–2,046 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
21 Sept 2026, 01:261,992no change
17 Sept 2026, 20:011,992-5
13 Sept 2026, 10:011,997-4
9 Sept 2026, 18:592,001-7
4 Sept 2026, 10:412,008-5
31 Aug 2026, 14:362,013-2
28 Aug 2026, 12:162,015-1
25 Aug 2026, 08:572,016-4
22 Aug 2026, 13:232,020-3
19 Aug 2026, 05:262,023-2
16 Aug 2026, 07:562,025-10
12 Aug 2026, 09:282,035-1
9 Aug 2026, 01:422,036-3
6 Aug 2026, 09:422,039first 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 21 September 2026 — this entry's latest reading, not the date you are reading this.

“Julian Assange” (@Julian_AssangeWikiLeaks), 1,992 subscribers as measured 21 September 2026. Telegram Register, tgregister.com/channel/Julian_AssangeWikiLeaks.

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.