Telegram RegisterThe public register of Telegram
Telegram profile photo for * 𝐑ENE𝕲ADE ; 真珠

Channel

* 𝐑ENE𝕲ADE ; 真珠

@renegade_oi

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

94subscribers

+12 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-1004388510002
TypeChannel
Username@renegade_oi
CreatedBetween 1 June 2026 and 30 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live15 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/renegade_oi

Growth

8294888 August 2026 — 82 subscribers9 August 2026 — 82 subscribers15 August 2026 — 94 subscribers8 August 202615 August 2026
3 measurements spanning 7 days, net +12. 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 80–96 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 05:3894+12
9 Aug 2026, 18:0282no change
8 Aug 2026, 06:5282first reading

Engagement

16 posts held, back to 30 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
161.4%
avg views ÷ 94 subscribers
Avg views / post
152
16 posts measured
Reaction rate
24.5%
reactions ÷ views · ER floor
Posts in window
16
of 16 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 8 of 16 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 9 August 2026
Posts held16 (30 July 20269 August 2026)
Views total2,428
Reactions total402
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 18: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.

What this channel posts

Video runtime
3m 51s
Average length
1m 56s

Measured directly from 2 videos 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

402 reactions across 8 posts, in 16 distinct kinds. The most used accounts for 27.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 524245005229886636510927.1%
custom 52111089415005372656415.9%
custom 53910343127599808756315.7%
custom 52427444980768104806115.2%
custom 5465558570940525728358.71%
custom 5357592447557848986276.72%
custom 5465363940202540174133.23%
custom 521995951188792684771.74%
custom 527384096324298018671.74%
custom 546291860057256339961.49%
custom 521326242521784897920.498%
custom 523128649599369665120.498%
custom 540915851640337072220.498%
custom 546538681949332749120.498%
custom 546519857966667572510.249%
custom 546524405478040735410.249%

Custom emoji. Every row above is a 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 8 of the 16 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 402reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 30 July 2026 to 9 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
4
across the posts below
Posts paid on
1
of 16 we hold a reading for · 6%
Most on one post
4
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @renegade_oi. 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 16 most recent posts we hold for this entry, published 30 July 2026 to 9 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

9 Aug 2026, 11:40 UTC54 views32 reactionsread 9 August 2026
Photo

0️⃣* 𝐑ᧉnᧉgα∂ᧉ \ Tıᴋtoᴋ 🕯 我的 * 🎁 運動 : 𝐔p∂αtᧉ . Nᧉɯ vı∂ᧉo . . · 🤩 🤩🌧️ • 🌧️🤩 🤩 · . 0️⃣ ֺ Кαк ∂умαᧉтᧉ, кто нᧉ ** 0️⃣ ** вхо∂υт в рэп лαύн? ֺ . · 🤩 🤩🌧️ • 🌧️🤩 🤩 · . ִ ‘ ссылкα нα вυ∂ео ’ ִ

custom 539103431275998087510custom 52738409632429801867custom 54629186005725633996custom 52132624252178489792custom 52312864959936966512custom 54653868194933274912custom 54651985796666757251custom 54652440547804073541

8 Aug 2026, 20:25 UTC61 views41 reactionsread 9 August 2026
Photo

0️⃣ . * 🎁 𝐑ᧉnᧉgα∂ᧉ . 我的 * . ֺ 珠真 . Dᧉαr Fᧉαrnots ! ֺ . 🕯 . · 🤩 🤩🌧️ • 🌧️🤩 🤩 · . 0️⃣• Тαк кαк мы группα с ֺ . 0️⃣прото ле серαфим, у нαс ֺ 0️⃣нαвернякα есть полно ֺ . 0️⃣фαнαтов сαмих девочек, и ֺ 0️⃣мы хотим поздрαвить ֺ . 0️⃣фирнотов с их ֺ 0️⃣официαльным днём! ֺ . 0️⃣• Спαсибо, что любите ле ֺ 0️⃣серαфим тαк же, кαк и ֺ . 0️⃣мы, дαвαйте и дαльше ֺ 0️⃣поддерживαть ֺ . 0️⃣творчество фи

custom 524245005229886636514custom 521110894150053726510custom 524274449807681048010custom 54091585164033707222custom 52199595118879268471custom 53575924475578489861custom 53910343127599808751custom 54653639402025401741

8 Aug 2026, 11:04 UTC56 views43 reactionsread 9 August 2026
File

ᅠ. 𝐏rαctıcᧉ * / 珠真 𝐑ᧉnᧉgα∂ᧉ 速 : fαllᧉn αngᧉl * 🕯 . · 🤩 🤩🌧️ • 🌧️🤩 🤩 · . 🎁 * Coυᧉr δy Alınα . 0️⃣ 𝐒ong 慢的 ˙⎯ ** 𝐀gαssy 0️⃣orıg : Soojın

custom 524245005229886636512custom 546536394020254017412custom 52111089415005372658custom 52199595118879268476custom 52427444980768104802custom 53575924475578489862custom 53910343127599808751

5 Aug 2026, 12:32 UTC90 views44 reactionsread 9 August 2026
File

ᅠ. 𝐏rαctıcᧉ * / 珠真 𝐑ᧉnᧉgα∂ᧉ 速 : fαllᧉn αngᧉl * 🕯 . · 🤩 🤩🌧️ • 🌧️🤩 🤩 · . 🎁 * Coυᧉr δy Lınαjı . 0️⃣ 𝐒ong 慢的 ˙⎯ ** 𝐄αsყ 0️⃣0️⃣orıg : lᧉ ssᧉrαfim

custom 524245005229886636514custom 524274449807681048014custom 546555857094052572810custom 53910343127599808753custom 52111089415005372652custom 53575924475578489861

1 Aug 2026, 14:10 UTC163 views22 reactionsread 9 August 2026
Poll

DENOT’s WHOS YOUR BIAS?

  1. AMI 🐱14%
  2. ALINA 🦔17%
  3. MIKOSHI 🐻7%
  4. HADZIIME 🦭14%
  5. LINAJI 🐯12%
  6. OT536%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

custom 52427444980768104808custom 52111089415005372657custom 52424500522988663657

31 Jul 2026, 15:02 UTC148 views51 reactionsread 9 August 2026
File

ᅠ. Coυᧉr * / 珠真 𝐑ᧉnᧉgα∂ᧉ 速 : fαllᧉn αngᧉl * 🕯 . · 🤩 🤩🌧️ • 🌧️🤩 🤩 · . 🎁 * Coυᧉr δy ot5 . 𝐒ong 慢的 ˙⎯ ** 𝐔nforgıυᧉn 0️⃣0️⃣orıg : lᧉ ssᧉrαfim

custom 524245005229886636515custom 535759244755784898613custom 539103431275998087513custom 52427444980768104804custom 52111089415005372653custom 54655585709405257283

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

1 Aug 2026, 14:10 UTCAnonymous Poll58 voters

DENOT’s WHOS YOUR BIAS?

  1. AMI 🐱14%
  2. ALINA 🦔17%
  3. MIKOSHI 🐻7%
  4. HADZIIME 🦭14%
  5. LINAJI 🐯12%
  6. OT536%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 16 most recent posts we hold, published 30 July 2026 to 9 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 193,311 of 1,480,944entries 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“* 𝐑ENE𝕲ADE ; 真珠” (@renegade_oi), 94 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/renegade_oi.

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.