Channel
@OmoriTriggerCf
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
531subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002605086334 |
|---|---|
| Type | Channel |
| Username | @OmoriTriggerCf |
| Description | • Неанон бот — @OmoriTriggerCf_bot • Анон бот — @AnonOmoriTriggerCf_bot Мы не поддерживаем те тейки которые выкладываем .. |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/OmoriTriggerCf |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 03:50 | 531 | no change |
| 7 Aug 2026, 19:39 | 531 | first reading |
15 posts held, back to 31 July 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 13 of 15 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 15 (31 July 2026 – 7 August 2026) |
| Views total | 3,171 |
| Reactions total | 196 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 03:50 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. Below Telegram’s rounding threshold, so these counts are exact.
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.
196 reactions across 13 posts, in 9 distinct kinds. The most used accounts for 28.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5280843336188438901 | 56 | 28.6% | |
| custom 5246929329526430145 | 49 | 25.0% | |
| custom 5404738496839586859 | 32 | 16.3% | |
| custom 5220205111002811934 | 25 | 12.8% | |
| 🤝 | 14 | 7.14% | |
| 💊 | 11 | 5.61% | |
| ❤ | 7 | 3.57% | |
| custom 5280763509926276958 | 1 | 0.51% | |
| 🔥 | 1 | 0.51% |
Custom emoji. 5 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 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 13 of the 15 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 196reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 31 July 2026 to 7 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.
🍉 Хочешь узнать мысли других об омори и почитать различные хэдканоны и теории? 🤩🤩 Хочешь сам поделиться своими мыслями о персонажах и лоре? 🙂🙂 Миллион часов гиперфикса, ищешь вдохновение и место, где людям действительно будет интересно дотошно обсуждать твою любимую игру? ⭐️️️️️️️⭐️️️️️️️⭐️️️️️️️⭐️️️️️️️ 🎻🙂🙂🙂 𝐖𝐞𝐥𝐜𝐨𝐦𝐞 𝐭𝐨... 😀😀😀😀😀 𝙃𝙀𝘼𝘿𝘾𝘼𝙉𝙊𝙉 …
Signed ㅤ⤷ 𝗍.𝗺𝗲/𝗁𝗈𝗌𝗁𝗶 ˓˓ㅤ
интерактив потому что в канале опять тихо какой ваш любимый пейринг и почему? Или же у вас нету любимый пейрингов? Прошу вас без ссор в комментариях и без проблематичных пейрингов, иначе вы получите бан #интерактив
Signed ㅤ⤷ 𝗍.𝗺𝗲/𝗁𝗈𝗌𝗁𝗶 ˓˓ㅤ
+ К ПРОШЛОМУ ТЕЙКУ У МЕНЯ ЕБЕЙШИЙ ТРИГГЕР НА САУНДТРЕК MY TIME СУКА ЭТО КОШМАР, Я НАЧИНАЮ БИТЬСЯ В КОНВУЛЬСИЯХ И КАТАТЬСЯ ПО ПОЛУ КОГДА СЛЫШУ СРАНОЕ CLOSE. ПОЖАЛУЙСТА ОПЛАТИТЕ МНЕ ПСИХОЛОГА неанон ада @OmoriTriggerCf_bot | #Т3йк
custom 528084333618843890113💊5
Signed ㅤ⤷ 𝗍.𝗺𝗲/𝗁𝗈𝗌𝗁𝗶 ˓˓ㅤ
У МЕНЯ ТРИГГЕР НА ЭТО ГОВНО неанон ада @OmoriTriggerCf_bot | #Т3йк
custom 52808433361884389018custom 54047384968395868591
Signed ㅤ⤷ 𝗍.𝗺𝗲/𝗁𝗈𝗌𝗁𝗶 ˓˓ㅤ
Триггер на японский фд омори твиттер, рисующий арты капитану космопарню Почему-то половина японского омори твиттера рисует с ним не только ебучий шотакон, но ещё и именно ПИССКИНК. Я не знаю почему им именно ЭТО нравится и меня это убивает очень, просто если ты наткнулся на яп арт с спейсбф это 80% что-то с ебучим писскинком это неизбежно @OmoriTriggerCf_bot | #Т3йк
custom 52469293295264301459custom 52202051110028119346
Signed ⣦ ִྀི 𝕖р𝖾⃪ܵۜ֞сь))0𖧁᳟) 👀𓈒♡゙ 🔪
Триггер… в общем-то на японский фд омори в твиттере. @OmoriTriggerCf_bot | #Т3йк
custom 522020511100281193410custom 54047384968395868593❤2💊2custom 52469293295264301451
Signed re
Триггер на этого худа который suggestive арты с санфлаверами и найтшейдами рисует ну просто это что сукаааа @OmoriTriggerCf_bot | #Т3йк
custom 540473849683958685910💊4custom 52807635099262769581
Signed ㅤ⤷ 𝗍.𝗺𝗲/𝗁𝗈𝗌𝗁𝗶 ˓˓ㅤ
Триггер на снежных ангелов на омори руте, ну типо бля пиздец я на то, чтобы убить всех этих 7 тварей потратил почти столько же времени, сколько на убийство капитана космопарня Они ещё и не пропадают с их локации после его убийства и бегают за тобой как угарелые и тебе мансить от них бля просто чтобы с локации выйти @OmoriTriggerCf_bot | #Т3йк
🤝14custom 52808433361884389013custom 54047384968395868593❤1
Signed ⣦ ִྀི 𝕖р𝖾⃪ܵۜ֞сь))0𖧁᳟) 👀𓈒♡゙ 🔪
Пр. Триггер на улитика. Сука улитик как по мне самый уебищный персонаж во всем хедспейсе Куда бы я не пошла оно тут и еще блять ебать проходы закрывает ТИПО БЛЯТЬ СУКА ДАЙ МНЕ ПРОЙТИ НАХУЙ Я НЕ ХОЧУ В ДРАКУ ПОПАДАТЬ СЕЙЧАС НАХУЙ МНЕ ОНО Ну думаю вы меня услышали д Неанон соль @OmoriTriggerCf_bot | #Т3йк
custom 528084333618843890114❤1
Signed ㅤ⤷ 𝗍.𝗺𝗲/𝗁𝗈𝗌𝗁𝗶 ˓˓ㅤ
триггер на это. @OmoriTriggerCf_bot | #Т3йк
custom 52808433361884389017❤3custom 54047384968395868593
Signed ㅤ⤷ 𝗍.𝗺𝗲/𝗁𝗈𝗌𝗁𝗶 ˓˓ㅤ
У МЕНЯ ЕБЕЙШИЙ ТРИГГЕР НА ЭТУ ХУЙНЮ БЛЯЯЯЯТЬ КТО ЭТО СОЗДАЛ неанон ада @OmoriTriggerCf_bot | #Т3йк
custom 528084333618843890111custom 52469293295264301451
Signed ⣦ ִྀི 𝕖р𝖾⃪ܵۜ֞сь))0𖧁᳟) 👀𓈒♡゙ 🔪
триггер на то, насколько в омори фд любят романтизировать и нормализовывать всякую фигню. ок, любите, шипперите, рисуйте что хотите, но поч это воспринимается за норму. у ру фд вообще отдельный прикол с тем, что они пытаются отшучиваться и/или в принципе считают проблематик контент или людей поводом для шутки или признаком крутости. im so fucking scared. @OmoriTriggerCf_bot | #Т3йк
custom 54047384968395868597
Signed ⣦ ִྀི 𝕖р𝖾⃪ܵۜ֞сь))0𖧁᳟) 👀𓈒♡゙ 🔪
Showing the 12 most recent of 15 posts we hold for @OmoriTriggerCf. 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 — 586,144 of 1,336,469entries 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 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.
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.
“[ НАБОР В АДМ ] — 💢💡 | .OM0RI TRIGGER!!” (@OmoriTriggerCf), 531 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/OmoriTriggerCf.
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.