Telegram RegisterThe public register of Telegram
Telegram profile photo for Ezzz Skin

Bot

Ezzz Skin

@ezzzskinbot

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

35,654monthly users

-7,150 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID8096573110
TypeBot
Username@ezzzskinbot
First recorded12 August 2026
Last confirmed live14 November 2026
Measurements held50
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/ezzzskinbot

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

26,33244,66435,4987 August 2026 — 42,804 monthly users8 August 2026 — 43,149 monthly users9 August 2026 — 43,371 monthly users10 August 2026 — 42,050 monthly users12 August 2026 — 42,124 monthly users12 August 2026 — 42,124 monthly users13 August 2026 — 42,580 monthly users14 August 2026 — 43,125 monthly users16 August 2026 — 44,576 monthly users17 August 2026 — 44,664 monthly users18 August 2026 — 44,406 monthly users19 August 2026 — 44,598 monthly users22 August 2026 — 44,564 monthly users23 August 2026 — 44,449 monthly users25 August 2026 — 43,641 monthly users26 August 2026 — 43,133 monthly users27 August 2026 — 42,964 monthly users29 August 2026 — 43,138 monthly users30 August 2026 — 42,937 monthly users1 September 2026 — 41,413 monthly users2 September 2026 — 41,359 monthly users6 September 2026 — 41,059 monthly users10 September 2026 — 39,685 monthly users12 September 2026 — 38,339 monthly users13 September 2026 — 38,786 monthly users15 September 2026 — 37,569 monthly users17 September 2026 — 37,248 monthly users27 September 2026 — 34,718 monthly users4 October 2026 — 27,949 monthly users9 October 2026 — 26,746 monthly users13 October 2026 — 27,495 monthly users14 October 2026 — 27,140 monthly users15 October 2026 — 27,336 monthly users17 October 2026 — 27,291 monthly users18 October 2026 — 27,320 monthly users20 October 2026 — 26,332 monthly users22 October 2026 — 26,452 monthly users23 October 2026 — 26,738 monthly users24 October 2026 — 26,855 monthly users25 October 2026 — 26,974 monthly users28 October 2026 — 28,798 monthly users29 October 2026 — 30,269 monthly users31 October 2026 — 30,825 monthly users1 November 2026 — 31,298 monthly users4 November 2026 — 32,970 monthly users5 November 2026 — 33,971 monthly users6 November 2026 — 34,424 monthly users9 November 2026 — 34,548 monthly users11 November 2026 — 34,652 monthly users14 November 2026 — 35,654 monthly users35,6547 August 202614 November 2026
50 measurements spanning 100 days, net -7,150. 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 23,582–47,414 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 50
Measured (UTC)Monthly usersChange
14 Nov 2026, 22:1835,654+1,002
11 Nov 2026, 22:1734,652+104
9 Nov 2026, 23:3834,548+124
6 Nov 2026, 13:5634,424+453
5 Nov 2026, 16:3933,971+1,001
4 Nov 2026, 15:2932,970+1,672
1 Nov 2026, 13:4631,298+473
31 Oct 2026, 12:5030,825+556
29 Oct 2026, 11:0930,269+1,471
28 Oct 2026, 07:3028,798+1,824
25 Oct 2026, 05:2726,974+119
24 Oct 2026, 05:1926,855+117
23 Oct 2026, 03:2626,738+286
22 Oct 2026, 05:2926,452+120
20 Oct 2026, 21:3826,332-988
18 Oct 2026, 19:1027,320+29
17 Oct 2026, 20:1827,291-45
15 Oct 2026, 23:0127,336+196
14 Oct 2026, 20:1827,140-355
13 Oct 2026, 10:2627,495first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

Mentions

Named by 19 registered channels — 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.

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

“Ezzz Skin” (@ezzzskinbot), 35,654 monthly users as measured 14 November 2026. Telegram Register, tgregister.com/channel/ezzzskinbot.

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.