Channel
@Ichigo_Bloody
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
14subscribers
+0 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004309539818 |
|---|---|
| Type | Channel |
| Username | @Ichigo_Bloody |
| Description | ɪ ᴅᴏɴ’ᴛ ᴡᴀɴɴᴀ ʙᴇ ʏᴏᴜʀ ꜰʀɪᴇɴᴅ, ɪ ᴡᴀɴɴᴀ ᴋɪꜱꜱ ʏᴏᴜʀ ʟɪᴘꜱ… ɪ ᴡᴀɴɴᴀ ᴋɪꜱꜱ ʏᴏᴜ ᴜɴᴛɪʟ ɪ ʟᴏꜱᴇ ᴍʏ ʙʀᴇᴀᴛʜ…! работаю тут: @BloodyYTTD |
| Created | Between 1 June 2026 and 6 August 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Ichigo_Bloody |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 01:31 | 14 | no change |
| 9 Aug 2026, 04:47 | 14 | first reading |
20 posts held, back to 6 August 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 16 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 10 August 2026 |
|---|---|
| Posts held | 20 (6 August 2026 – 10 August 2026) |
| Views total | 297 |
| Reactions total | 36 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 01:31 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 12 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.
36 reactions across 16 posts, in 3 distinct kinds. The most used accounts for 63.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 💘 | 23 | 63.9% | |
| 🍓 | 10 | 27.8% | |
| 💋 | 3 | 8.33% |
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 16 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 36reactions 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 6 August 2026 to 10 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.
.🎀༘⋆ ⊹₊‧︵‿₊୨ᰔ୧₊‿︵‧₊⊹ ִֶָ🪽་༘ Я смотрела на закрытую за мной дверь. Всегда рада поговорить с Мейпл..постараюсь чаще ее навещать, а сейчааас…очень устала, хочу спать. Но перед этим нужно обязательно вернуться в свой офис и убраться там. Пока я разбиралась с этими бесконечными бумагами, оставила на полу немного мусора. Тогда я просто не могла прибраться, потому что была слишком злой. Good time to talk, right? 𖧷₊˚˖𓍢ִ🍓✧˚…
🍓2💘1
.🎀༘⋆ ⊹₊‧︵‿₊୨ᰔ୧₊‿︵‧₊⊹ ִֶָ🪽་༘ Я спокойно кивнула и усмехнулась, поставив фарфоровую чашку обратно на столик. Чай был... просто блаженным, чего уж там. Он мне действительно очень понравился. — Это всегда хорошо узнавать что-то новое, особенно такой, как ты. Хмм.. — Опустив взгляд на пол, я на пару секунд о чем-то задумалась, но тут же вернула свое внимание к Мейпл, чтобы не показаться грубой или не создать впечатление…
💘3
.🎀༘⋆ ⊹₊‧︵‿₊୨ᰔ୧₊‿︵‧₊⊹ ִֶָ🪽་༘ Наконец-то она успокоилась..все таки не очень-то и хочется, чтобы на ее плач пришли коллеги. Хотя, думаю, что уже все разошлись по домам. — Ах, нет нет..благодарю за беспокойство, но я правда могу сама за себя постоять и решить свои проблемы. — Я откашлялась и убрала руку, чтобы взяться за ручку чашки. Плавно поднеся её к губам, я сдула пар с горячего напитка. — больше ничего такого при…
💘3
.🎀༘⋆ ⊹₊‧︵‿₊୨ᰔ୧₊‿︵‧₊⊹ ִֶָ🪽་༘ Я вздрогнула от резкого плача. Совсем позабыла, что Мэйпл настолько эмоциональна... Я её сильно расстроила, наверное. Даже не знаю, как её теперь успокоить... — Эй, ну чего сразу рыдать-то?!?..Эмм…мне не нужна помощь, сама разберусь!! — Мягко улыбнувшись, я поднялась с дивана и подошла ближе, чтобы тихонько положить ей ладонь на плечо — Не волнуйся так за меня, дорогая. — Good time to …
💘2🍓1
.🎀༘⋆ ⊹₊‧︵‿₊୨ᰔ୧₊‿︵‧₊⊹ ִֶָ🪽་༘ — Ага. Я в принципе перестала много есть. Мне посоветовали новую диету и строго ей придерживаюсь — я осмотрела комнату, тут всегда так чисто..иногда удивляюсь, как Мейпл так быстро наводит тут чистоту. Нет. Не люблю долго молчать, да и вообще, некультурно как-то скрывать свои проблемы от друзей…иначе придет ещё больше вопросов, как мне потом все разгребать? — Ну..я стала гораздо чаще зл…
💘2
.🎀༘⋆ ⊹₊‧︵‿₊୨ᰔ୧₊‿︵‧₊⊹ ִֶָ🪽་༘ — ..да. Из-за прически. — Стоит ли мне говорить, что я к каждой даме в нашей организации так обращаюсь?..ладно, не буду. Услышав вопрос Мейпл, я убрала руки от своих волос. Трясусь как лист, но всё равно пытаюсь вести себя как обычно. — Да нет..ничего не случилось. Работаю..вот, начала следить за собой наконец, а то есть одни сладости не очень-то и здорово, понимаешь? Хотя.. — Я посмот…
💘3
.🎀༘⋆ ⊹₊‧︵‿₊୨ᰔ୧₊‿︵‧₊⊹ ִֶָ🪽་༘ — А..ахаха, точно, совсем забыла! Что-то я в последнее время сама не своя.. — Я неловко посмеялась и аккуратно присела за маленький столик, поправив юбку. Пальцами перебирала свои локоны. И из-за чего я так распереживалась? Глупости какие-то. — Белый..или чай с мятой. Какой найдешь, сладкая. — Good time to talk, right? 𖧷₊˚˖𓍢ִ🍓✧˚.🎀༘⋆ﾟ＊
🍓1💘1
.🎀༘⋆ ⊹₊‧︵‿₊୨ᰔ୧₊‿︵‧₊⊹ ִֶָ🪽་༘ Ха, рада, что она открыла. С легкостью на душе я вошла в комнату подруги. Розовая..красивый цвет. Пф, говорю так, будто бы впервые тут нахожусь. — Прости, если разбудила. Я сюда пришла, чтобы провести с тобой время и выпить немного чая, ты не против? — Good time to talk, right? 𖧷₊˚˖𓍢ִ🍓✧˚.🎀༘⋆ﾟ＊
🍓2💘1
.🎀༘⋆ ⊹₊‧︵‿₊୨ᰔ୧₊‿︵‧₊⊹ ִֶָ🪽་༘ Набрав в лёгкие воздуха и ещё пару раз постучавшись, я поняла, что мне вряд ли ответят, пока не представлюсь. Неприлично такой леди, как я, приходить просто так и не сказать, кто ты. — Мейпл, дорогая, есть минутка? Это Ичиго, не волнуйся… — Я сказала это непривычно нежным и спокойным голосом. Good time to talk, right? 𖧷₊˚˖𓍢ִ🍓✧˚.🎀༘⋆ﾟ＊
🍓1💘1
.🎀༘⋆ ⊹₊‧︵‿₊୨ᰔ୧₊‿︵‧₊⊹ ִֶָ🪽་༘ — я пришла к Мейпл. Сегодня совсем настроения не было, пыталась не сорваться на первого, кого увидела бы.. Мой собственный офис ощущался СЛИШКОМ громким, тьфу! В такие моменты мне необходима компания, а Мейпл приятный собеседник) Плюс, мы давно не виделись. Я хочу выпить с ней чашечку чая…или две. Может три. В общем, столько, сколько потребуется, пока не приду в норму. 𖧷₊˚˖𓍢ִ🍓✧˚.🎀༘⋆ﾟ＊
🍓2💘1
Sticker, posted without a caption
Photo, posted without a caption
Showing the 12 most recent of 20 posts we hold for @Ichigo_Bloody. 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 — 1,073,606 of 1,481,217entries 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.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“ʸᵒᵘʳ ᵍʳᵃᶜⁱᵒᵘˢ ᵖʳⁱⁿᶜᵉˢˢ” (@Ichigo_Bloody), 14 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Ichigo_Bloody.
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.