Telegram RegisterThe public register of Telegram
Telegram profile photo for Devil Mirror X Leech (4GB)

Supergroup

Devil Mirror X Leech (4GB)

@Dleeching

Has discussion group

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

1,819members

-133 since we began measuring on 7 August 2026

104 online right now

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

Register entry

Telegram ID-1002103248649
TypeSupergroup
Username@Dleeching
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded22 September 2026
Last confirmed live30 October 2026
Measurements held24
Confirmed unchanged1 time, most recently 30 October 2026
On Telegramt.me/Dleeching

Topic

Software piracy — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 86% 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,8191,9521,885.57 August 2026 — 1,952 members8 August 2026 — 1,950 members11 August 2026 — 1,943 members14 August 2026 — 1,940 members18 August 2026 — 1,938 members21 August 2026 — 1,932 members24 August 2026 — 1,931 members27 August 2026 — 1,925 members30 August 2026 — 1,920 members1 September 2026 — 1,914 members5 September 2026 — 1,909 members10 September 2026 — 1,895 members13 September 2026 — 1,892 members17 September 2026 — 1,890 members22 September 2026 — 1,890 members26 September 2026 — 1,874 members5 October 2026 — 1,862 members12 October 2026 — 1,851 members15 October 2026 — 1,844 members18 October 2026 — 1,841 members21 October 2026 — 1,834 members24 October 2026 — 1,832 members27 October 2026 — 1,825 members30 October 2026 — 1,819 members7 August 202630 October 2026
24 measurements spanning 84 days, net -133. 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,799–1,972 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 24
Measured (UTC)MembersChange
30 Oct 2026, 07:411,819-6
27 Oct 2026, 16:491,825-7
24 Oct 2026, 13:301,832-2
21 Oct 2026, 17:301,834-7
18 Oct 2026, 03:571,841-3
15 Oct 2026, 13:281,844-7
12 Oct 2026, 05:001,851-11
5 Oct 2026, 05:011,862-12
26 Sept 2026, 05:591,874-16
22 Sept 2026, 02:251,890no change
17 Sept 2026, 17:151,890-2
13 Sept 2026, 20:571,892-3
10 Sept 2026, 05:411,895-14
5 Sept 2026, 07:361,909-5
1 Sept 2026, 21:331,914-6
30 Aug 2026, 04:371,920-5
27 Aug 2026, 13:261,925-6
24 Aug 2026, 14:281,931-1
21 Aug 2026, 01:331,932-6
18 Aug 2026, 00:511,938first 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.

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

“Devil Mirror X Leech (4GB)” (@Dleeching), 1,819 members as measured 30 October 2026. Telegram Register, tgregister.com/channel/Dleeching.

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.