Telegram RegisterThe public register of Telegram
Telegram profile photo for etan smooth

Channel

etan smooth

@etansmooth

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

96subscribers

+2 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-1002156535948
TypeChannel
Username@etansmooth
CreatedBetween 1 May 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live3 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 3 October 2026
On Telegramt.me/etansmooth

Topic

Religion — 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 27 September 2026 and assigned it the closest of 31 fixed categories, at 62% 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

939694.57 August 2026 — 94 subscribers9 August 2026 — 94 subscribers20 August 2026 — 95 subscribers3 September 2026 — 93 subscribers11 September 2026 — 95 subscribers3 October 2026 — 96 subscribers7 August 20263 October 2026
6 measurements spanning 57 days, net +2. 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 93–96 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Oct 2026, 23:3796+1
11 Sept 2026, 09:1595+2
3 Sept 2026, 01:3593-2
20 Aug 2026, 23:4695+1
9 Aug 2026, 12:4794no change
7 Aug 2026, 14:4794first reading

Engagement

16 posts held, back to 28 July 2026 — 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 9 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
3m 05s
Average length
3m 05s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

37 reactions across 15 posts, in 11 distinct kinds. The most used accounts for 27.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤‍🔥1027.0%
❤718.9%
custom 5384246963057235648410.8%
🥰410.8%
custom 538199433860982609638.11%
custom 538418863310638619638.11%
😭25.41%
custom 538212658924280695712.70%
👍12.70%
🔥12.70%
😈12.70%

Custom emoji. 4 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

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 15 of the 16 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 37 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 28 July 2026 to 9 August 2026, 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

9 Aug 2026, 11:11 UTC8 views1 reactionsread 9 August 2026

🇮🇳настоящий буддист не должен сопротивляться если его пырнуть, ведь последствия его кармы привели к такому исходу🇮🇳

🥰1

9 Aug 2026, 03:55 UTC16 views1 reactionsread 9 August 2026
Photo

сука да этих паджитов не переплюнуть в обсирании их же религии

custom 53842469630572356481

9 Aug 2026, 03:52 UTC15 views1 reactionsread 9 August 2026
Photo

я уверена я не первая этот сюжет придумала, но я думаю сиддхартха гаутама был рожден именно так

🔥1

6 Aug 2026, 00:31 UTC43 views1 reactionsread 9 August 2026
Photo

это как противостояние пьюдипая и индийских сериалов 10 лет назад

custom 53841886331063861961

2 Aug 2026, 18:08 UTC61 views2 reactionsread 9 August 2026
Photo

кто-нибудь помнит этого добряка

😭2

2 Aug 2026, 14:00 UTC49 views4 reactionsread 9 August 2026
Photo

оказалось существовали в ограниченном количестве айподы, выпущенные в честь перезапуска 2х2 в 2007, и мне выпала честь урвать с авито один из них и с ними задача разгадать значение цифр после 11-34

custom 53819943386098260963custom 53842469630572356481

2 Aug 2026, 07:03 UTC44 views2 reactionsread 9 August 2026
Photo

он мне слишком понравился

custom 53841886331063861962

2 Aug 2026, 02:51 UTC47 views3 reactionsread 9 August 2026
Photo

первый мультик на моей памяти, где озвучку заедает и она повторяет одну и ту же строчку (примерно с 1 часа 19 минут) и надо вручную добавлять сабы к оригиналу чтоб нормально досмотреть 2х2 бы точно это не показал из-за 134 ук рф

❤2custom 53821265892428069571

2 Aug 2026, 01:05 UTC47 views1 reactionsread 9 August 2026
Photo

худший кошмар прокуратуры зуевского района кировской области

😈1

1 Aug 2026, 04:25 UTC57 views3 reactionsread 9 August 2026

что-то люди перестали романтизировать роскомпозор в виде анимешной телки в костюме с молоточком

❤‍🔥3

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

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

“etan smooth” (@etansmooth), 96 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/etansmooth.

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.