Telegram RegisterThe public register of Telegram
Telegram profile photo for ᛝ‍‍ лиϐdie

Channel

ᛝ‍‍ лиϐdie

@enansn

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

32subscribers

+2 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1003688307852
TypeChannel
Username@enansn
Created2 May 2026measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live30 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/enansn

Growth

3036339 August 2026 — 30 subscribers11 August 2026 — 30 subscribers17 August 2026 — 36 subscribers24 August 2026 — 35 subscribers30 August 2026 — 32 subscribers329 August 202630 August 2026
5 measurements spanning 21 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 29–37 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 23:2632-3
24 Aug 2026, 23:1935-1
17 Aug 2026, 11:5736+6
11 Aug 2026, 04:0030no change
9 Aug 2026, 18:0030first reading

Engagement

8 posts held, back to 2 May 2026the 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 8 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

321 reactions across 4 posts, in 22 distinct kinds. The most used accounts for 9.35% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5283027778030046149309.35%
custom 5454246898393180781299.03%
custom 5325956212376763979247.48%
custom 5283206276870868769226.85%
custom 5444872956176006859226.85%
custom 5359578878522196708195.92%
custom 5282965165996803805185.61%
custom 5233343617824743359175.30%
custom 5265236279733279513164.98%
custom 5415761521814832446154.67%
custom 5467756297115952480154.67%
custom 5285234257348826665123.74%
custom 5282952783606090654113.43%
custom 5325588893888707784113.43%
custom 528295054163315991492.80%
custom 534610172641388606792.80%
custom 544499287595787771782.49%
custom 522211933497697152472.18%
custom 528309593486606810272.18%
custom 532783980464417167472.18%
2 further kinds134.05%

Custom emoji. Every row above is a 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 4 of the 8 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 321 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 8 most recent posts we hold, published 2 May 2026 to 5 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

5 Aug 2026, 09:12 UTC143 views53 reactionsread 11 August 2026
Photo

⠀ ♡゙лиϐ няɯкɑ 🤩 めshᧉher 🎀 @ anσn 🥹 more inf

custom 546775629711595248012custom 535957887852219670811custom 544487295617600685911custom 52830959348660681024custom 52852342573488266654custom 53461017264138860674custom 54449928759578777174custom 52493732518172109413

5 Aug 2026, 08:53 UTC118 views45 reactionsread 11 August 2026
File

🥰🥰 sociαl 🥹🥹nᧉtwσrks :: 🥹sweet telegram channel shitpost 🥹channel tiktok 🥰 discord livangel67 ➕work in :: deadblonde mtrl blush daimin piar chat

custom 544487295617600685911custom 52852342573488266658custom 53595788785221967088custom 53461017264138860675custom 54449928759578777174custom 52493732518172109413custom 52830959348660681023custom 54677562971159524803

10 Jul 2026, 08:17 UTC400 views87 reactionsread 11 August 2026
File

File, posted without a caption

custom 523334361782474335917custom 545424689839318078117custom 526523627973327951316custom 52829505416331599149custom 52221193349769715247custom 52829651659968038057custom 53278398046441716747custom 54023831539543252557

7 May 2026, 17:51 UTC981 views136 reactionsread 11 August 2026
Photo

ㅤ💕𝗈𝗎𝗋 𝂅꒰ ྀི 𝗈p͡𝗂𝗇𝗂𝑜𝗇 🥹🥹 𝂅𓎟͡ 𝗈𝗇 𝗅i𝗏 🥹🥹 𝖺𝖻𝗈𝗎𝗍 💕𝗇f𝗈

custom 528302777803004614930custom 532595621237676397924custom 528320627687086876922custom 541576152181483244615custom 545424689839318078112custom 528295278360609065411custom 528296516599680380511custom 532558889388870778411

Showing the 8 most recent of 8 posts we hold for @enansn. 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.

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

“ᛝ‍‍ лиϐdie” (@enansn), 32 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/enansn.

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.