Telegram RegisterThe public register of Telegram
Telegram profile photo for ㅤㅤㅤ𝒔𝒖𝒊𝐜𝐢𝐝𝐚𝒍𝒔𝒘 𝐩𝐫𝐢𝐜𝐞

Channel

ㅤㅤㅤ𝒔𝒖𝒊𝐜𝐢𝐝𝐚𝒍𝒔𝒘 𝐩𝐫𝐢𝐜𝐞

@suicidalsw

On this record: Growth · Engagement · Posts · Citations · Cite this entry

2subscribers

+0 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1003217810354
TypeChannel
Username@suicidalsw
Created5 January 2026measured — dated from the channel’s first post
First recorded17 September 2026
Last confirmed live17 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/suicidalsw

Growth

121.514 August 2026 — 2 subscribers31 August 2026 — 1 subscribers17 September 2026 — 1 subscribers17 September 2026 — 2 subscribers14 August 202617 September 2026
4 measurements spanning 34 days. 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 1–2 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 22:022+1
17 Sept 2026, 13:231no change
31 Aug 2026, 23:481-1
14 Aug 2026, 23:322first reading

Engagement

17 posts held, back to 5 January 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
12230.0%
avg views ÷ 2 subscribers
Avg views / post
245
15 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
15
of 17 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 27 August 2026
Posts held17 (5 January 202627 August 2026)
Views total3,669
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Sept 2026, 13:23 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.

Recent posts

27 Aug 2026, 06:29 UTC293 viewsread 17 September 2026

🥹понадобился впшер? с радостью помогу! ㅤㅤНЕ ПОЙДУ В КАНАЛЫ С ТЕМАТИКОЙ: если они нарушают базу дни, нсфв, прокомдарк, сх, любой слив, рейд,а так же если ваш канал входит в мой дни.(кликбательно) ⎯⎯⎯⎯⎯⎯⎯ 🥹анкета: 𝟎𝟏. суицидал • он/его • @keigosbf 𝟎𝟐. инфо 𝟎𝟑. опыта много. всегда стараюсь делать вп каждый день, хотя бы по одному-два в день. но если говорить про недели, то в неделю от 5 до 15+ вп. зависит от обстоят

27 Aug 2026, 06:26 UTC276 viewsread 17 September 2026

🥹предложить вп всему списку можно под этим постом. ㅤㅤ 🥹могу отказать без причины!🥹

27 Aug 2026, 06:26 UTC266 viewsread 17 September 2026

ㅤㅤㅤㅤㅤ🐏𝟓𝟎𝟎-𝟏𝟎𝟎𝟎+🐏 𝟏. @gossipnetssekaii 𝟓𝟑𝟎+ тематика: подслушано сскм. ㅤ [50+] 🥹DNI: рейдеры, хейт кф/дейли. ㅤㅤ𝟐. @obsessedwIvan 𝟔𝟎𝟎+ тематика: дейли алнст. ㅤ [250+] 🥹DNI: аморал. 𝟑. @sekainetslove 𝟔𝟓𝟎+ тематика: кф по сеткам секая. ㅤ [150+] 🥹DNI: база. ㅤㅤ𝟒. @toyafanclub 𝟖𝟏𝟎+ тематика: дейли секай. ㅤ [500+] 🥹DNI: нсфв,хейт. 𝟓. @ivantilldaily_com 𝟖𝟕𝟎+ тематика: дей

27 Aug 2026, 06:25 UTC235 viewsread 17 September 2026

𝟐𝟑. @alnstfdhates 𝟐𝟒𝟎+ тематика: ХЕЙТ кф алнст. ㅤ [0+] 🥹DNI: аморальщина. ㅤㅤ𝟐𝟒. @americanstage 𝟐𝟒𝟎+ тематика: алнст сетка. ㅤ [50+] 🥹DNI: база, нсфв/л, проблематика. 𝟐𝟓. @chorocheSSKM 𝟐𝟒𝟎+ тематика: кф секай сетки км. ㅤ [70+] 🥹DNI: база, гуро, рейд,нсфв,-филия ㅤㅤ𝟐𝟔. @kus_verses 𝟑𝟎𝟎+ тематика: алнст сетка. ㅤ [40+] 🥹DNI: база. 𝟐𝟕. @innetssekairecognize 𝟑𝟒𝟎+

27 Aug 2026, 06:25 UTC245 viewsread 17 September 2026

ㅤㅤㅤㅤㅤ 🐏𝟏𝟎𝟎-𝟓𝟎𝟎🐏 𝟏. @mini_sekai 𝟏𝟎𝟎+ тематика: секай сетка ㅤ [50+] 🥹DNI: база. 🥹 🥹ВП ИСКЛ С ХОЙО/ТЕМ. РИТМ ИГР ㅤㅤ𝟐. @bless_sekai 𝟏𝟎𝟎+ тематика: секай сетка ㅤ [10+] 🥹DNI: нету. 𝟑. @historyoflilies_sekai 𝟏𝟎𝟎+ тематика: секай сетка ㅤ [0+] 🥹DNI: нсфв. ㅤㅤ𝟒. @Starful_Library 𝟏𝟏𝟎+ тематика: секай сетка ㅤ [0+] 🥹DNI: база,хейт,рейд. 𝟓. @housekinosekai 𝟏𝟏𝟎+ тематика: секай

27 Aug 2026, 06:25 UTC232 viewsread 17 September 2026

ㅤㅤ𝟐𝟑. @WaterDashNET 𝟔𝟎+ тематика: секай сетка [0+] 🥹DNI: политика, 𝟐𝟒. @feralSEKAI 𝟔𝟎+ тематика: секай сетка [10+] 🥹DNI:база. ㅤㅤ𝟐𝟓. @softcloudnet 𝟕𝟎+ тематика: секай сетка ㅤ [0+] 🥹DNI: база, нсфв, проблематика 𝟐𝟔. @akitoclaude 𝟕𝟎+ тематика: саппортсекай ㅤ [0+] 🥹DNI: база. ㅤㅤ𝟐𝟕. @spiritual_resonance 𝟕𝟎+ тематика: секай сетка

27 Aug 2026, 06:25 UTC252 viewsread 17 September 2026

ㅤㅤㅤㅤㅤ🐏𝟎-𝟏𝟎𝟎🐏 𝟏. @Sparxie_Sun 𝟏𝟎+ тематика: саппорт хойо [0+] 🥹DNI: база. ㅤㅤ𝟐. @Mitya_tfd 𝟏𝟎+ тематика: саппорт хойо ㅤ [0+] 🥹DNI: база. 𝟑. @TheBirdCult_SEKAI тематика: секай сетка ㅤ [0+] 🥹DNI: база, нсфв ㅤㅤ𝟒. @NeedySekaiOverdose_net 𝟐𝟎+ тематика: секай сетка ㅤ [0+] 🥹DNI: база. 𝟓. @peculiarsekai_net 𝟐𝟎+ тематика: секай сетка ㅤ [5+] 🥹DNI: база, -филия, нсфв,

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

Names

Channels on the register whose handles appear in this channel's posts.

В АЛНСТ ФД НЕНАВИДЯТ
@ALNSTFDHATES · 342
1 post
𐔌ㅤ 𝓐𝐧𝐠ׁ𝐞𝐥 𝐬𝐞ׁׅ𝐤𝐚𝐢 𖥔ㅤ˖ ݁
@angelsekaii · 30
1 post
[ набор в админы!! ] 𝘼𝙍𝘾𝘼𝙑𝙀 𝙎𝙀𝙆𝘼𝙄: сеть телеграмм каналов
@arcavesekai · 41
1 post
𝗖𝗢𝗗𝗘 𝗩𝗘𝗜𝗡: 𝗻𝗲𝘄 𝗯𝗹𝗼𝗼𝗱🩸
@CODEVEIN_net · 38
1 post
𝑫𝒆𝒆𝒑 𝑺𝒍𝒆𝒆𝒑 𝑺𝑬𝑲𝑨𝑰!𝅄 ׁ ⏜۫‌‌۫۫‌ᮬ︵ ꒰ַᮬ‌࡙۫۫ сеть тг каналов
@DeepSleepTrilogy_Sekai · 54
1 post
0103 LOVE CF
@harufuutaLOVE · 71
1 post
‎ ‎ ‎𝐇ou͟s͟e͟ki 𝐧𝐨 𝐒e͟k͟a͟i ! !
@housekinosekai · 118
1 post
dnidnidni @keigosfavorite
@keigosfavorite · 2
1 post
MIKUdemy ! net
@MIKUdemy_net · 113
1 post
ᅠ›𝗠𝗂𝗻𝖾𝗰𝗋𝗮𝖿𝘁𝗦𝖾𝗸𝖺𝗶⋮ сеть телеграм-каналов!
@MinecraftSekai · 89
1 post
ᴡᴡᴡ. @ 𝓶𝘪𝘯𝘪 🅂𝘦𝘬𝘢𝘪! !
@mini_sekai · 124
1 post
𝓷 𝓸 𝓽 𝓮 𝓫 𝓸 𝓸 𝓴 .
@Mitya_tfd · 18
1 post
𝑵𝒆𝒆𝒅𝒚 𝑺𝒆𝒌𝒂𝒊 𝑶𝒗𝒆𝒓𝒅𝒐𝒔𝒆 || net
@NeedySekaiOverdose_net · 26
1 post
ㅤ:: 𝓝𝐄𝐖 𝓝𝐀𝐌𝐄 ⃟ˢᵉᵏᵃⁱ 📂
@nn_sekai · 63
1 post
𐙚ꪱֹ ˖Pᥱᥴᥙᥣiᥲr 𐍃ᥱκᥲi ͝𓏵
@PeculiarSekai_net · 30
1 post
𝓢𝘢𝘺𝘰𝘯𝘢𝘳𝘢 𝓢𝘦𝘬𝘢𝘪
@Sayo_Nara_Sekai · 60
1 post
⋮ ׅ 𓏴ᅠ𝓢𝗰𝒂𝑟ყ‌︩︪ׄ ׅ𝑆𝗲𝒌𝗮ꪱׁׁׁׅׅׅ ♡̶ ׅ ︎
@ScarySekai · 24
1 post
♯ 𝓢 𝗆𝗈𝗄𝖾𝗋 𝐓𝗋𝗂𝗈 𝖽𝖺𝗂𝗅𝗒 ⤷ 𝖼𝖿 ˎˊ˗
@smokertriomg · 96
1 post
⋮ 𝐒𝗍αᥣ𝗄𝖾𝗋 𓏴 𝐒𝖾𝗀α ֺ
@stalker_sega · 50
1 post
𝓢𝙚𝙠𝕒ⓘ 𝆺𝅥🆂𝐭𝐫𝒆ꨵ𝓪𝙢𝙞𝙣𝙜 ࣪.
@streamingSekai_net · 25
1 post
𝑻𝑯𝑬 𝑪𝑶𝑭𝑭𝑰𝑵 𝑶𝑭 𝑺𝑬𝑲𝑨𝑰
@TCOS_NET · 52
1 post
🕊 𝚃𝚑𝚎 𝙱𝚒𝚛𝚍 𝙲𝚞𝚕𝚝 . . . | ꇙꏂꀘꋬ꒐ ꈤꏂ꓄
@TheBirdCult_SEKAI · 14
1 post
꒰֮ 𝗪𝗔𝗧𝗘𝗥 𝗗𝗔𝗦𝗛 𝘀𝗲𝗸𝗮𝗶 𓏺
@WaterDashNET · 60
1 post
⇉ ZENO SEKAI | NET
@zenoPJSK · 130
1 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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“ㅤㅤㅤ𝒔𝒖𝒊𝐜𝐢𝐝𝐚𝒍𝒔𝒘 𝐩𝐫𝐢𝐜𝐞” (@suicidalsw), 2 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/suicidalsw.

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.