Telegram RegisterThe public register of Telegram
Telegram profile photo for «Ивент» 𝘍u𝘶𝘵𝘢 Ꮶꭺꭻꮖꭹꭺꮇꭺ!. 003.

Channel

«Ивент» 𝘍u𝘶𝘵𝘢 Ꮶꭺꭻꮖꭹꭺꮇꭺ!. 003.

@FuutaKajiyamaNet

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

19subscribers

+2 since we began measuring on 24 August 2026

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

Register entry

Telegram ID-1004275496991
TypeChannel
Username@FuutaKajiyamaNet
CreatedBetween 1 May 2026 and 21 August 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded24 August 2026
Last confirmed live25 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 25 August 2026
On Telegramt.me/FuutaKajiyamaNet

Growth

17191824 Aug 2026, 05:16 — 17 subscribers24 Aug 2026, 05:30 — 17 subscribers25 Aug 2026, 05:43 — 19 subscribers24 Aug 2026, 05:1625 Aug 2026, 05:43
3 measurements spanning 1 day, net +2. 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 17–19 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Aug 2026, 05:4319+2
24 Aug 2026, 05:3017no change
24 Aug 2026, 05:1617first reading

Engagement

20 posts held, back to 21 August 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
82.3%
avg views ÷ 19 subscribers
Avg views / post
15.6
19 posts measured
Reaction rate
47.3%
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 8 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 24 August 2026
Posts held20 (21 August 202624 August 2026)
Views total297
Reactions total53
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken24 Aug 2026, 05:30 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.

Reaction mix

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53484738540313394641222.6%
custom 53485678279157742751120.8%
custom 5370831452319555296815.1%
custom 5370754744203647018611.3%
custom 5370978108272843362611.3%
custom 537098357147124220647.55%
💯35.66%
❤‍🔥11.89%
🍓11.89%
👻11.89%

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 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 8 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 53reactions 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 August 2026 to 24 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

24 Aug 2026, 03:38 UTC3 views1 reactionsread 24 August 2026

Пр л**хи🌟 сегодня у нас Фута х Сопляк 🌟🌟

custom 53709781082728433621

22 Aug 2026, 17:13 UTC12 views5 reactionsread 24 August 2026

🌟❕🤩🤩🤩🩸🩸🤩 🌙🌟ꫀ‌‌🅦⃘ׅᩬᮬ゙⃝ p𖹭‌‌‌፝֟s৳𐇽! ׅؖ𓏵 #RP_POST🎮 🌟ута немного набрал воздух в свои легкие, немного расслабляясь, но все еще был на меньшем взводе. И мгновенно посмотрел в пол, немного стыжась своей реакции на него, но все же.. Челюсть?.. Это глупости! Глупости.. Такое бывает только в играх! - ..... - 🔹звините!.. Все же погорячился сразу.. Не каждый день, увидишь перед собой 🔹🔹🔹такое существо. 🩸

custom 53485678279157742752custom 53484738540313394641custom 53708314523195552961custom 53709781082728433621

22 Aug 2026, 13:20 UTC18 views9 reactionsread 24 August 2026

🌟❕🤩🤩🤩🩸🩸🤩 🌙🌟ꫀ‌‌🅦⃘ׅᩬᮬ゙⃝ p𖹭‌‌‌፝֟s৳𐇽! ׅؖ𓏵 #RP_POST🎮 🌟ыжеволосый не ожидал ничего, буквально ничего. Но такого блять! Что бы сзади тебя был какой-то чел, тем более с ЧЕЛЮСТЯМИ ЗАМЕСТО БОШКИ?!.. ЧЕГО БЛЯТЬ??? В горле все как будто пересохло, А губы напряженно сжимались вместе, и с расскрытыми глазами тот глядел на существо. Фуута явно был напряжен, это было видно по его сжатым плечам к себе, и одним глазо

custom 53484738540313394642custom 53485678279157742752👻1custom 53707547442036470181custom 53708314523195552961custom 53709781082728433621custom 53709835714712422061

22 Aug 2026, 12:53 UTC18 views10 reactionsread 24 August 2026

"Омг, это это челюсти, или чеее😱😱😱"

custom 53484738540313394643custom 53707547442036470182custom 53708314523195552962❤‍🔥1💯1custom 53485678279157742751

22 Aug 2026, 12:43 UTC21 views7 reactionsread 24 August 2026

Пр л**хи🌟 первый день у нас Фута х Кейн 🌟🌟

custom 53484738540313394642custom 53485678279157742752custom 53707547442036470181custom 53708314523195552961custom 53709781082728433621

22 Aug 2026, 12:32 UTC5 views4 reactionsread 24 August 2026
Forwarded from @FANDOMSnetPhoto

#Ивент 🌟 🌟🌟🌟🌟🌟🌟 🌟 Oh no! Кажется, им придется встретиться лицом к лицу... 😏 🍷 > Все персонажи телепортировались в отдельные дома, где рука одного персонажа скована наручниками с рукой другого на неделю! Им предстоит провести время скованными наручниками между собой, так ещё и "партнёр" меняется каждый день. Давайте же посмотрим на то, как они (наверное) веселятся! ⚫️⚫️⚫️⚫️⚪️⚫️⚪️⚪️⚪️ ⚪

custom 53485678279157742752custom 53708314523195552961custom 53709835714712422061

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

Citation-graph rank — 781,834 of 1,620,105entries 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

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 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.

Names

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

event ❨ ᧃׄ𐐼‌ׄ𝕚ִ𐓣꯭ׄ ❩ 𖹬
@cainTADC_NET · 106
2 posts
event эɞ⍺ִн̈ ⍺ִϕꭑ𝑜н̈
@EvanAftonblog · 24
2 posts
[ИВЕНТ] 𝘈𝘥𝘢𝘮 𝘔𝘪𝘭𝘭𝘪𝘨𝘢𝘯&𝘔𝘪𝘤𝘩𝘢𝘦𝘭
@adamndmichael · 16
1 post
Event˚₊· ͟͟͞͞➳𝓐𝓵𝓲𝔃𝓪 ݁˖ 𐙚 ˖ ݁𖥔 ݁
@aliza_nett · 21
1 post
ꃳ꒐꒒꒒'ꇙ ꋪꏂꇙꏂꋬꋪꉔꀿ ꒻ꄲ꒤ꋪꈤꋬ꒒{ИВЕНТ}
@BillCipher_StarFalls · 17
1 post
Event. ˚₊· ͟͟͞͞Chara Dreemurr ݁˖ ݁𖥔 ݁
@charadreemurr_net · 24
1 post
Dude . Ивент
@DudeFDbet · 21
1 post
[ИВЕНТ]♟#Эмир
@emir_Loxx · 26
1 post
[ИВЕНТ]❕⋆. 𝙂𝙚𝙧𝙢𝙖𝙣𝙮 . 💉
@German_net · 18
1 post
event ֵ۫಄ᩧ̶⃨̫ۣ𝆹᳝࣪ ֵᨢ𑄹ટִ Тᥱ̸ׁⲧ̸ּׁ͠︵ۭ᷼⌒᳟
@GodTetNET · 22
1 post
! ყ۫чꭎꭑᥱꪒ̤ⱃ 𝕜᳕𝑜թ𝑜 ۫᥋ᥱн̈۫᥋ᥱū۫ !
@KorosenseibLog · 19
1 post
.𝑳𝘦𝘰𝘯 𝑻𝘳𝘦𝘮𝘣𝘭𝘢𝘺.com
@LeonTremblay_net · 17
1 post
архив | — #MICHAEL 𝖠𝖿𝗍𝗈𝗇
@MichaelAftonNet · 27
1 post
event░⃟ⴇ⃜𝐥࣪𝕔ჩ⃪ꫀ‌‌⃝‌⃨𝐥࣪𝐥࣪ꫀ‌‌.
@michelle_aftonnet · 15
1 post
event ׄrᥲۢࠖr🄸⃝৳𐇽y⌒‌⃨፝‌⃘𐇽፝֟
@rarityNETpyp · 28
1 post
R4VE XD ИВЕЕНТТ ^3^
@RAVE_Net · 22
1 post
𐍂ꤕ꤯ꤍꤖ᥉꤈꤯ꤍꤖ𑀱սꤙɠ🥀
@reichsl1chtung · 22
1 post
𝑲𝒏𝒊𝒈𝒉𝒕.
@The_Knight_That_Hollow · 21
1 post
[Ивент] Oᕼ ᑎO. IT'S ᖇᗩIᑎIᑎG ᗩGᗩIᑎ.
@TheRainNet · 15
1 post
Event.ࣳ‌ 𖧧 Ͳɾʝρωʝɾεʾ ִ ׂ ♡⃘ ࣪ . ֹ ۪ ♡
@tripwire_net · 14
1 post
[ИВЕНТ] V1! 🩸
@V1umer · 25
1 post
EVENT | William Afton. [🪓]
@WilliamAftonNet · 26
1 post
EVENT | Wolverine | Logan.
@WOLVERINE_NET · 18
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 25 August 2026 — this entry's latest reading, not the date you are reading this.

“«Ивент» 𝘍u𝘶𝘵𝘢 Ꮶꭺꭻꮖꭹꭺꮇꭺ!. 003.” (@FuutaKajiyamaNet), 19 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/FuutaKajiyamaNet.

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.