Telegram RegisterThe public register of Telegram

Channel

𝑆𝑖𝑙𝑒𝑛𝑡 ࣲ 𝐹𝑜𝑙𝑑 #life

@sf_lifeee

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

79subscribers

+0 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-1003550511965
TypeChannel
Username@sf_lifeee
Descriptionинфо — @sf_infooo ᴧᴀйɸ — @sf_lifeee влᴀдᴇлᴇų — @zxcsosisks
CreatedBetween 1 December 2025 and 31 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held2
On Telegramt.me/sf_lifeee

Growth

799 Aug 2026, 02:01 — 79 subscribers9 Aug 2026, 19:17 — 79 subscribers9 Aug 2026, 02:019 Aug 2026, 19:17
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 78–80 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 19:1779no change
9 Aug 2026, 02:0179first reading

Engagement

20 posts held, back to 21 July 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
69.4%
avg views ÷ 79 subscribers
Avg views / post
54.8
19 posts measured
Reaction rate
9.92%
reactions ÷ views · ER floor
Posts in window
20
of 20 held

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 10 of 19 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 August 2026
Posts held20 (21 July 20263 August 2026)
Views total1,041
Reactions total66
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 19:17 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.

What this channel posts

Photos
232
Videos
13
Links
118

Lifetime counters from Telegram’s own channel header, read 9 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.

Reaction mix

66 reactions across 10 posts, in 11 distinct kinds. The most used accounts for 15.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53437912272821713901015.2%
custom 5341574671970119600812.1%
custom 5341597031569859166710.6%
custom 5343728847177160944710.6%
custom 5343837728893084596710.6%
custom 534376838664609308869.09%
custom 534128069434360778457.58%
custom 534132097684187561146.06%
custom 534172177460000536546.06%
custom 534355238844580549146.06%
custom 534395523490333279746.06%

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 10 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 66reactions 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 21 July 2026 to 3 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

3 Aug 2026, 08:55 UTC156 views7 reactionsread 9 August 2026
Photo

🤩🤩🤩# 𝐂𝐋𝐄𝐀𝐍𝐈𝐍𝐆 ♠️ ✉️𝐡𝐞𝐫𝐞 𝐚𝐫𝐞 𝐧𝐨 𝐫𝐚𝐧𝐝𝐨𝐦 𝐥𝐨𝐬𝐬𝐞𝐬 𝐢𝐧 𝐚 𝐜𝐚𝐬𝐢𝐧𝐨 — 𝐨𝐧𝐥𝐲 𝐫𝐞𝐬𝐭𝐚𝐫𝐭𝐬 𝐨𝐟 𝐭𝐡𝐞 𝐠𝐚𝐦𝐞. 𝐖𝐞 𝐝𝐨𝐧'𝐭 𝐭𝐡𝐫𝐨𝐰 𝐚𝐰𝐚𝐲 𝐜𝐡𝐢𝐩𝐬, 𝐰𝐞 𝐫𝐞𝐜𝐚𝐥𝐜𝐮𝐥𝐚𝐭𝐞 𝐛𝐞𝐭𝐬. 𝐄𝐯𝐞𝐫𝐲 𝐬𝐩𝐢𝐧 𝐢𝐬 𝐚 𝐜𝐡𝐚𝐧𝐜𝐞, 𝐚𝐧𝐝 𝐞𝐯𝐞𝐫𝐲 𝐥𝐨𝐬𝐭 𝐜𝐨𝐢𝐧 𝐜𝐚𝐧 𝐫𝐞𝐭𝐮𝐫𝐧 𝐰𝐢𝐭𝐡 𝐚 𝐛𝐨𝐧𝐮𝐬. ⸼ ۫ ׅ 🌸🌸🥹🥹 ࣪ ࣪ ᴨᴏᴧучиᴧи бᴀн:: ִ ִ › 💧 ‹ Чжун Ли ࣪ ࣪ ᴏᴛдᴇᴧᴀᴧиᴄь ʙᴀᴩнᴏʍ:: ִ ִ › 💧 ‹ Мика 🌨️🅱️ 🅱️ 🅱️🌨️ #𝐜𝐥𝐞𝐚𝐧𝐢𝐧𝐠_𝐒𝐅 🎁 #𝐫𝐞𝐩𝐨𝐫𝐭𝐬_𝐒𝐅

custom 53415970315698591663custom 53417217746000053651custom 53435523884458054911custom 53437288471771609441custom 53439552349033327971

3 Aug 2026, 08:54 UTC61 views5 reactionsread 9 August 2026
Photo

🦊🦊 # 𝐍𝐄𝐖 𝐕𝐈𝐃𝐄𝐎 ♠️ 🔤овое видео уже выложено 🔤 тик-токе проекта .‌ ‌ּ ‌ ‌‌ 🦊🦊 ‌ ‌ ‌ ‌ׄ ‌ ‌ ‌ ‌‌ ‌‌ ‌ ‌ּ ‌‌ ‌ 🤍🤍🤍🤍🤍🤍 𝗰𝗿𝗲𝗮𝘁𝗼𝗿 - Tᴀrᴛᴀgliᴀ 𝗶𝗱𝗲𝗮 - 🥹🥹🥹 🦊 click // поддержать наш проект 🌸🌸🌸🌸🌧️🅱️🅱️🅱️🌨️ #𝐯𝐢𝐝𝐞𝐨_𝐒𝐅

custom 53415746719701196001custom 53415970315698591661custom 53437288471771609441custom 53437912272821713901custom 53438377288930845961

27 Jul 2026, 18:58 UTC99 views11 reactionsread 9 August 2026
Photo

🦊🦊 # 𝐍𝐄𝐖 𝐕𝐈𝐃𝐄𝐎 ♠️ 🔤овое видео уже выложено 🔤 тик-токе проекта .‌ ‌ּ ‌ ‌‌ 🦊🦊 ‌ ‌ ‌ ‌ׄ ‌ ‌ ‌ ‌‌ ‌‌ ‌ ‌ּ ‌‌ ‌ 🤍🤍🤍🤍🤍🤍 𝗰𝗿𝗲𝗮𝘁𝗼𝗿 - Tᴀrᴛᴀgliᴀ 𝗶𝗱𝗲𝗮 - 🥹🥹🥹 🦊 click // поддержать наш проект 🌸🌸🌸🌸🌧️🅱️🅱️🅱️🌨️ #𝐯𝐢𝐝𝐞𝐨_𝐒𝐅

custom 53437912272821713903custom 53417217746000053652custom 53437683866460930882custom 53438377288930845962custom 53415746719701196001custom 53439552349033327971

27 Jul 2026, 07:35 UTC52 views7 reactionsread 9 August 2026
Poll

𝑻𝑬𝑺𝑻 𝑭𝑶𝑹 𝑳𝑼𝑪𝑲 🙀

  1. 🐋9%
  2. 🦊18%
  3. 🌸9%
  4. 🍷27%
  5. 💪36%

Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.

custom 53413209768418756111custom 53415746719701196001custom 53435523884458054911custom 53437288471771609441custom 53437912272821713901custom 53438377288930845961custom 53439552349033327971

27 Jul 2026, 07:34 UTC42 views4 reactionsread 9 August 2026
File

File, posted without a caption

custom 53415970315698591661custom 53437288471771609441custom 53437912272821713901custom 53438377288930845961

27 Jul 2026, 07:34 UTC42 views5 reactionsread 9 August 2026
Photo

🤩🤩🤩🔤Cᴀrd ᴏf ᴛhᴇ dᴀy🔤 ❤️🔤унᴀ, ᴄᴋᴩыʙᴀяᴄь ɜᴀ ᴄʙᴇᴛᴏʍ ᴄᴏᴧнцᴀ, дᴀᴩуᴇᴛ нᴀʍ бᴧᴀᴦᴏᴄᴧᴏʙᴇниᴇ нᴀ нᴏʙый дᴇнь, ᴛᴀᴋ дᴀʙᴀйᴛᴇ жᴇ ᴨᴩиᴄᴧуɯᴀᴇʍᴄя ᴋ ᴄᴇᴦᴏдняɯнᴇʍу ᴨᴩᴏᴩᴏчᴇᴄᴛʙу... 😋7 Мᴇчᴇй 😋 :: 🔤ᴇ ᴨᴧᴏхᴏй, нᴏ ʙᴏɜʍᴏжнᴏ нᴀᴄᴛᴏᴩᴏжᴇнный дᴇнь, ᴋᴏᴦдᴀ ʙы ʙᴩᴏдᴇ ᴄᴨᴏᴋᴏйны, нᴏ ʙ дуɯᴇ ʙᴄё ᴩᴀʙнᴏ ᴋᴀᴋиᴇ-ᴛᴏ ᴨᴏдᴏɜᴩᴇния, ᴋᴀᴋᴀя-ᴛᴏ ᴀᴋᴋуᴩᴀᴛнᴏᴄᴛь. Вᴏɜʍᴏжнᴏ, уɜнᴀёᴛᴇ ᴛᴏ, чᴇᴦᴏ ᴩᴀньɯᴇ нᴇ ɜᴀʍᴇчᴀᴧи, ᴏбᴩᴀщᴀᴇᴛᴇ ʙниʍᴀниᴇ нᴀ ᴋᴀᴋиᴇ-ᴛᴏ ᴛᴏнᴋᴏᴄᴛи, ᴏᴄᴏɜнᴀёᴛᴇ дᴧя ᴄᴇбя чᴛᴏ-ᴛᴏ нᴏ

custom 53415970315698591661custom 53435523884458054911custom 53437288471771609441custom 53437683866460930881custom 53437912272821713901

27 Jul 2026, 06:15 UTC40 views11 reactionsread 9 August 2026

🤩🤩🤩🤩# 𝐍𝐄𝐖 𝐔𝐍𝐈𝐎𝐍 🐋 🤩🤩 🤩🤩💛 ‹ 𝐅𝐑𝐈𝐄𝐍𝐃𝐋𝐘 ༝ ۪ ࣪ ⭐️⭐️⭐️ ⭐⭐ ִ ׅ # ♠️ ࣪ ۪ ࣪ ⭐⭐⭐⭐⭐ 🌸🌸🌸ִ ︵᷼𝓸 𝙑𝙚𝙡𔓕𝙧𝙞𝙖 ִ ᷼ ‌ ྀ 🪨🪨 ༝ 𐌏.𝟏. Iᥒf᧐ — @vveloria_info 🌸🌸🌸🌸 𐌏.𝟐. 𑀉ifᥱ — @vveloria_life 🌸Trᥲᥴκᥱr:: › @vlrphainonbot ❔ ‹

custom 53412806943436077843custom 53415746719701196002custom 53413209768418756111custom 53415970315698591661custom 53435523884458054911custom 53437288471771609441custom 53437683866460930881custom 53437912272821713901

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

27 Jul 2026, 07:35 UTCAnonymous Quiz11 voters

𝑻𝑬𝑺𝑻 𝑭𝑶𝑹 𝑳𝑼𝑪𝑲 🙀

  1. 🐋9%
  2. 🦊18%
  3. 🌸9%
  4. 🍷27%
  5. 💪36%

Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 21 July 2026 to 3 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 88,773 of 1,350,102entries 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

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

“𝑆𝑖𝑙𝑒𝑛𝑡 ࣲ 𝐹𝑜𝑙𝑑 #life” (@sf_lifeee), 79 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/sf_lifeee.

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.