Channel
@promiseLFE
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
216subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002178419157 |
|---|---|
| Type | Channel |
| Username | @promiseLFE |
| Description | 𝒮𝗁𝖾'𝗌 𝐂𝐑𝐀𝐙𝐘, 𝖻𝗎𝗍 𝖘𝖍𝖊’𝖘 𝐌𝐈𝐍𝐄 @versara_life ❣︎ 𝒪𝐰𝐧𝐞𝐫 - @mxxwde ℐ𝐧𝐟𝐨 𝒸𝐡𝐚𝐧𝐧𝐞𝐥 - @promiseINF 𝒟𝐞𝐬𝐢𝐠𝐧 𝒸𝐫𝐞𝐚𝐭𝐨𝐫 - @mxxwde |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/promiseLFE |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 17:30 | 216 | no change |
| 8 Aug 2026, 17:17 | 216 | first reading |
20 posts held, back to 7 August 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.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 8 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 20 (7 August 2026 – 8 August 2026) |
| Views total | 730 |
| Reactions total | 58 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 17:30 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
58 reactions across 8 posts, in 8 distinct kinds. The most used accounts for 17.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5330111107904349639 | 10 | 17.2% | |
| custom 5379902758256158452 | 9 | 15.5% | |
| custom 5328122057009966183 | 8 | 13.8% | |
| custom 5328164121919658547 | 8 | 13.8% | |
| custom 5330333754714003531 | 7 | 12.1% | |
| custom 5330405377588633640 | 6 | 10.3% | |
| custom 5328221210624957742 | 5 | 8.62% | |
| custom 5330353391304480766 | 5 | 8.62% |
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 areTelegram’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 8 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 58reactions 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 7 August 2026 to 8 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.
〞𝒪бещание – это нить между сердцами. 我保證永遠和你在一起。我們的心是相連的。#cleaningMISE ┆︎ ┈︎ 信仰'их обещание больше не имеет смысла . . . ┆Кокоми, Мика, Аято, Лини, Панталоне, Фурина › › 信仰'готовы дать особенное обещание Альбедо >> любая роль ︎┈︎ 〞𝖨𝐧𝐟o cha𝐧𝐧𝖾𝗅 – 信仰'promise 〞𝖡o𝐭 – 信仰'promise
Sticker, posted without a caption
〞𝒪бещание — это нить между сердцами. 我保證永遠和你在一起。我們的心是相連的。#videoMISE┆︎ ┈︎ 𝖢𝐫𝐞𝐚𝐭𝐨𝐫 › › 𝖢𝗈𝗅𝗎𝗆𝖻𝗂𝗇𝖺 𝖫𝐢𝐧𝐤 › › 信仰'promise
custom 53281641219196585472custom 53282212106249577422custom 53799027582561584522custom 53301111079043496391custom 53303533913044807661custom 53304053775886336401
Sticker, posted without a caption
〞𝒪бещание – это нить между сердцами. 我保證永遠和你在一起。我們的心是相連的。#unionMISE ┆︎ ┈︎ 我相信你。Сегодня мы скрепляем наш союз обещанием быть рядом в любой ситуации, делить радость и поддерживать в трудную минуту. Пусть наши слова станут прочной основой, а взаимное доверие – тем мостом, который будет соединять нас, несмотря на любые преграды. ˚˚.↲⊹݃𝖶⍺ִ𝐤ᧉẜ࡙ꭎֺlִ 𐨌⃟ʾᵐ░҉░csִֺᧉrყֺ·﹆ …
custom 53281220570099661831custom 53281641219196585471custom 53282212106249577421custom 53301111079043496391custom 53303337547140035311custom 53303533913044807661custom 53799027582561584521
〞𝒪бещание – это нить между сердцами. 我保證永遠和你在一起。我們的心是相連的。#unionMISE ┆︎ ┈︎ 我相信你。Сегодня мы скрепляем наш союз обещанием быть рядом в любой ситуации, делить радость и поддерживать в трудную минуту. Пусть наши слова станут прочной основой, а взаимное доверие – тем мостом, который будет соединять нас, несмотря на любые преграды. ㅤ─۫۫🎴 ࣪⃞亡ɦ𝗂ᥒ𝖾ⲋ𝖾 丂𝗎ᥒ. I𝐧𝐟o l𝐢𝐟e
custom 53281220570099661831custom 53281641219196585471custom 53301111079043496391custom 53303337547140035311custom 53303533913044807661custom 53799027582561584521
Sticker, posted without a caption
〞𝖪𝐢𝐧𝐢𝐜𝗁 › › #gapMISE┆︎ 信仰'Когда обещание нарушено, остаётся не только разочарование, но и холод – будто что то важное ушло безвозвратно. 𝐏азрыв 你對我來說很重要。 ┈︎ 〞𝐄.ۨ𝐕ۧ𝐎ۜ𝐈𝐑۪𝐄 закрытие. 𝑳𝒆𝒂𝒇 𝑳𝒆𝒈𝒂𝒄𝒚 с их стороны.
custom 53303337547140035311
Sticker, posted without a caption
〞𝖪𝐢𝐧𝐢𝐜𝗁 › › #shitpostMISE ┆︎ 信仰'Привет, я устал. В коммах скину результаты отдельно для тех, у кого не обновлен тг. А еще я случайно взял на одного человека больше🥺 你對我來說很重要。 ┈︎ Все результаты носят исключительно развлекательный характер и не несут в себе никакого негатива. Информация полностью взята из интернет источников, поэтому я не несу полную ответственность за ее достоверность!
custom 53799027582561584522custom 53281220570099661831custom 53282212106249577421custom 53301111079043496391custom 53303337547140035311custom 53303533913044807661custom 53304053775886336401
Sticker, posted without a caption
Posted without readable text
custom 53281641219196585472custom 53303337547140035312custom 53799027582561584522custom 53281220570099661831custom 53301111079043496391custom 53304053775886336401
Showing the 12 most recent of 20 posts we hold for @promiseLFE. 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 — 40,638 of 1,189,255entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 39 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“L𝐢𝐟e » 承諾'𝖯𝐫𝐨𝐦𝐢𝐬𝖾” (@promiseLFE), 216 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/promiseLFE.
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.