Telegram RegisterThe public register of Telegram
Telegram profile photo for переезд, BLACK SAPPHIRE DAILY . . #мыпротивмотоки

Channel

переезд, BLACK SAPPHIRE DAILY . . #мыпротивмотоки

@sapphire_lovee

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

211subscribers

-16 since we began measuring on 15 August 2026

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

Register entry

Telegram ID-1002457104356
TypeChannel
Username@sapphire_lovee
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 August 2026
Last confirmed live10 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 10 September 2026
On Telegramt.me/sapphire_lovee

Growth

21122721915 August 2026 — 227 subscribers15 August 2026 — 227 subscribers24 August 2026 — 220 subscribers1 September 2026 — 215 subscribers10 September 2026 — 211 subscribers15 August 202610 September 2026
5 measurements spanning 26 days, net -16. 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 209–229 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 07:19211-4
1 Sept 2026, 00:18215-5
24 Aug 2026, 11:34220-7
15 Aug 2026, 10:00227no change
15 Aug 2026, 09:46227first reading

Engagement

20 posts held, back to 30 April 2025the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 2 May 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

300 reactions across 11 posts, in 6 distinct kinds. The most used accounts for 27.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 60216735005220596878327.7%
custom 52962394109651492557926.3%
custom 54494685969525078597424.7%
😈299.67%
👾268.67%
🎉93.00%

Custom emoji. 3 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 are Telegram’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 11 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 300 reactions 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 30 April 2025 to 2 May 2025, 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

2 May 2025, 03:28 UTC≈1,570 views21 reactionsread 15 August 2026

если че постов не будет

👾15custom 60216735005220596876

2 May 2025, 00:56 UTC≈1,590 views35 reactionsread 15 August 2026

и извините все, кто нам подарки, заезды и голоса давал😔😔😔

custom 602167350052205968735

2 May 2025, 00:55 UTCviews —

Channel name was changed to «переезд, BLACK SAPPHIRE DAILY . . #мыпротивмотоки»

2 May 2025, 00:54 UTC≈1,590 views20 reactionsread 15 August 2026

всем пр у нас переезд

custom 602167350052205968720

1 May 2025, 15:04 UTC≈1,550 views27 reactionsread 15 August 2026
Photo

🤩🤩 𝗇𝖾𝗐 𝗉𝗈𝗌𝗍 . . . 🤩admin :: Курасан. ⇄ boost ! @Blackcookie_0Bot ! 🤩cr : UEumyeon40199 on x. 🤩 #BlackSapphire → #art

custom 529623941096514925517custom 54494685969525078595custom 60216735005220596875

1 May 2025, 13:03 UTC≈1,250 views44 reactionsread 15 August 2026
Photo

🤩🤩 𝗇𝖾𝗐 𝗉𝗈𝗌𝗍 . . . 🤩admin :: Собакен. ⇄ boost ! @Blackcookie_0Bot ! 🤩cr : IHateCrimson on x. 🤩 #BlackSapphire → #art

custom 529623941096514925528custom 54494685969525078598🎉4👾3custom 60216735005220596871

1 May 2025, 11:04 UTC≈1,150 views37 reactionsread 15 August 2026
Photo

🤩🤩 𝗇𝖾𝗐 𝗉𝗈𝗌𝗍 . . . 🤩admin :: Корица. ⇄ boost ! @Blackcookie_0Bot ! 🤩cr : ??? on pinterest 🤩 #BlackSapphire → #art

😈19custom 52962394109651492558🎉3👾3custom 54494685969525078592custom 60216735005220596872

1 May 2025, 09:02 UTC639 views46 reactionsread 15 August 2026
Photo

🤩🤩TW :: блекбеллы. 🤩🤩 𝗇𝖾𝗐 𝗉𝗈𝗌𝗍 . . . 🤩admin :: Кристина. ⇄ boost ! @Blackcookie_0Bot ! 🤩cr : Kirikait on x. 🤩 #BlackSapphire → #art→ #other

custom 544946859695250785928custom 60216735005220596878😈6👾2custom 52962394109651492552

1 May 2025, 07:04 UTC557 views43 reactionsread 15 August 2026
Photo

🤩🤩 𝗇𝖾𝗐 𝗉𝗈𝗌𝗍 . . . 🤩admin :: Кристина. ⇄ boost ! @Blackcookie_0Bot ! 🤩cr : kuronokunoku on x. 🤩 #BlackSapphire → #art

custom 544946859695250785922custom 52962394109651492556custom 60216735005220596876😈4👾3🎉2

1 May 2025, 01:00 UTC508 views5 reactionsread 15 August 2026
Photo

—я так хочу увидеть канал про куки ран! —даа, особенно про prune juice cookie!) интересуешься? тебе к нам ┊ 🖤 ⃟ . ִ 🕷 ° ꒱꒱ 🕸 ⃝ админы: рини- влд🍇 мика- вп админ🎂 эмодзи комбо—💜🔮 вп пост хештеги буст тейк бот

custom 54494685969525078595

1 May 2025, 00:30 UTC418 viewsread 15 August 2026
Forwarded from @pricechanellPhoto

🌟🌟🌟В Вашем почтовом ящике новое письмо !! ❌Сеток по куки рану так много, и все с однотипным сюжетом! Когда уже создадут что-то новое?! ❌Тоже надоела эта проблема? Тогда наше письмо специально для Вас! ❌❌❌❌ ❌❌ 🤍🤍 Добро пожаловать в английское графство Йорк. На улицах нашего города царит тишина и спокойствие... Или же так кажется только на первый взгляд? Кажется, каждый персонаж хранит в себе какую-то страшную тайн

1 May 2025, 00:04 UTC344 viewsread 15 August 2026
Forwarded from @LoveCEREMONY_CookieLovePhoto

❌🤩Ах. . .любовь - прекрасное чувство, доказательство привязанности. . .но к кому? 🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀 🎀LOVE CEREMONY - сеть каналов по Cookie Run, где ты можешь стать тем, кто подарит любовь или получить любви!🎀

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

Forward network

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

“переезд, BLACK SAPPHIRE DAILY . . #мыпротивмотоки” (@sapphire_lovee), 211 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/sapphire_lovee.

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.