Telegram RegisterThe public register of Telegram

Channel

𝗜𝗡𝗙𝗢::⊱ ۫ ׅ 𝐇𝕖᷼‌𐐼‌ִv𝕖᷼‌ꪦIℽ 𝐁Iꪱs͟͟s͟͟ ♪‧₊˚

@Roleplay_InfoHB

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

189subscribers

-1 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-1002542063253
TypeChannel
Username@Roleplay_InfoHB
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 8 August 2026
On Telegramt.me/Roleplay_InfoHB

Growth

189190189.58 Aug 2026, 06:00 — 190 subscribers8 Aug 2026, 12:02 — 190 subscribers8 Aug 2026, 17:37 — 189 subscribers8 Aug 2026, 06:008 Aug 2026, 17:37
3 measurements taken within a single day, net -1. 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 189–190 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 17:37189-1
8 Aug 2026, 12:02190no change
8 Aug 2026, 06:00190first reading

Engagement

20 posts held, back to 28 June 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
119.8%
avg views ÷ 189 subscribers
Avg views / post
227
2 posts measured
Reaction rate
5.68%
reactions ÷ views · ER floor
Posts in window
2
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 1 of 2 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 18 July 2026
Posts held20 (28 June 202618 July 2026)
Views total453
Reactions total13
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 12:02 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

34 reactions across 9 posts, in 6 distinct kinds. The most used accounts for 38.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52829069777798779101338.2%
custom 53774680271953870191029.4%
custom 5303229989930431488720.6%
🥰25.88%
💋12.94%
💘12.94%

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 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 9 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 34reactions 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 28 June 2026 to 18 July 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

18 Jul 2026, 09:12 UTC229 views13 reactionsread 8 August 2026

ㅤ 🤩🤩🤩 🪽 𝒞.𝐎-𝐏𝐋𝐀𝐘𝐄𝐑𝐒 🤩🤩🤩 🌟 🤩 🤩 Данный пост предназначен для поиска, а также знакомства с соролевиками/саморолами нашей ролевой.🤩 🤩 ㅤ 🤩🤩🤩🤩🤩🤩🤩 🤩 😀😀 🔠.𝐨-𝐩𝐥𝐚𝐲𝐞𝐫𝐬: 𝅘 🤩глая ( 🤩 ) и 🤩оскресенье ( 🤩 ) 𝅘 🤩астория ( 🪻 ) и 🤩тто (🍕) 🤩 😀😀 𝒮 .𝐨𝐥𝐨 𝐫𝐨𝐥𝐞𝐩𝐥𝐚𝐲𝐞𝐫: 𝅘 Список отсутствует... 🤩 😀😀 𝒮. 𝐞𝐚𝐫𝐜𝐡:: — данный раздел предназначен для тех, кто в поиске соролевика. 𝅘 Ищем Альбедо ( 🌭 )

custom 53774680271953870195custom 52829069777798779104🥰2💋1💘1

28 Jun 2026, 18:18 UTC442 views4 reactionsread 8 August 2026

ㅤ😀😀 🤩 ℛ.𝐎𝐋𝐄𝐏𝐋𝐀𝐘𝐈𝐍𝐆 ㅤㅤㅤㅤㅤㅤ𝒫 𝐋𝐎𝐓 🤩🤩🤩 Лор нашего Рая, помогает ангелам лучше узнать это место, а также быстро адаптироваться здесь. Помни: чтобы переступить порог небес, мы потребуем от твоей души заполненную анкету, которую вы сможете повстречать в анкетнице нашей ролевой.🪽🪽🪽 🤩🤩🤩🤩🤩🤩🤩🤩 🌟 🤩сновной сюжет (click) «Пассажир зафиксирован. Память аннулирована. Ты в поезде

custom 52829069777798779102custom 53032299899304314881custom 53774680271953870191

28 Jun 2026, 18:17 UTC344 views3 reactionsread 8 August 2026

🤩🤩🤩 🤩 𝒫.𝐋𝐀𝐘𝐋𝐈𝐒𝐓 🤩🤩🤩 🤩🤩🤩 — 〰️узыка связывает сердца наших ангелов, заполняя пространство небес крепкой любовью 🎁 🤩🤩🤩🤩🤩🤩🤩🤩 ㅤ ㅤㅤㅤ𝖡𝖺𝖼𝗄 𝗍𝗈 𝗇𝖺𝗏𝗂𝗀𝖺𝗍𝗂𝗈𝗇

custom 52829069777798779101custom 53032299899304314881custom 53774680271953870191

28 Jun 2026, 18:14 UTC280 views3 reactionsread 8 August 2026

ㅤ🤩🤩🤩 🤩 𝒫.𝐀𝐓𝐄𝐍𝐓 🤩🤩🤩 🥹 💎 — 🤩т дня создания ролевой, а именно от даты 19.04.2025 года, в проекте поставлен Кодекс (патент), для защиты наших идей и трудов, которые были вложены в проект. Он запрещает использовать наших: 🥹 Баннеров и аватарок 🥹 Текстового оформлении постов 🥹 Текста в статьях 🥹 Названия проекта Если вам настолько понравилось оформление баннеров и аватарок, то за этим вы сможете обратить

custom 52829069777798779101custom 53032299899304314881custom 53774680271953870191

28 Jun 2026, 18:13 UTC207 views3 reactionsread 8 August 2026

🤩🤩🤩 𝐉𝐚𝐧𝐮𝐚𝐫𝐲: ㅤ🤩🤩апитано - 17.01 ㅤ🤩🤩урин - 25.01. 🤩🤩🤩 𝐅𝐞𝐛𝐫𝐮𝐚𝐫𝐲: ㅤ🤩🤩исиленса - 21.02. 🤩🤩🤩. 𝐌𝐚𝐫𝐜𝐡: ㅤ🤩 🤩карамучча - 27.03 🤩🤩🤩 𝐀𝐩𝐫𝐢𝐥: ㅤ🤩🤩адзуха - 08.04. ㅤ🤩🤩арянка - 09.04. 🤩🤩🤩 𝐌𝐚𝐲: ㅤ🤩 🤩🤩🤩 𝐉𝐮𝐧𝐞: ㅤ🤩 🤩🤩🤩 𝐉𝐮𝐥𝐲: ㅤ🤩🤩астория - 31.07. 🤩🤩🤩 𝐀𝐮𝐠𝐮𝐬𝐭: ㅤ🤩 🤩арталья - 07.08. ㅤ🤩🤩еликая Герта - 28.08. ㅤ🤩🤩оскресенье - 31.08. 🤩🤩🤩 𝐒𝐞𝐩𝐭𝐞𝐦𝐛𝐞𝐫: ㅤ🤩 🤩🤩🤩 𝐎𝐜𝐭𝐨𝐛𝐞𝐫: ㅤ🤩🤩тто - 02.10. ㅤ🤩🤩итлали - 05.10. ㅤ🤩 🤩скра - 11.10.

custom 52829069777798779102custom 53032299899304314881

28 Jun 2026, 18:13 UTC165 views2 reactionsread 8 August 2026

🤩🤩🤩 🤩 ℬ.𝐈𝐑𝐓𝐇𝐃𝐀𝐘𝐒 🤩🤩🤩 ㅤ🎁ㅤ— 🤩ни рождения наших ангелов, это чудесное событие на небесах. В эти дни, приданным сыпят золотом, благовествуя новорожденного ангела. 🤩🤩 🤩 такие дни, даже самые тихие поздравления, звучат громче шёпота. ㅤㅤ🤩акие события ни в коем случае нельзя пропустить, чтобы не оскорбить честь и достоинство каждого ангела. ㅤㅤ🤩🤩🤩🤩🤩🤩🤩🤩 🥹 🌟 〰️ни рождения наших ангелов:

custom 52829069777798779101custom 53774680271953870191

Showing the 12 most recent of 20 posts we hold for @Roleplay_InfoHB. 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 — 538,435 of 1,169,250entries 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.

Mentions

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

“𝗜𝗡𝗙𝗢::⊱ ۫ ׅ 𝐇𝕖᷼‌𐐼‌ִv𝕖᷼‌ꪦIℽ 𝐁Iꪱs͟͟s͟͟ ♪‧₊˚” (@Roleplay_InfoHB), 189 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/Roleplay_InfoHB.

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.