Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝗜𝗡𝗙𝗢 | . 𖦹 𝙎ℇ𝙍𝘌𝙉𝙄𝙏Ƴ₊ ꒱

Channel

𝗜𝗡𝗙𝗢 | . 𖦹 𝙎ℇ𝙍𝘌𝙉𝙄𝙏Ƴ₊ ꒱

@SRN_INF

On this record: Previous handles · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Cite this entry

112subscribers

-17 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003657733851
TypeChannel
Username@SRN_INF
Description— 𝗌𝗍𝖺𝗋𝗍 :: 𝟏𝟒.𝟎𝟐.𝟐𝟔 ° — 𝑳𝑰𝑭𝑬 :: @SRN_LIF — 𝑼𝑵𝑰𝑶𝑵𝑺 :: @UNIONS_SRN
CreatedBetween 1 December 2025 and 5 February 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live16 September 2026
Measurements held4
On Telegramt.me/SRN_INF

Previous handles

@SRN_INF was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@serenity_infoo
held 9 August 20269 August 2026

Growth

112129120.58 August 2026 — 129 subscribers9 August 2026 — 129 subscribers15 August 2026 — 127 subscribers15 September 2026 — 112 subscribers8 August 202615 September 2026
4 measurements spanning 38 days, net -17. 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 109–132 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 03:22112-15
15 Aug 2026, 02:17127-2
9 Aug 2026, 01:31129no change
8 Aug 2026, 11:15129first reading

Engagement

26 posts held, back to 5 February 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
54.7%
avg views ÷ 112 subscribers
Avg views / post
61.3
16 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
16
of 26 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 25 August 2026
Posts held26 (5 February 202625 August 2026)
Views total980
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Sept 2026, 03: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
16
Links
20

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

Reaction mix

45 reactions across 10 posts, in 8 distinct kinds. The most used accounts for 31.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53572810194792291071431.1%
custom 5312018463680652095817.8%
custom 5312422508434055422817.8%
custom 5337314395124957009613.3%
custom 5357184803621867648511.1%
custom 533697645850817469524.44%
custom 533702985783656387612.22%
custom 533719043377886069812.22%

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

Measured over the 26 most recent posts we hold, published 5 February 2026 to 25 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.

Telegram Stars

Stars received
14
across the posts below
Posts paid on
3
of 26 we hold a reading for · 12%
Most on one post
12
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @SRN_INF. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 26 most recent posts we hold for this entry, published 5 February 2026 to 25 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

25 Aug 2026, 19:00 UTC75 viewsread 15 September 2026
Photo

🐏 🩵🩵🩵🩵🩵🩵🩵🩵🐏 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 。○ Тихие, гармоничные звуки растворяют суету, наполняя пространство светом. 🔮 🪧 Мы собрали для вас плейлист, который ассоциируется с нашим проектом. Его можно найти под этим постом, приятного прослушивания! 𝘣𝘢𝘤𝘬 𝘵𝘰 𝘯𝘢𝘷𝘪𝘨𝘢𝘵𝘪𝘰𝘯。。。

25 Aug 2026, 18:55 UTC62 viewsread 15 September 2026
Photo

🐏 🩵🩵🩵🩵🩵🐏 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 。• Игры - неотъемлемая часть жизни нашего флуда. Поэтому мы частенько любим поиграть во что-то. Игры проводят игроведы, владельцы и старшие админы. Со списком игр а также других развлечений можно ознакомиться ниже. >> ..𝗚𝗔𝗠𝗘𝗦 ..˙. 𖦹 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 .𝜗 ☁ Дᴧя дᴏᴨᴏᴧниᴛᴇᴧьных ʙᴏᴨᴩᴏᴄᴏʙ : @srnanonnbot 𝘣𝘢𝘤𝘬 𝘵𝘰 𝘯𝘢𝘷𝘪𝘨𝘢𝘵𝘪𝘰𝘯。。。

25 Aug 2026, 18:54 UTC57 viewsread 15 September 2026
Photo

🐏 🩵🩵🩵🩵🩵 🩵🩵🩵🐏 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 。• 𝖶𝖾 𝖺𝗋𝖾...𝗢𝗣𝗘𝗡 / 𝗖𝗟𝗢𝗦𝗘 ₊ ꒱ [ 𝟣𝟫/𝟦𝟧 ] - без учёта ботов ⌢˙. Если набор будет закрыт - брони будут доступны всегда. Если вы пока не думаете вступать - вы всегда можете указать, что вы ставите бронь на роль. °˖ ꒱꒱ Если ставите бронь - указывайте сроки! 𝘣𝘢𝘤𝘬 𝘵𝘰 𝘯𝘢𝘷𝘪𝘨𝘢𝘵𝘪𝘰𝘯。。。

25 Aug 2026, 18:53 UTC59 viewsread 15 September 2026
Photo

🐏 🩵🩵🩵🩵🩵🩵🩵 🩵🩵🩵🩵🩵🩵🩵🩵🩵🐏 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 ᝰ..𝗢𝗪𝗡𝗘𝗥 « • 𝖦𝖺𝗇𝗒𝗎 «🟥🟧» - @GANYU_SRNbot [мск] Отвечает за всё во флуде. ᝰ..𝗖𝗢-𝗢𝗪𝗡𝗘𝗥 « • 𝖢𝗂𝗉𝗁𝖾𝗋 « 🟥🟧 » - @CIPHER_SRNbot [мск] Правая рука владельца. принимает нью, следит за чатом, проводит интерактивы, отвечает за список, ответственная за ресты, проводит чистки. ᝰ..𝗦𝗘𝗡𝗜𝗢𝗥 𝗔𝗗𝗠𝗜𝗡 « [ 𝟭/𝟮 ] • 𝖫𝗂𝗌𝖺 « 🟥🟧 » - @LISA_SRN_bot [мск] Слежка за чатом,

25 Aug 2026, 18:52 UTC68 viewsread 15 September 2026
Photo

🐏 🩵🩵🩵🩵🩵🩵🐏 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 。• С 14.02.26 наш проект берёт патент на следующие пункты: • название и шрифт нашего проекта - . 𖦹 𝙎ℇ𝙍𝘌𝙉𝙄𝙏Ƴ₊ ꒱ • текст в нашем инфо/лайфе • оформление наших постов (а также баннеров, аватарок) • инициалы • наши видео и идеи для них • наши стикеры и эмодзи! 𐔌 🌟 . Если администрация заметит, что вы пытаетесь выдать вышеперечисленное за своё - мы в полном праве попросить вас переоформи

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

Forward network

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.

Mentions

Named by 1 registered channel — 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.

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

“𝗜𝗡𝗙𝗢 | . 𖦹 𝙎ℇ𝙍𝘌𝙉𝙄𝙏Ƴ₊ ꒱” (@SRN_INF), 112 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/SRN_INF.

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.