Telegram RegisterThe public register of Telegram
Telegram profile photo for Arsip Ribbon Hospital

Channel

Arsip Ribbon Hospital

@arsiprbh

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

7subscribers

+0 since we began measuring on 3 November 2026

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

Register entry

Telegram ID-1004377578203
TypeChannel
Username@arsiprbh
CreatedBetween 1 June 2026 and 30 September 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded3 November 2026
Last confirmed live12 November 2026
Measurements held2
On Telegramt.me/arsiprbh

Growth

73 Nov 2026, 06:49 — 7 subscribers3 Nov 2026, 07:22 — 7 subscribers3 Nov 2026, 06:493 Nov 2026, 07:22
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 6–8 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Nov 2026, 07:227no change
3 Nov 2026, 06:497first reading

Engagement

20 posts held, back to 23 October 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
2797.1%
avg views ÷ 7 subscribers
Avg views / post
196
20 posts measured
Reaction rate
0.334%
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 2 of 20 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 23 October 2026
Posts held20 (23 October 2026 – 23 October 2026)
Views total3,916
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Nov 2026, 07:22 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.

What this channel posts

Photos
1
Links
5

Lifetime counters from Telegram’s own channel header, read 3 November 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

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1100.0%

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 2 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 1 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 23 October 2026 to 23 October 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

Telegram’s own ‘edited’ marker: 7 of 20 posts held from the last 30 days (35.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

23 Oct 2026, 17:21 UTC107 views1 reactionsread 3 November 2026

𓇼 𓈒 𝐒𝐔𝐌𝐌𝐄𝐑 𝐈𝐍𝐓𝐀𝐊𝐄 𓏲 🐚 pssstt ... ☀️ Halo, little sunshine! Ada calon summer buddy yang ingin berlabuh di pulau hangat Ribbon Hospital! 🏝️🎀 Berikut data yang perlu diisi sebelum memulai petualangan bersama kami! ୨ৎ ִֶָ Nama Lengkap: ୨ৎ ִֶָ Username: ୨ৎ ִֶָ ID Telegram: ୨ৎ ִֶָ Divisi yang Dipilih: ୨ৎ ִֶָ Divisi Cadangan: ୨ৎ ִֶָ Alasan Ingin Bergabung: ୨ৎ ִֶָ Link Postingan Channel: 𓇼 ⋆。˚ 𓆉 Semilir angin, hangatnya me…

❤1

23 Oct 2026, 17:15 UTC140 viewsread 3 November 2026
File

🌴✨ 𝑺𝑼𝑴𝑴𝑬𝑹 𝑽𝑰𝑩𝑬𝑺 : 𝑱𝑶𝑰𝑵 𝑾𝑰𝑻𝑯 𝑾𝑨𝑹𝑴 𝑭𝑨𝑴𝑰𝑳𝒀! .. 𝟒𝟖𝐇 𝐍𝐄𝐖 𝐂𝐑𝐄𝐖 𖤓 𝓢ummer has arrived! ✨ Ribbon Hospital is once again opening its doors to dedicated individuals who wish to spread warmth, cheer, and provide the best possible care at our hospital. ⌕ GET YOUR PASS HERE : 🏖 / https://t.me/Ribbonhospital/9306 🏖 / https://t.me/Ribbonhospit…

23 Oct 2026, 17:13 UTC192 views0 reactionsread 3 November 2026
Photo

ㅤ🏖️ 𝗀𝗋𝖾𝖾𝗍𝗂𝗇𝗀𝗌! 𝖨 𝖺𝗆 [ Avelisse Elunéa Vaelune + @avelishz ] 𝖿𝗋𝗈𝗆 [Customer Service], 𝖻𝗋𝗂𝗇𝗀𝗂𝗇𝗀 𝗌𝗎𝗇𝗌𝗁𝗂𝗇𝖾 𝖺𝗇𝖽 𝗌𝗎𝗆𝗆𝖾𝗋 𝗏𝗂𝖻𝖾𝗌 𝗍𝗈 𝗍𝗁𝖾 Ribbon 𝖧𝗈𝗌𝗉𝗂𝗍𝖺𝗅 𝗍𝖾𝖺𝗆 𝗋𝖾𝖼𝗋𝗎𝗂𝗍𝗆𝖾𝗇𝗍! ☀️🌊 ㅤㅤㅤ𝖺𝗌 𝗍𝗁𝖾 𝗌𝗎𝗆𝗆𝖾𝗋 𝗌𝗉𝗂𝗋𝗂𝗍 𝗌𝖺𝗒𝗌 ⋮ “ 𝘓𝘦𝘵 𝘠𝘰𝘶𝘳 𝘚𝘮𝘪𝘭𝘦 𝘚𝘩𝘪𝘯𝘦 𝘉𝘳𝘪𝘨𝘩𝘵𝘦𝘳 𝘛𝘩𝘢𝘯 𝘛𝘩𝘦 𝘚𝘶𝘯—𝘔𝘢𝘬𝘦 𝘛𝘩𝘪𝘴 𝘚𝘶𝘮𝘮𝘦𝘳 𝘜𝘯𝘧𝘰𝘳𝘨𝘦𝘵𝘵𝘢𝘣𝘭𝘦! ” 🌻 ㅤ➜ ❲ ☀️ ❳ 𝖲𝗎𝗇𝗌𝗁𝗂𝗇𝖾 𝗆𝗈𝖽𝖾 𝗈𝗇! 𝖨'𝗆 𝖻𝗋𝗂𝗇𝗀𝗂𝗇𝗀 𝟣𝟢𝟢% 𝖾𝗇𝗍𝗁𝗎𝗌𝗂𝖺𝗌𝗆, 𝗐𝖺𝗋𝗆 𝗌𝗆𝗂𝗅𝖾𝗌, 𝖺𝗇𝖽 𝖿𝗋𝖾𝗌𝗁 𝖾𝗇𝖾𝗋𝗀𝗒 𝗍𝗈 𝗆𝖺𝗄𝖾 𝗈𝗎𝗋 𝗍𝖾𝖺𝗆 𝗌𝗁𝗂𝗇𝖾 𝖺𝗌 𝖻𝗋𝗂𝗀𝗁𝗍 𝖺𝗌 𝖺 𝗌𝗎𝗆𝗆𝖾𝗋 𝖽𝖺𝗒! 🍹✨

23 Oct 2026, 17:10 UTC254 viewsread 3 November 2026
File

ㅤ🏖️ 𝗀𝗋𝖾𝖾𝗍𝗂𝗇𝗀𝗌! 𝖨 𝖺𝗆 [𝗇𝖺𝗆𝖺 + 𝗎𝗌𝖾𝗋𝗇𝖺𝗆𝖾] 𝖿𝗋𝗈𝗆 [𝖽𝗂𝗏𝗂𝗌𝗂], 𝖻𝗋𝗂𝗇𝗀𝗂𝗇𝗀 𝗌𝗎𝗇𝗌𝗁𝗂𝗇𝖾 𝖺𝗇𝖽 𝗌𝗎𝗆𝗆𝖾𝗋 𝗏𝗂𝖻𝖾𝗌 𝗍𝗈 𝗍𝗁𝖾 Ribbon 𝖧𝗈𝗌𝗉𝗂𝗍𝖺𝗅 𝗍𝖾𝖺𝗆 𝗋𝖾𝖼𝗋𝗎𝗂𝗍𝗆𝖾𝗇𝗍! ☀️🌊 ㅤㅤㅤ𝖺𝗌 𝗍𝗁𝖾 𝗌𝗎𝗆𝗆𝖾𝗋 𝗌𝗉𝗂𝗋𝗂𝗍 𝗌𝖺𝗒𝗌 ⋮ “ 𝘓𝘦𝘵 𝘠𝘰𝘶𝘳 𝘚𝘮𝘪𝘭𝘦 𝘚𝘩𝘪𝘯𝘦 𝘉𝘳𝘪𝘨𝘩𝘵𝘦𝘳 𝘛𝘩𝘢𝘯 𝘛𝘩𝘦 𝘚𝘶𝘯—𝘔𝘢𝘬𝘦 𝘛𝘩𝘪𝘴 𝘚𝘶𝘮𝘮𝘦𝘳 𝘜𝘯𝘧𝘰𝘳𝘨𝘦𝘵𝘵𝘢𝘣𝘭𝘦! ” 🌻 ㅤ➜ ❲ ☀️ ❳ 𝖲𝗎𝗇𝗌𝗁𝗂𝗇𝖾 𝗆𝗈𝖽𝖾 𝗈𝗇! 𝖨'𝗆 𝖻𝗋𝗂𝗇𝗀𝗂𝗇𝗀 𝟣𝟢𝟢% 𝖾𝗇𝗍𝗁𝗎𝗌𝗂𝖺𝗌𝗆, 𝗐𝖺𝗋𝗆 𝗌𝗆𝗂𝗅𝖾𝗌, 𝖺𝗇𝖽 𝖿𝗋𝖾𝗌𝗁 𝖾𝗇𝖾𝗋𝗀𝗒 𝗍𝗈 𝗆𝖺𝗄𝖾 𝗈𝗎𝗋 𝗍𝖾𝖺𝗆 𝗌𝗁𝗂𝗇𝖾 𝖺𝗌 𝖻𝗋𝗂𝗀𝗁𝗍 𝖺𝗌 𝖺 𝗌𝗎𝗆𝗆𝖾𝗋 𝖽𝖺𝗒! 🍹✨ ㅤ❲ 🐚 ❳ 𝖥𝗋𝗈𝗆 𝗌𝗁𝖺𝗋𝗂𝗇𝗀 𝗐𝖺𝗋𝗆 𝗌𝗎𝗆𝗆𝖾𝗋

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

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.

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.

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

“Arsip Ribbon Hospital” (@arsiprbh), 7 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/arsiprbh.

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.