Telegram RegisterThe public register of Telegram
Telegram profile photo for Nex leech

Channel

Nex leech

@nexleech

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

191subscribers

-4 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001760300348
TypeChannel
Username@nexleech
Created10 December 2021 — measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live11 October 2026
Measurements held7
Confirmed unchanged2 times, most recently 11 October 2026
On Telegramt.me/nexleech

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

191196193.57 August 2026 — 195 subscribers8 August 2026 — 195 subscribers15 August 2026 — 196 subscribers27 August 2026 — 195 subscribers3 September 2026 — 194 subscribers12 September 2026 — 193 subscribers30 September 2026 — 191 subscribers7 August 202630 September 2026
7 measurements spanning 54 days, net -4. 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 190–197 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Sept 2026, 07:56191-2
12 Sept 2026, 03:41193-1
3 Sept 2026, 08:36194-1
27 Aug 2026, 20:54195-1
15 Aug 2026, 01:36196+1
8 Aug 2026, 11:46195no change
7 Aug 2026, 08:37195first reading

Engagement

13 posts held, back to 10 December 2021 — 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 13 posts for this entry, the most recent from 26 October 2022. An engagement rate over an empty window would be a number about nothing.

Reaction mix

80 reactions across 11 posts, in 7 distinct kinds. The most used accounts for 37.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍3037.5%
🔥1721.3%
😱1721.3%
❤78.75%
😁67.50%
🤩22.50%
🎉11.25%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 11 of the 13 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 80 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 10 December 2021 to 26 October 2022, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

7 May 2022, 11:45 UTC≈11,800 views20 reactionsread 8 August 2026

All 10 + ❗heruku account suspended. My all bot stop expact railway hosted So all bot down wait for fix.

😱15👍4🎉1

2 May 2022, 03:01 UTC≈11,300 views12 reactionsread 8 August 2026
Forwarded from @OMG_infoPhoto

Photo, posted without a caption

❤6👍6

27 Feb 2022, 09:27 UTC≈11,200 views2 reactionsread 8 August 2026

📌For now Mirror bot Not available. It's Removed Reason: 🚫Mirror bot "drive" Gmail account banded by Google. 🚫 Mirror bot banded by Telegram It will replace new LEECH BOT Soon ™ 🔜🔜🔜🔜

👍2

26 Jan 2022, 02:16 UTC≈10,700 views5 reactionsread 8 August 2026
Forwarded from @OMG_infoPhoto

We wish all our Indian followers a very happy 73rd Indian Republic Day 🇮🇳 Jai Hind 🇮🇳

👍2🔥2😁1

14 Jan 2022, 03:23 UTC≈9,210 views2 reactionsread 8 August 2026
Photo

May this Makar Sankranti takes away all your sadness and lighten your life with warmth, joy, happiness, and love forever!

👍1🔥1

9 Jan 2022, 15:09 UTC≈7,710 views6 reactionsread 8 August 2026

In LEECH bot update limited to 50 GB. Yt play list 40

🔥6

10 Dec 2021, 04:15 UTC≈7,610 views7 reactionsread 8 August 2026

Joined now. 𝗡𝗘𝗫 𝗖𝗟𝗢𝗨𝗗 ☁️ 𝐍𝐄𝐗 𝐂𝐋𝐎𝐔𝐃 ☁️ 𝐘𝐎𝐔 𝐂𝐀𝐍 𝐋𝐄𝐄𝐂𝐇. 𝐀𝐋𝐋 𝐘𝐓𝐃𝐋P 𝐒𝐔𝐏𝐏𝐎𝐑𝐓 𝐋𝐈𝐍𝐊 🚫 NOTE DRM PROTECT VIDEO. VIDEO NOT SUPPORT.

😁3👍2🔥1😱1

10 Dec 2021, 04:11 UTC≈6,510 views12 reactionsread 8 August 2026

The rules for 𝐍𝐄𝐗 𝐂𝐋𝐎𝐔𝐃 ☁️ ☁️ are: Rules: ✅ Before sending link check /list filename Once.. ❌ Porn links Not Allowed. ❌ Don't Share any links to Channels/Groups / Public.. ❌ Don't send Dead Magnets... (Automatically cancelled in 10Min) ❌ Deleting Direct link or magnet link with Command Message is not allowed If anyone don't follow above rules they would be banned instantly. ❌No Porn - Porn is strictly prohibite…

👍6🔥2😁2❤1😱1

Showing the 12 most recent of 13 posts we hold for @nexleech. 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

Republishes

Channels on the register whose posts this channel has forwarded.

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

Names

Channels on the register whose handles appear in this channel's posts.

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

“Nex leech” (@nexleech), 191 subscribers as measured 30 September 2026. Telegram Register, tgregister.com/channel/nexleech.

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.