Sticker, posted without a caption

Channel
—. 𝒩 𝗲𝘄 𝘀𝗵𝗶𝗻𝗲|𝗅𝗂𝖿𝖾-𝖼𝗁𝖺𝗇𝖾𝗅
@NewSh1nelife
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
36subscribers
+0 since we began measuring on 27 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003915664444 |
|---|---|
| Type | Channel |
| Username | @NewSh1nelife |
| Description | —.Это Лайф канал ролевой —. 𝒩 𝗲𝘄 𝘀𝗵𝗶𝗻𝗲. |
| Created | Between 1 April 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 27 September 2026 |
| Last confirmed live | 27 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/NewSh1nelife |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Sept 2026, 22:22 | 36 | no change |
| 27 Sept 2026, 21:47 | 36 | first reading |
Engagement
19 posts held, back to 24 September 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 page of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 81.4%
- avg views ÷ 36 subscribers
- Avg views / post
- 29.3
- 16 posts measured
- Reaction rate
- 13.1%
- reactions ÷ views · ER floor
- Posts in window
- 19
- of 19 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 5 of 16 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 27 September 2026 |
|---|---|
| Posts held | 19 (24 September 2026 – 27 September 2026) |
| Views total | 469 |
| Reactions total | 27 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Sept 2026, 22:22 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
- 72
- Videos
- 46
- Links
- 57
Lifetime counters from Telegram’s own channel header, read 27 September 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
- 6s
- Average length
- 6s
Measured directly from 1 video 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
27 reactions across 5 posts, in 7 distinct kinds. The most used accounts for 18.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5303454870123099200 | 5 | 18.5% | |
| ❤ | 5 | 18.5% | |
| custom 5303346782976124796 | 4 | 14.8% | |
| custom 5303522722016438875 | 4 | 14.8% | |
| custom 5301088944438420092 | 3 | 11.1% | |
| custom 5303104881828081743 | 3 | 11.1% | |
| custom 5303379626591036755 | 3 | 11.1% |
Custom emoji. 6 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 5 of the 19 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 27 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 24 September 2026 to 27 September 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
—.🟥🟧🔤егодня в этот чудесный осенний день мы перезаключили союз с милейшими ጠყsᤐֹ᷼ꫀׄdꫀׁׅܻ꯱ . 🔤еперь мы их Пик а они наши Вару. 🐈⬛𝘛𝘢𝘨𝘴: #𝙉𝙨𝙝𝘧𝘢𝘮𝘪𝘭𝘺
🌟
🎁
—.🟥🟧Давайте вы нам добьете 40 подписчиков а я вам ассоциации на тему какой вы пейринг из 13 карт. 🐈⬛𝘛𝘢𝘨𝘴:#𝙉𝙨𝙝_щп
❤4
—.🟥🟧🔤октор, оно опять началось. 🐈⬛𝘛𝘢𝘨𝘴:: #𝙉𝙨𝙝𝘣𝘳𝘦𝘢𝘬
—.🟥🟧 𝗧𝗮𝗿𝘁𝗮𝗹𝘆𝗮𝗻𝘀 𝗳𝗹𝗼𝗼𝗱 мои хорошие, нам очень понравился результат, учитывая что Афины один из моих любимых городов, благодарим за такую ассоциацию. #𝙉𝙨𝙝_щп
Messages in this channel will no longer be automatically deleted
Messages in this channel will be automatically deleted after 1 week
—.🟥🟧 🔤одные напоминаю вам об этом посте. 🐈⬛𝘛𝘢𝘨𝘴: #𝙉𝙨𝙝_щп
Sticker, posted without a caption
🌟🔤🔤🔤 🔤🔤🔤🔤🔤🎁 «Дружба — это когда два "я" становятся одним "мы", но при этом у каждого есть свой запасной ключ». 🔤🔤🔤🔤🔤🔤🔤🔤 , в эту дату был заключёна новая дружба между двумя проектами —. 𝒩 𝗲𝘄 𝘀𝗵𝗶𝗻𝗲 и 𝒫ℯ𝓉𝒶𝓁𝓈 . Надеемся на долгую и надежную дружбу и поддержку 𝗟𝗶𝗳𝗲 #𝙉𝙨𝙝𝘶𝘯𝘪𝘰𝘯
Showing the 12 most recent of 19 posts we hold for @NewSh1nelife. 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.
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.
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.
@AER_life · 501 postÂ𝐌𝐄𝐒 𝔏𝐈É𝐄𝐒 life
@amesllif · 2381 post. ጠყsᤐֹ᷼ꫀׄdꫀׁׅܻ꯱ָׂˏˏ hᦒꬻmꬻׂ . .
@homeMSDs · 751 postʜᴀᴠᴇɴ ᴏғ ᴛʜᴇ ᴍᴏᴏɴᶫᶦᶠᵉ
@hvm_life · 4251 post. ጠყsᤐֹ᷼ꫀׄdꫀׁׅܻ꯱ָׂˏˏ inꬻfᦒꬻׂ . .
@infoMSDs · 881 post𝗟𝗶𝗳𝗲 𝘀𝗵𝗮𝗻𝗻𝗲𝗹 || 𝗧𝗵𝗲 𝗙𝗶𝗿𝗲𝗳𝗹𝘆 𝗙𝗮𝗰𝘁𝗼𝗿𝘆
@lifechannellolofd · 211 post—. 𝒩 𝗲𝘄 𝘀𝗵𝗶𝗻𝗲| 𝘪𝘯𝘧𝘰-𝘤𝘩𝘢𝘯𝘦𝘭|
@NewSh1ne · 511 post[INFO] 𝒫ℯ𝓉𝒶𝓁𝓈
@petals_01 · 991 post𝐿𝑖𝑓𝑒 𝐶ℎ𝑎𝑛𝑛𝑒𝑙 / 𝚀𝚞𝚒𝚎𝚝 𝙾𝚌𝚎𝚊𝚗 𝙵𝚕𝚘𝚘𝚛
@QOF_Life · 3751 post
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 27 September 2026 — this entry's latest reading, not the date you are reading this.
“—. 𝒩 𝗲𝘄 𝘀𝗵𝗶𝗻𝗲|𝗅𝗂𝖿𝖾-𝖼𝗁𝖺𝗇𝖾𝗅” (@NewSh1nelife), 36 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/NewSh1nelife.
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.