Telegram RegisterThe public register of Telegram
Telegram profile photo for No Mercy - VIP's

Channel

No Mercy - VIP's

@nomercyvip

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

4,393subscribers

-295 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002626233185
TypeChannel
Username@nomercyvip
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded3 September 2026
Last confirmed live27 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 27 September 2026
On Telegramt.me/nomercyvip

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

4,3934,6884,540.57 August 2026 — 4,688 subscribers8 August 2026 — 4,684 subscribers11 August 2026 — 4,655 subscribers14 August 2026 — 4,639 subscribers17 August 2026 — 4,620 subscribers20 August 2026 — 4,601 subscribers24 August 2026 — 4,577 subscribers27 August 2026 — 4,569 subscribers30 August 2026 — 4,567 subscribers2 September 2026 — 4,538 subscribers3 September 2026 — 4,538 subscribers7 September 2026 — 4,501 subscribers11 September 2026 — 4,479 subscribers15 September 2026 — 4,456 subscribers27 September 2026 — 4,393 subscribers7 August 202627 September 2026
15 measurements spanning 51 days, net -295. 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 4,349–4,732 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Sept 2026, 23:004,393-63
15 Sept 2026, 18:584,456-23
11 Sept 2026, 23:214,479-22
7 Sept 2026, 14:574,501-37
3 Sept 2026, 12:114,538no change
2 Sept 2026, 21:454,538-29
30 Aug 2026, 09:584,567-2
27 Aug 2026, 03:244,569-8
24 Aug 2026, 10:454,577-24
20 Aug 2026, 10:434,601-19
17 Aug 2026, 18:554,620-19
14 Aug 2026, 10:374,639-16
11 Aug 2026, 07:214,655-29
8 Aug 2026, 04:134,684-4
7 Aug 2026, 15:444,688first 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 27 September 2026 — this entry's latest reading, not the date you are reading this.

“No Mercy - VIP's” (@nomercyvip), 4,393 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/nomercyvip.

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.