Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝓢𝖺𝗉𝗉𝗁𝗂𝗋𝖾’𝗌 𝗉𝗋𝖾𝖽𝗂𝖼𝗍𝗂𝗈𝗌

Channel

𝓢𝖺𝗉𝗉𝗁𝗂𝗋𝖾’𝗌 𝗉𝗋𝖾𝖽𝗂𝖼𝗍𝗂𝗈𝗌

@sapphire_hw

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

9subscribers

+0 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1002646956485
TypeChannel
Username@sapphire_hw
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live2 September 2026
Measurements held2
On Telegramt.me/sapphire_hw

Growth

912 Aug 2026, 12:19 — 9 subscribers12 Aug 2026, 13:18 — 9 subscribers12 Aug 2026, 12:1912 Aug 2026, 13:18
2 measurements taken within a single day. 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 8–10 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 13:189no change
12 Aug 2026, 12:199first reading

Engagement

20 posts held, back to 30 September 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 17 November 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
7
Videos
1
Links
26

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.

Reaction mix

73 reactions across 18 posts, in 4 distinct kinds. The most used accounts for 64.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💘4764.4%
custom 52988787156131692251216.4%
custom 54701360440053864051216.4%
🕊22.74%

Custom emoji. 2 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 18 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 73 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 September 2025 to 17 November 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

17 Nov 2025, 08:23 UTC34 views3 reactionsread 12 August 2026

— я не сомневаюсь. 🌟 ☺️апфир посмеялась и поцеловала Рубин в щёку “на удачу”, хотя, если верить предвидению, то это не поможет. #𝒆𝒗𝒆𝒏𝒕

💘3

17 Nov 2025, 05:34 UTC34 views2 reactionsread 12 August 2026

— давай попробуем. 🤩 #𝒆𝒗𝒆𝒏𝒕

💘2

17 Nov 2025, 04:36 UTC33 views2 reactionsread 12 August 2026

☺️аконец надурачившись, самоцветы, несмотря на то что теперь они полностью мокрые, решили прогуляться дальше в поисках ещё какого-нибудь занятия.  #𝒆𝒗𝒆𝒏𝒕

💘2

1 Nov 2025, 15:52 UTC41 views5 reactionsread 12 August 2026

— хе-хе, погляжу, ты просто мастер в этом деле. 🌟 так и быть, я попробую. ☺️апфир решила не мелочиться и нырнула в бочку с головой, облив и Рубин, конечно же. После чего вынырнула с яблоком во рту. #𝒆𝒗𝒆𝒏𝒕

🕊2💘1custom 52988787156131692251custom 54701360440053864051

1 Nov 2025, 15:44 UTC37 views5 reactionsread 12 August 2026

☺️апфир умилённо рассмеялась реакции Рубин. — я знаю, что ты очень хочешь. #𝒆𝒗𝒆𝒏𝒕

💘3custom 52988787156131692251custom 54701360440053864051

1 Nov 2025, 15:40 UTC36 views5 reactionsread 12 August 2026

☺️амоцветы шли по красочной и шумной ярмарке, держась за руки. Сапфир увидела так называемое людское развлечение в виде бочки с водой и яблоками. Предвидение подсказало, что Рубин такое бы пришлось по вкусу, так что та предложила: — Руби, смотри, — Сапфир указала пальцем. #𝒆𝒗𝒆𝒏𝒕

💘3custom 52988787156131692251custom 54701360440053864051

31 Oct 2025, 14:19 UTC28 views4 reactionsread 12 August 2026

пойдём, разумеется. #𝒆𝒗𝒆𝒏𝒕

💘2custom 52988787156131692251custom 54701360440053864051

30 Oct 2025, 17:11 UTC17 views1 reactionsread 12 August 2026
Forwarded from @SU_HomeWorld_set

😃: у нас первый хейтер, ура Ладно, я к вам с благой вестью—мы уходим в рест. Нет, не по причине уходов, хотя это тоже верно. Мы с совладельцем и другими участниками пришли к окончательному решению, что нам нужен рест. С этого дня и до конца следующего месяца мы будем делать только ВП. Всех новопришедших, ресты, анресты, уходы мы будем объявлять тогда, когда выйдем из реста. Рибята пака до декабря рибята😆

💘1

30 Oct 2025, 15:16 UTC29 views4 reactionsread 12 August 2026

так много расколотых... я понимаю, я вижу, что это ненадолго, но... всё же... я знаю, мне не стоит поддаваться эмоциям, но... я буду скучать. даже если мы не провели много времени друг с другом, я всё равно успела привязаться к некоторым, даже просто читая так называемые "каналы". что ж, раз уж судьба распорядилась так, значит так нужно.

💘2custom 52988787156131692251custom 54701360440053864051

28 Oct 2025, 15:04 UTC35 views4 reactionsread 12 August 2026

в последнее время так много потерь... но не всё так печально, предвидение подсказывает, что после “чёрной полосы” вскоре наступит белая. не стоит отчаиваться.

💘3custom 52988787156131692251

28 Oct 2025, 10:33 UTC34 views4 reactionsread 12 August 2026
Sticker

Sticker, posted without a caption

💘2custom 52988787156131692251custom 54701360440053864051

28 Oct 2025, 10:28 UTC30 views6 reactionsread 12 August 2026
Photo

из недавних событий: сегодня пробовали с Рубин готовить тыквенный пирог. мне нравится готовить с ней, хотя ей, по-моему, гораздо больше нравится есть. и всё же, я думаю, совместная готовка — один из самый милых видов совместного времяпровождения. 🌟 но есть я всё равно не очень люблю, по крайней мере, главное, что это любит Руби. ❤️ #𝒆𝒗𝒆𝒏𝒕

💘4custom 52988787156131692251custom 54701360440053864051

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

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

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

“𝓢𝖺𝗉𝗉𝗁𝗂𝗋𝖾’𝗌 𝗉𝗋𝖾𝖽𝗂𝖼𝗍𝗂𝗈𝗌” (@sapphire_hw), 9 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/sapphire_hw.

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.