Channel
@rhenium_re
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
350subscribers
-2 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001933660417 |
|---|---|
| Type | Channel |
| Username | @rhenium_re |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/rhenium_re |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 07:23 | 350 | -2 |
| 8 Aug 2026, 06:47 | 352 | no change |
| 8 Aug 2026, 01:31 | 352 | first reading |
15 posts held, back to 21 July 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 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 5 August 2026 |
|---|---|
| Posts held | 15 (21 July 2026 – 5 August 2026) |
| Views total | 2,892 |
| Reactions total | 495 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 06:47 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.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
495 reactions across 15 posts, in 10 distinct kinds. The most used accounts for 40.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5220054611053791222 | 200 | 40.4% | |
| custom 5249399558491896781 | 111 | 22.4% | |
| custom 5388937514021059284 | 60 | 12.1% | |
| custom 5918022599501160999 | 35 | 7.07% | |
| custom 5469843204545195127 | 32 | 6.46% | |
| 🕊 | 31 | 6.26% | |
| custom 5470103256225033503 | 18 | 3.64% | |
| custom 5206519154764447446 | 5 | 1.01% | |
| custom 6224019657628587394 | 2 | 0.404% | |
| custom 5337111668373611079 | 1 | 0.202% |
Custom emoji. 9 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 15 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 495reactions 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 21 July 2026 to 5 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.
мне нужно чото показывать штобы вы не думали чт я плюю в потолок, а то как я пишу новеллу там особо не показать я рисую полноценку смотрите
custom 591802259950116099923custom 52493995584918967817custom 52065191547644474464custom 52200546110537912222custom 62240196576285873941
Signed `× ,,rheni. !¡ ꧦ✧
https://vt.tiktok.com/ZS4y1d46f/ хоть бы не теневой бан апдейт чуваки спасибо огромное кормите проста 🎎🎎
custom 522005461105379122216custom 59180225995011609994custom 53889375140210592843custom 62240196576285873941
Signed `× ,,rheni. !¡ ꧦ✧
аукцион начался ссылики добави ла
custom 522005461105379122211custom 52493995584918967811custom 53889375140210592841
Signed `× ,,rheni. !¡ ꧦ✧
аукцион тут и здес и вотут [есть 800]
custom 522005461105379122227custom 53889375140210592847custom 52493995584918967816custom 54698432045451951274custom 54701032562250335032
Signed `× ,,rheni. !¡ ꧦ✧
чуваки у сансарика гача щас посмотрите я думаю вам понравятся хорошенькие оченн я пишу новеллу соре шт контента маловато скоро будет
custom 522005461105379122218custom 52493995584918967816custom 53889375140210592846
Signed `× ,,rheni. !¡ ꧦ✧
привет клянитесь что ничего не видели
🕊31custom 524939955849189678117custom 522005461105379122213custom 54698432045451951275custom 54701032562250335033
Signed `× ,,rheni. !¡ ꧦ✧
чуваки сделать штобы спрайты проста менялись иле смешно подпрыгивали??
custom 522005461105379122215custom 52493995584918967815custom 53889375140210592843
Signed `× ,,rheni. !¡ ꧦ✧
https://t.me/rhenium_re https://t.me/rhenium_re https://t.me/rhenium_re У Рхени вчера было день рождение, прости пожалуйста, что припозднилась💔💔💔 С прошедшим тебя броо
custom 522005461105379122215custom 52493995584918967814custom 53889375140210592843
Signed `× ,,rheni. !¡ ꧦ✧
🔤🔤🔤🔤 🔤🔤🔤🔤🔤🔤🔤🔤 у мня севодня вот так чтт 🎎 🦴🦴🦴🦴🦴🦴🦴🦴🦴 🤩 - спасибо мои любимк поздравили меня с др, я за этот год ну нафармила некоторой ауры (и 56 рас сходила во вкуснаточку) 🌟🌟 [моя интернет личность составляет 80% от мнея, трети ден рожденя отмеча с вами на этом канале 😊😊] 🦴🦴🦴🦴🦴🦴🦴🦴🦴🦴🦴🦴 ➿➿➿➿➿➿➿➿➿➿➿➿➿ буду рада если репостните мои картинки итд, можно взять у менч камишку или вообще безвозмездно пожертвовать мне на лап…
custom 524939955849189678120custom 546984320454519512712custom 522005461105379122211custom 54701032562250335034
Signed `× ,,rheni. !¡ ꧦ✧
Сегодня у моей любимой художницы @rhenium_re день рождения! 🥳 Давайте напишем ей приятностей🥺 #animation@sunnerwy #gift@sunnerwy
custom 522005461105379122213custom 52493995584918967815custom 59180225995011609995
Signed `× ,,rheni. !¡ ꧦ✧
А сегодня я сделала подарок для Рени, Рехни, Стар Рин, Ванны Лим, впрочем много у нее псевдонимов сменилось, но я, как её олд(надеюсь что да), решила собрать парочку её старых ос/персонажей) 27.07.2026
custom 522005461105379122214custom 52493995584918967818custom 53889375140210592846
Signed `× ,,rheni. !¡ ꧦ✧
завтра др, ладно
custom 546984320454519512711custom 52200546110537912229custom 54701032562250335039
Signed `× ,,rheni. !¡ ꧦ✧
Showing the 12 most recent of 15 posts we hold for @rhenium_re. 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 — 266,139 of 1,481,306entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 4 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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.
“rheni1111. ✧” (@rhenium_re), 350 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/rhenium_re.
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.