Channel
@olight_life
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
29subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003860321942 |
|---|---|
| Type | Channel |
| Username | @olight_life |
| Description | 𝐈𝖭𝖥𝖮 ⸺ olight_info.t.me |
| Created | Between 1 February 2026 and 30 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/olight_life |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 11:30 | 29 | no change |
| 11 Aug 2026, 11:18 | 29 | first reading |
18 posts held, back to 30 May 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 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 18 posts for this entry, the most recent from 5 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 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.
Measured directly from 7 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.
2 reactions across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5456122776899314917 | 2 | 100.0% |
Custom emoji. One 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 count beside it isTelegram’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 1 of the 18 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 2reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 30 May 2026 to 5 June 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.
ᅠᛝ ˖ ⃞🐈⬛ : 𝖺𝗅𝗁𝖺𝗂𝗍𝗁𝖺𝗆𝄄 💋 ᅠ ᅠ ᅠ : навия покидает пост следящего по причине вылета из флуда, а вместе с тем лайф канал закрывается, ибо у меня самого сил и времени тянуть это дело нет😭 со всеми союзниками разрыв, спасибо, что были с нами!
custom 54561227768993149172
Sticker, posted without a caption
Sticker, posted without a caption
ᅠᛝ ˖ ⃞🔤𝖤𝖯𝓞𝖲𝖳 𝖳𝖨𝖬𝖤🥹 🤩🤩🤩 .navia ⏜⌒ ⸼ 𝗦𝗧𝗔𝗥𝗧 & 𝗘𝗡𝗗
: : — Эᴦρᥲᥴᥴᥱ᧘ь - на 100 подписчиков в лайфе хочу сделать интерактив, так что активно ищу союзы🌟 Условия союзов Те, кто сейчас заключают : : ° Эграссель, писать — [ @xolli24_993 ] ° Сайрисса, писать — [ @Syrissa_union_bot ] [ Подробнее о союзах - 🤍🤍🤍 ] #репостAL
🤍🍭🥹 🔹𝕾𝐒𝐎𝐂➖𝐀𝐓𝕴𝐎𝕹 🎁 ˚ ➖𝖊m𝖆 :: к𝖆к𝖆я 𝕹ы 𝕽года/𝕱рукт ?.?. # 🔹𝖊ст𝖆 🛜 𝕯ля с𝖔юз𝖔в 🎁 7/10..? 🤍??… 𝕯ля 𝖄ч𝖆стник𝖔в :: 2/5..? 🥹 🐈⬛➖сл𝖔вия 🍭 #🔹𝖔юз𝖔в 🍷 🤍🤍ᴨᴏдᴨиᴄᴋᴀ нᴀ ᴧᴀйɸ, ᴩᴇᴨᴏᴄᴛ ᴨᴄ ᴋ ᴄᴇбᴇ ʙ ᴋᴀнᴀᴧ, ᴄᴋинуᴛь ᴀʙᴀᴛᴀᴩᴋу, нᴀɜʙᴀниᴇ ʙ ʍᴏнᴏ ʙ ᴋᴏʍʍᴇнᴛᴀᴩии 💋 🤍 🪦 💉 @ 😀ч𝖆стник𝖔в 🎁 ⃟ 🪭пᴏдᴨиᴄᴋᴀ нᴀ ᴧᴀйɸ, ᴄᴋинуᴛь ʙ ᴋᴏʍʍᴇнᴛᴀᴩии ɸᴏᴛᴏ ᴄʙᴏᴇй ᴩᴏᴧи 🤍#репост𝕹𝐘 & #интерактив𝕹𝐘
✨✨✨✨N𝐄𝐖 𝐄𝑹𝐀✨🔍 ┈───────────── N𝐄𝐖.......? Во время нью эры мы: 🎀Не заключаем союзы. 🎀Не проводим Рп-таймы. 🎀Не следим за союзниками. 🎀 Не принимаем участие в различных бинго/ассоциациях. 🌧️26.🥹 — ....?🌧️
┌───┐────────────────── 🐰 ׄ . ⋆۫ . ๑ 🕷𝒆𝒘 𝒗𝒊𝒅𝒆𝒐 ˚ 𓈒 𝅄۫ ۪𝄄𝄄 └───┘────────────────── 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 сделал/а -> Мицури 🤩🤩🤩🤩 -> тренд/своя 🕷 — лепесток сакуры, упавший на лотос, но не сломавший его. そして、何千もの目に囲まれた群衆の中で、私はまだあなたの 目を探し続けるでしょう #video_𝑷𝑩𝑯
💭🌟🌟🌟🌟🌟 🌟🌟🌟🌟🌟💭 ✨✨✨✨✨✨✨✨ Уже есть в тик токе, смотреть Тут ⤾ 🎀Creator: 🎀Кокоми 🎀 🎀 Наш тик ток; @moonchartflood 🌧️🌧️🦋🦋🌧️🦋🦋🦋🌧️ #NewVideo_Ꮇᴄf
🔤 🌟🤩Небольшое новвоведение в условиях союза (пункт 1.5): теперь, в одном посте с репостами будет только по одному видео от каждого союза. Неограниченное кол-во видео исключительно для семейных союзов. (Которые теперь доступны для заключения!!) 🔹Если данное условие вам не подходит, прошу сообщить о разрыве в бота: @no9unions01_bot Если вы хотите заключить семейный союз, просьба также обращаться в бота. ㅤ➿➿➿➿➿➿➿➿➿➿➿ 🐩…
🟣🟣🟣🟣❗️ ㅤ ㅤ ㅤ ㅤ ㅤ🟣🟣🟣 ・┆･ﾟ ･ﾟ·:｡ ･ﾟﾟ･ʚ❀୨🌸୧❀ɞ ･ﾟ ･ﾟ·:｡ ･ﾟﾟ･┆・ Здравствуйте, дорогие участники и следящие. У нас серьёзные перемены в проекте!🦋 🤍Что изменилось? Роль владельца: Кастория ➡ Яоши Название проекта: ☽𝑴𝒐𝒐𝒏 𝑬𝒎𝒑𝒊𝒓𝒆☾︎︎ ➡ ˚₊‧꒰ა ❀ ᏗᏰᎧᎴᏋ Ꭷᖴ ᎥᎷᎷᎧᏒ𐐆ᏗᏝ ᏰᏝᎧᏕᏕᎧᎷᎥᏁᎶ ❀ ໒꒱ ‧₊˚ (Обитель Бессмертного Цветения, текст моно) Ссылки: Лайф: @life_Moon_Empire ➡ @AIB_life Инфо: @info_Moon_Empire ➡ @AIB_inf0 Боты: Заявки на вступле…
、⭐️ ୨ᰍ る 🌟𝐄𝐖 𝐕𝐈𝐃𝐄𝐎 . 🤩 ⟢ ｡ ────────────────────────── 𝐓𝐡𝐞 𝐞𝐝𝐢𝐭𝐨𝐫: 𝐃.𝐑𝐀𝐓𝐈𝐎 ⭐⭐⭐⭐ ꒰ づ。 🤩 ┊ °🤩 ૮꒰ྀི ៸៸ ꒱১ 🎁 ꕀ ౿ 🕯🕯🕯🕯🕯🕯🕯🕯🕯🕯🕯🕯🕯🕯 #𝐕𝐢𝐝𝐞𝐨_𝐂𝐃 〢 #𝐑𝐞𝐩𝐨𝐬𝐭_𝐂𝐃
Showing the 12 most recent of 18 posts we hold for @olight_life. 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 — 969,639 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@olight_life named 9 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“𝐋𝖨𝖥𝖤 ⟢ ꒱꒱ 𝐎𝖱𝖠𝖢𝖫𝖤 𝐋𝖨𝖦𝖧𝖳 . .” (@olight_life), 29 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/olight_life.
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.