Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝘓𝘐𝘍𝘌 #𝒜𝒟 //. .💧

Channel

𝘓𝘐𝘍𝘌 #𝒜𝒟 //. .💧

@Liife_AD

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

30subscribers

-3 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003828065691
TypeChannel
Username@Liife_AD
CreatedBetween 1 February 2026 and 28 April 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live15 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/Liife_AD

Growth

303331.58 August 2026 — 33 subscribers11 August 2026 — 33 subscribers16 August 2026 — 32 subscribers24 August 2026 — 31 subscribers15 September 2026 — 30 subscribers8 August 202615 September 2026
5 measurements spanning 37 days, net -3. 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 30–33 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 03:3930-1
24 Aug 2026, 05:1731-1
16 Aug 2026, 19:3432-1
11 Aug 2026, 01:4633no change
8 Aug 2026, 23:0133first reading

Engagement

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

Reaction mix

77 reactions across 9 posts, in 12 distinct kinds. The most used accounts for 18.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54156595163415544121418.2%
custom 53165694754520064591316.9%
custom 53145592203040826561215.6%
custom 53146908481668009851114.3%
custom 534802621106490474179.09%
custom 531660718526486545067.79%
67.79%
custom 531474438493414598345.19%
custom 531476274591933836911.30%
custom 531896549167755923311.30%
🔥11.30%
🥰11.30%

Custom emoji. 9 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 9 of the 20 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 77 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 28 April 2026 to 10 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

10 Aug 2026, 17:47 UTC7 views5 reactionsread 11 August 2026

#𝑴𝒖𝒛𝒂𝒏_𝒜𝒟 #𝘐𝘮𝘱𝘰𝘳𝘵𝘢𝘯𝘵𝒜𝒟 Всем доброго времени суток, на связи Мудзан. Недолго думая мы с Аказой решили что проект • °. 𝒜𝒒𝓊𝒶𝒻𝓇𝑜𝓇𝒶 𝒟𝓇𝑒𝒶𝓉𝓈 ◟﷟!! 💧 официально объявляется открытым! Мы долго думали и уже решили что проект продолжит свою работу. Мы над этим думали и думали и потом уже выбрали такое решение. Спасибо всем за ваши терпения!

3🔥1🥰1

28 Jul 2026, 19:31 UTC25 views3 reactionsread 11 August 2026

я надумываю вернуть этот флуд к жизни после моря..

3

1 May 2026, 11:32 UTC382 views8 reactionsread 11 August 2026

#𝐴𝑘𝑎𝑧𝑎_𝒜𝒟 РЕБЯТ, не грустите пожалуйста.😭😭 я и так собираюсь открывать новый флуд позже, поэтому я не навсегда прощаюсь с вами. #𝐾𝑜𝑘𝑢𝑠ℎ𝑖𝑏𝑜_𝒜𝒟 Да как тут не грустить, такой красивый проект и тут бац.

custom 54156595163415544128

1 May 2026, 07:06 UTCviews —

Channel name was changed to «ЗАКРЫТ // 𝘓𝘐𝘍𝘌 #𝒜𝒟 //. .💧»

1 May 2026, 07:06 UTC550 views14 reactionsread 11 August 2026

#𝐴𝑘𝑎𝑧𝑎_𝒜𝒟 флуд закрыт, со всеми разрыв. у меня больше нет сил продвигать этот флуд, я устал от игнора в чате и неактива. мне дискомфортно в этом флуде. простите пожалуйста.

custom 53165694754520064596custom 53146908481668009854custom 53147443849341459834

30 Apr 2026, 11:20 UTC474 views13 reactionsread 11 August 2026

#𝐴𝑘𝑎𝑧𝑎_𝒜𝒟 в субботу чистка, норма набрана у 2х человек. в неактиве 11 человек...😝 на интерактивы игнор, на просьбы админов поднимать актив/делать видео — тишина. я уже хс что делать, снова пропадает мотивация. #𝘚𝘩𝘱𝒜𝒟

custom 53480262110649047416custom 54156595163415544126custom 53145592203040826561

29 Apr 2026, 18:27 UTC421 views3 reactionsread 11 August 2026

È 𝘣𝘦𝘭𝘭𝘰 𝘷𝘦𝘥𝘦𝘳𝘦 𝘱𝘦𝘳𝘴𝘰𝘯𝘦 𝘤𝘰𝘴ì 𝘱𝘪𝘢𝘤𝘦𝘷𝘰𝘭𝘪🤩 𝘪𝘯 𝘲𝘶𝘦𝘴𝘵𝘰 𝘢𝘯𝘨𝘰𝘭𝘰 𝘥𝘦𝘭 𝘮𝘰𝘯𝘥𝘰 𝘤𝘩𝘦 𝘤𝘪 𝘴𝘰𝘯𝘰 𝘱𝘪𝘢𝘤𝘪𝘶𝘵𝘦...💿 𝘛𝘪 𝘢𝘱𝘱𝘳𝘦𝘻𝘻𝘪𝘢𝘮𝘰 𝘮𝘰𝘭𝘵𝘰.🕹 😎ловим облачка. . . . ➖🤩собираем мыльные пузыри. . . ➖➖🤩хрумкаем стиральными капсулками. . ⭐️⭐️⭐️⭐️⭐️⭐️⭐️⭐️ «Тихий ᴄʙᴇᴛ нᴀᴨᴏᴧниᴧ нᴀɯ уюᴛный ʍиᴩ — дᴏбᴩᴏ ᴨᴏжᴀᴧᴏʙᴀᴛь, 𐔌 𝐸𝑐ℎ𝑜 𝑂𝑓 𝑆𝑢𝑛 !! Пуᴄᴛь ɜдᴇᴄь ᴛᴇбᴇ будᴇᴛ ᴄᴨᴏᴋᴏйнᴏ и ᴄʙᴇᴛᴧᴏ.» ⭐️⭐️⭐️⭐️⭐️⭐️⭐️⭐️ #𝘕𝘦𝘸𝘜𝘯𝘪𝘰𝘯𝒜𝒟

custom 53146908481668009853

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

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.

Mentions

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

“𝘓𝘐𝘍𝘌 #𝒜𝒟 //. .💧” (@Liife_AD), 30 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/Liife_AD.

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.