Telegram RegisterThe public register of Telegram
Telegram profile photo for ill's ~ls

Channel

ill's ~ls

@illgate

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

149subscribers

-99 since we began measuring on 12 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003430755413
TypeChannel
Username@illgate
Created3 December 2025 — measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live10 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 10 October 2026
On Telegramt.me/illgate

Topic

Marketing & affiliate — 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 24 September 2026 and assigned it the closest of 31 fixed categories, at 65% 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

149248198.512 August 2026 — 248 subscribers13 August 2026 — 248 subscribers20 August 2026 — 233 subscribers28 August 2026 — 223 subscribers4 September 2026 — 209 subscribers12 September 2026 — 180 subscribers1 October 2026 — 153 subscribers10 October 2026 — 149 subscribers12 August 202610 October 2026
8 measurements spanning 60 days, net -99. 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 134–263 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Oct 2026, 23:17149-4
1 Oct 2026, 00:37153-27
12 Sept 2026, 14:00180-29
4 Sept 2026, 10:22209-14
28 Aug 2026, 05:04223-10
20 Aug 2026, 19:16233-15
13 Aug 2026, 01:16248no change
12 Aug 2026, 06:01248first reading

Engagement

16 posts held, back to 3 December 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 16 posts for this entry, the most recent from 18 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

18 Jul 2026, 19:50 UTC907 viewsread 12 August 2026

IG(.)com VM Api based requirements = proxies CPM: 10k+ Price: $676 MM @cupid / @cold 🛡

17 Jul 2026, 19:27 UTC≈2,340 viewsread 12 August 2026

Crypto(.)com VM Api based requirements = proxies CPM: 5k+ Price: $500 MM @cupid / @cold 🛡

24 Jun 2026, 13:45 UTC≈1,130 viewsread 12 August 2026

oobit(.)com VM Api based requirements = proxies CPM: 15k+ Price: $700 MM @cupid / @cold 🛡

24 Jun 2026, 13:40 UTC≈1,240 viewsread 12 August 2026

Coinglass(.)com VM Api based requirements = proxies CPM: 40k+ Price: $800 MM @cupid / @cold 🛡

24 Jun 2026, 13:39 UTC≈1,160 viewsread 12 August 2026

Capital(.)com VM Api based, anysolver and/or in-house solver requirements = proxies CPM: 10k+ Price: $900 MM @cupid / @cold 🛡

18 Jun 2026, 21:58 UTC≈1,370 viewsread 12 August 2026

hellostake(.)com VM Api based requirements = proxies CPM: 30k+ Price: $500 MM @cupid / @cold 🛡

18 Jun 2026, 14:29 UTC≈3,190 viewsread 12 August 2026

Gate(.)io VM Api based requirements = proxies CPM: 10k+ Price: $800 MM @cupid / @cold 🛡

16 Jun 2026, 10:15 UTC≈4,300 viewsread 12 August 2026

Investing(.)com VM Api based requirements = proxies CPM: 10k+ Price: $1,000 MM @cupid / @cold 🛡

16 Jun 2026, 10:12 UTC≈2,320 viewsread 12 August 2026

InvestEngine VM Api based requirements = proxies CPM: 15k+ Price: $1,000 MM @cupid / @cold 🛡

16 Jun 2026, 10:11 UTC≈2,550 viewsread 12 August 2026

Finelo VM Api based requirements = proxies CPM: 40k+ Price: $1,200 MM @cupid / @cold 🛡

16 Jun 2026, 10:10 UTC≈1,560 viewsread 12 August 2026

CMC(CoinMarketCap) VM Api based, uses in-house solver requirements = proxies CPM: 30k+ Price: $500 MM @cupid / @cold 🛡

16 Jun 2026, 10:09 UTC≈2,540 viewsread 12 August 2026

BTCC VM Api based requirements = proxies CPM: 25k+ Price: $1,000 MM @cupid / @cold 🛡

Showing the 12 most recent of 16 posts we hold for @illgate. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

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.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under 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 10 October 2026 — this entry's latest reading, not the date you are reading this.

“ill's ~ls” (@illgate), 149 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/illgate.

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.