Telegram RegisterThe public register of Telegram

Channel

рена~лия

@renalliaa

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

151subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002580991832
TypeChannel
Username@renalliaa
Descriptionлс @renalliaaa анонимка http://t.me/anonaskbot?start=paksjedkxh
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 held2
On Telegramt.me/renalliaa

Growth

1516 August 2026 — 151 subscribers8 August 2026 — 151 subscribers6 August 20268 August 2026
2 measurements spanning 2 days. 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 150–152 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 19:32151no change
6 Aug 2026, 21:46151first reading

Engagement

12 posts held, back to 31 July 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
79.1%
avg views ÷ 151 subscribers
Avg views / post
119
11 posts measured
Reaction rate
12.9%
reactions ÷ views · ER floor
Posts in window
12
of 12 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 10 of 11 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 8 August 2026
Posts held12 (31 July 20268 August 2026)
Views total1,314
Reactions total164
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 19:32 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
417
Videos
58
Links
44

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

Video runtime
5s
Average length
5s

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.

Reaction mix

164 reactions across 10 posts, in 14 distinct kinds. The most used accounts for 20.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3320.1%
❤‍🔥3320.1%
💋3320.1%
🙏169.76%
🥰148.54%
🔥84.88%
custom 542915677319178360563.66%
custom 534816654053137434753.05%
💘53.05%
🍓31.83%
🤗31.83%
custom 535057998573420813421.22%
🎉21.22%
custom 539106643911538045710.61%

Custom emoji. 4 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 10 of the 12 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 164reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 12 most recent posts we hold, published 31 July 2026 to 8 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.

Telegram Stars

Stars received
66
across the posts below
Posts paid on
3
of 11 we hold a reading for · 27%
Most on one post
62
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @renalliaa. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 12 most recent posts we hold for this entry, published 31 July 2026 to 8 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

8 Aug 2026, 09:56 UTC42 views7 reactionsread 8 August 2026

спасибо большое за звездочки 🥹🥹

custom 54291567731917836053❤‍🔥2🥰2

7 Aug 2026, 21:01 UTC395 views53 reactions62 Starsread 8 August 2026
Photo

с хеппи бездей меня ✌🏻 как сказала моя бести: я потеряла хайповую единичку в возрасте💔 очень сильно не люблю писать огромные тексты, так что краткость сестра таланта за последний год очень многое изменилось в лучшую сторону, я встала на путь той жизни, о которой мечтала многие годы и повстречала множество прекрасных людей надеюсь, слеющий год я проведу ещё лучше~ 😊ну и не нарушаем традиции: самый лучший подарок для

💋1815❤‍🔥13💘3🎉2🍓1🤗1

7 Aug 2026, 13:20 UTC76 views5 reactionsread 8 August 2026

вот как

💋31custom 53481665405313743471

7 Aug 2026, 11:16 UTC77 views21 reactions1 Starread 8 August 2026
Photo

а вы знали, что я не пинаю хуи🤔 (не факт)

🙏8❤‍🔥5💋3🤗2🍓1🔥1custom 54291567731917836051

5 Aug 2026, 09:04 UTC74 views14 reactionsread 8 August 2026
Forwarded from @nuna_phPhoto

От такие мы вчера были после фотосика с Джун и Реной 🙂 (А сегодня новый день лабного марафона, с чем я себя и не поздравляю)

❤‍🔥4🔥3custom 53481665405313743473💋2🙏2

4 Aug 2026, 20:09 UTC85 views15 reactionsread 8 August 2026
Forwarded from @JunieSongrythmPhoto

Сегодня снимали кое-что классное с Нуной, но постик с бэками будет позже. Меня наказали и поставили в угол, поэтому сначала нужно, собственно, отбыть наказание 😭 За смешнявки спасибо Рене ❤️

❤‍🔥6🥰4🔥3🙏2

3 Aug 2026, 17:55 UTC44 viewsread 8 August 2026
Forwarded from @lunamoonshade

👽🧦™️🦄🛼🥑🐈™️🪀🍷 Представь, что мы делаем с тобой парный косплей. Кого будем делать и почему? 👁 Или кем ты меня видишь в пару к уже своему сделанному образу? 😇

1 Aug 2026, 17:58 UTC145 views30 reactions3 Starsread 8 August 2026
Photo

🤩🤩🤩🤩🤩 -Нᴏ..ᴇᴄᴧи ʙᴇᴩᴀ ʙ Бᴏᴦᴀ - В ᴄʙᴏᴇᴦᴏ Бᴏᴦᴀ, ʙ ᴄʙᴏю Вᴄᴇᴧᴇнную 🤩🤩🤩🤩🤩 🖤🖤🖤 🖤🖤🖤 🖤🖤🖤 🤩ph #alienstage #sua

11🥰6❤‍🔥3💋2💘2custom 54291567731917836052🍓1🔥1

31 Jul 2026, 20:40 UTC126 views3 reactionsread 8 August 2026
Forwarded from @nwcosplayhelpPhoto

« ПК » : Помощь Косплеерам 🥰 💋 Репостните этот пост, а подписчики вашего тгк пусть скажут. . . 1) какой ваш косплей им нравится больше всего 2) персонаж, косплей на которого они очень ждут 3) косплеер, с которым хотят видеть коллаб

💋2🙏1

31 Jul 2026, 05:46 UTC117 views1 reactionsread 8 August 2026

для понимания всего ужаса скажу, что полностью на эти узоры ушло порядка 70-75 часов 🥰🥰 а ещё я трижды отпарывала весь бисер, ибо мне не нравилось как он пришит

🙏1

31 Jul 2026, 05:43 UTC133 views15 reactionsread 8 August 2026
Photo

я ненавижу эти рукава всей душой😱 осталось доклеить стразы на втором и этот ад официально закончится мне ахуеть как обидно, что в итоге половину бисера даже не видно🖕

6💋3🥰2🙏1custom 53481665405313743471custom 53505799857342081341custom 53910664391153804571

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 79,747 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.

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

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

“рена~лия” (@renalliaa), 151 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/renalliaa.

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.