Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝒃𝒍𝒐𝒐𝒅𝒚𝒎𝒂𝒓𝒚 𝒄𝒐𝒏𝒇𝒆𝒔𝒔𝒊𝒐𝒏𝒔 ⁺ ᵈᵃⁱˡʸ

Channel

𝒃𝒍𝒐𝒐𝒅𝒚𝒎𝒂𝒓𝒚 𝒄𝒐𝒏𝒇𝒆𝒔𝒔𝒊𝒐𝒏𝒔 ⁺ ᵈᵃⁱˡʸ

@bloodymarycff

On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

250subscribers

+11 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-1003927445052
TypeChannel
Username@bloodymarycff
CreatedBetween 1 April 2026 and 31 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live16 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/bloodymarycff

Growth

239250244.58 August 2026 — 239 subscribers8 August 2026 — 239 subscribers8 August 2026 — 242 subscribers16 August 2026 — 250 subscribers8 August 202616 August 2026
4 measurements spanning 8 days, net +11. 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 237–252 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 06:38250+8
8 Aug 2026, 13:46242+3
8 Aug 2026, 09:50239no change
8 Aug 2026, 09:01239first reading

Engagement

15 posts held, back to 6 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
48.6%
avg views ÷ 250 subscribers
Avg views / post
121
15 posts measured
Reaction rate
22.1%
reactions ÷ views · ER floor
Posts in window
15
of 15 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 14 of 15 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 8 August 2026
Posts held15 (6 August 20268 August 2026)
Views total1,822
Reactions total393
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 09: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.

Reaction mix

393 reactions across 14 posts, in 13 distinct kinds. The most used accounts for 34.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 524270912472616743113734.9%
custom 53618108484718581025413.7%
custom 60328758876265565625313.5%
4310.9%
🍓4210.7%
custom 5242728718366968866246.11%
custom 5242722172836812467194.83%
custom 547223709905691844682.04%
💊71.78%
🍾20.509%
💘20.509%
❤‍🔥10.254%
👀10.254%

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 14 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 393reactions 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 6 August 2026 to 8 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

8 Aug 2026, 07:00 UTC46 viewsread 8 August 2026
Forwarded from @RyanGosling_cf

🔤𝐨 𝐲𝐨𝐮 𝐥𝐢𝐤𝐞 . . . 🤩 🥹🤩🔤yan 🔤osling⁉️ sub!!😄 & 𝘞𝘢𝘯𝘵 𝘧𝘪𝘯𝘥 more ᯓ 🎁🤩 🤩🤩🤩𝘤𝘰𝘯𝘵𝘦𝘯𝘵 𝘸𝘪𝘵𝘩 𝘩𝘪𝘮??🤍 🎬 Then, welcome to our cf + daily

Signed Neo March ⁿᵉᵒˡⁱ 🪐

7 Aug 2026, 14:32 UTC126 views42 reactionsread 8 August 2026
Photo

🥂🥹🥹𝒃𝒍𝒐𝒐𝒅𝒚𝒎𝒂𝒓𝒚 ⁺ ᵈᵃⁱˡʸ 🤩#daily | #art cr 🥹🥹haedyllic🥹X

26custom 53618108484718581029custom 52427091247261674315custom 52427221728368124671custom 60328758876265565621

Signed ㅤ۫𖥻 ִ 𝐻𝖺݊ռ𝘢 ׄ ִ𝐺𝗋𝘢𝚌ꫀׁׅܻ ﹫

7 Aug 2026, 11:05 UTC120 views34 reactionsread 8 August 2026
Photo

🥂🥹🥹𝒃𝒍𝒐𝒐𝒅𝒚𝒎𝒂𝒓𝒚 ⁺ ᵈᵃⁱˡʸ 🤩#daily | #art cr 🥹🥹funkyylizard🥹X

custom 524270912472616743121custom 52427287183669688666custom 52427221728368124674❤‍🔥1custom 53618108484718581021custom 60328758876265565621

Signed ㅤ۫𖥻 ִ 𝐻𝖺݊ռ𝘢 ׄ ִ𝐺𝗋𝘢𝚌ꫀׁׅܻ ﹫

7 Aug 2026, 09:33 UTC116 views31 reactionsread 8 August 2026
Photo

🥂🥹🥹𝒃𝒍𝒐𝒐𝒅𝒚𝒎𝒂𝒓𝒚 ⁺ ᵈᵃⁱˡʸ 🤩#daily | #art cr 🥹🥹GeLoki10🥹X

custom 524270912472616743117custom 54722370990569184467custom 60328758876265565624custom 52427287183669688662custom 53618108484718581021

Signed ㅤ۫𖥻 ִ 𝐻𝖺݊ռ𝘢 ׄ ִ𝐺𝗋𝘢𝚌ꫀׁׅܻ ﹫

7 Aug 2026, 09:07 UTC118 views10 reactionsread 8 August 2026

Дарова!! Ищу сорола по этому шикарному шипу из-за которого мы тут все собрались🥰 У меня кучу идей, а у партнёра щас со мной не совпадает гиперфикс. Ну вот я и ищу с кем поролить. Я разнострочник + почти всегда свободен. Стараюсь писать без ошибок, но запятые оказались сильнее меня(хоть так и не скажешь по началу). Мне если что 18, потому всякие крутые кровавые или очень интересные постельные сцены для меня не проб

custom 53618108484718581025🍾2custom 52427287183669688662custom 60328758876265565621

Signed 𝒃𝒍𝒐𝒐𝒅𝒚𝒎𝒂𝒓𝒚 TAKE

7 Aug 2026, 08:59 UTC116 views22 reactionsread 8 August 2026
Photo

Ладно.. 🫪🫡 Неанон, Или (однажды я оставлю свой ТГК, правда) ゞ #тейк | @bloodymarytakebot

custom 524270912472616743114custom 52427221728368124673custom 53618108484718581022💘1custom 52427287183669688661custom 60328758876265565621

Signed 𝒃𝒍𝒐𝒐𝒅𝒚𝒎𝒂𝒓𝒚 TAKE

7 Aug 2026, 08:00 UTC118 views36 reactionsread 8 August 2026
Photo

HELL YEAH КОНФА ПО БЛАДИМЕРИ!!!!! Неанон, Рене Тгк: @chimere_rene (на арте указано, но мало ли неразборчиво хехе) ゞ #тейк | @bloodymarytakebot

custom 524270912472616743119custom 536181084847185810293custom 52427287183669688663custom 52427221728368124671custom 60328758876265565621

Signed 𝒃𝒍𝒐𝒐𝒅𝒚𝒎𝒂𝒓𝒚 TAKE

7 Aug 2026, 07:57 UTC129 views47 reactionsread 8 August 2026
Photo

И долго мы будем молчать про Евангелион аушку, где бладимэри отсылаются на каосинов..? cr: isza_pizza in inst ゞ #тейк | @bloodymarytakebot

custom 524270912472616743129custom 53618108484718581027custom 524272871836696886641🍓1👀1💘1custom 52427221728368124671

Signed 𝒃𝒍𝒐𝒐𝒅𝒚𝒎𝒂𝒓𝒚 TAKE

6 Aug 2026, 21:22 UTC124 views12 reactionsread 8 August 2026

Хорошо теперь вопрос!!! какая ваша любимая бладимери ау ゞ #тейк | @bloodymarytakebot

💊7custom 52427091247261674312custom 60328758876265565622custom 52427221728368124671

Signed 𝒃𝒍𝒐𝒐𝒅𝒚𝒎𝒂𝒓𝒚 TAKE

6 Aug 2026, 16:44 UTC134 views17 reactionsread 8 August 2026

вот немного фичков, некоторые аушки, потому что очень люблю аушки though i may never be free (обе части завершены)- Саймон думает, что Грейсу следует отплатить. единственное что у него есть его тело и секс ( и вторая часть, где все налаживается и это недопонимание решается) SloeBurn (в процессе) - au! Саймон стример, Грейс его первый подписчик, и у них фейковые отношения. (по началу я ухахатывалась) there is meani

custom 524270912472616743111custom 52427221728368124673custom 53618108484718581023

Signed 𝒃𝒍𝒐𝒐𝒅𝒚𝒎𝒂𝒓𝒚 TAKE

6 Aug 2026, 16:30 UTC136 views31 reactionsread 8 August 2026
Photo

я хочу засунуть его в субмарину и потрясти тгк: @cubeaval ゞ #тейк | @bloodymarytakebot

custom 603287588762655656218custom 524270912472616743174custom 52427221728368124671custom 53618108484718581021

Signed 𝒃𝒍𝒐𝒐𝒅𝒚𝒎𝒂𝒓𝒚 TAKE

6 Aug 2026, 15:30 UTC138 views27 reactionsread 8 August 2026
Photo

Окей, забавная фигня (Саймону не стал рисовать зубы на щеке) Неанон, Или ゞ #тейк | @bloodymarytakebot

custom 5361810848471858102156custom 52427091247261674315custom 52427221728368124671

Signed 𝒃𝒍𝒐𝒐𝒅𝒚𝒎𝒂𝒓𝒚 TAKE

Showing the 12 most recent of 15 posts we hold for @bloodymarycff. 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 — 941,869 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“𝒃𝒍𝒐𝒐𝒅𝒚𝒎𝒂𝒓𝒚 𝒄𝒐𝒏𝒇𝒆𝒔𝒔𝒊𝒐𝒏𝒔 ⁺ ᵈᵃⁱˡʸ” (@bloodymarycff), 250 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/bloodymarycff.

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.