Telegram RegisterThe public register of Telegram

Channel

LIFE | 𐍄𐍪𐌹𐍃𐍄𐌴D 𐍄𐍪𐌹𐍰𐌹GH𐍄

@owldlekf

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

5subscribers

+0 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1002217080719
TypeChannel
Username@owldlekf
DescriptionРады приветствовать вас в нашем лайф канала! °>. Наш инфо - https://t.me/info_8174
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live13 August 2026
Measurements held2
On Telegramt.me/owldlekf

Growth

512 Aug 2026, 10:30 — 5 subscribers13 Aug 2026, 01:47 — 5 subscribers12 Aug 2026, 10:3013 Aug 2026, 01:47
2 measurements taken within a single day. 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–6 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 01:475no change
12 Aug 2026, 10:305first reading

Engagement

17 posts held, back to 1 March 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 17 posts for this entry, the most recent from 1 June 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
45
Videos
2
Links
24

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
24s
Average length
12s

Measured directly from 2 videos 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

8 reactions across 7 posts, in 4 distinct kinds. The most used accounts for 62.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
562.5%
🐳112.5%
😨112.5%
😱112.5%

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

Measured over the 17 most recent posts we hold, published 1 March 2025 to 1 June 2025, 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

1 Jun 2025, 19:58 UTC25 viewsread 13 August 2026

Калл этот флуд закрывается ибо надежды на него кончились, он свое отжил. Если есть желающие можете вступить в новый проект заранее выбрав роль, откроется в скором времени. https://t.me/flsummursflyd

12 Apr 2025, 23:28 UTC42 views1 reactionsread 13 August 2026

На данный момент известно что возраст Чёрного Лебедя 59, а Ахерон 51.

😱1

12 Apr 2025, 23:26 UTC33 views1 reactionsread 13 August 2026
Photo

И так, сегодня во флуде 𐍄𐍪𐌹𐍃𐍄𐌴D 𐍄𐍪𐌹𐍰𐌹GH𐍄 были замеченны незаконные действия о том как двое представителей администрации флуда обсуждали похещение насилие использования детского труда, и строили планы по действими над детьми 9-11 лет, так называемый владелец "Чёрный Лебедь " рассказывал как забирал детей утверждая что он знакомый их родителей, что сейчас с этими детьми точно не известно, но судя по всему их держат

😨1

10 Apr 2025, 05:05 UTC46 viewsread 13 August 2026

ʙʟᴀᴄᴋ ꜱᴡᴀɴ 👾| Что-то время летит слишком быстро,времени на лайф мало. --+++--------+---+++--------+----+++-- С прошедшей чистки у нас омаободило множество ролей, В активном поиске новых участников,всех желающих просим писать в нашего бота. С уважением Лебедь и Ахерон.

31 Mar 2025, 12:40 UTC23 views1 reactionsread 13 August 2026
Photo

°. New Union. .° С этого дня проект:: 𐍄𐍪𐌹𐍃𐍄𐌴D 𐍄𐍪𐌹𐍰𐌹GH𐍄 И 𝚃𝚑𝚎 𝚍𝚎𝚊𝚍 𝚑𝚎𝚊𝚛𝚝 Заключили договор о союзе! ---------------------° °----------------------- Рады приветствовать нашего нового союзника в нашем Флуде. Рады видеть что история нашего проекта только растёт и движется в нужном направлении, дабы передать всё в его историю. Также надеемся на долгий срок действия союза, также что всё правила

1

21 Mar 2025, 22:00 UTC33 views2 reactionsread 13 August 2026

Чтож!) Пришло 22 марта, а это значит что наступил день рождения нашего прекрасного Чёрного Лебедя. Этот человек сделал многое для проэкта и продолжает делать с каждым разом добиваясь больших успехов. Пожелаем лебедю достижений в его целях, что-бы в жизни все было ровно без ям в дороге и камней.

1🐳1

15 Mar 2025, 13:12 UTC34 viewsread 13 August 2026
Photo

°. New Union. .° С этого дня проект:: 𐍄𐍪𐌹𐍃𐍄𐌴D 𐍄𐍪𐌹𐍰𐌹GH𐍄 И 𝐯𝐞𝐫𝐟𝐚𝐮𝐥𝐞𝐧 Заключили договор о союзе! ---------------------° °----------------------- Рады приветствовать нашего нового союзника в нашем Флуде. Рады видеть что история нашего проекта только растёт и движется в нужном направлении, дабы передать всё в его историю. Также надеемся на долгий срок действия союза, также что всё правила буду

14 Mar 2025, 23:12 UTC25 views0 reactionsread 13 August 2026
Photo

ʙʟᴀᴄᴋ ꜱᴡᴀɴ 👾| Что ж. 15 Марта, а значит что Сегодня день рождения великого человека — Нашего совладельца. Хотелось бы пожелать побольше умиротворения, свечек и конечно же как бы ни было банально говорить:: Здоровья и благополучия. Лично от себя также пару слов. Через месяц и с десяток дней нашему общению стукнет ровно год и это замечательная цифра дабы попытаться её запомнить дабы окунуться и вспомнить всё ошибки

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

Citation-graph rank

Citation-graph rank — 898,897 of 1,340,412entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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

“LIFE | 𐍄𐍪𐌹𐍃𐍄𐌴D 𐍄𐍪𐌹𐍰𐌹GH𐍄” (@owldlekf), 5 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/owldlekf.

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.