Telegram RegisterThe public register of Telegram
Telegram profile photo for bio rtx

Channel

bio rtx

@bioRtx666

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

9subscribers

-1 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003527586883
TypeChannel
Username@bioRtx666
Created15 December 2025 — measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live13 October 2026
Measurements held3
Confirmed unchanged7 times, most recently 13 October 2026
On Telegramt.me/bioRtx666

Growth

9109.57 August 2026 — 10 subscribers12 August 2026 — 10 subscribers16 August 2026 — 9 subscribers7 August 202616 August 2026
3 measurements spanning 9 days, 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 9–10 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 14:149-1
12 Aug 2026, 09:4610no change
7 Aug 2026, 17:5810first reading

Engagement

2 posts held, back to 15 December 2025 — 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 2 posts for this entry, the most recent from 2 February 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
14s
Average length
14s

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

39 reactions across 1 post, in 7 distinct kinds. The most used accounts for 46.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54651749358717036121846.2%
custom 5465378667645388853717.9%
custom 5456145415671924632512.8%
custom 545438235736672703537.69%
custom 535253039910278852625.13%
custom 546559322703162818725.13%
custom 546773112431262120925.13%

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 are Telegram’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 1 of the 2 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 39 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 2 most recent posts we hold, published 15 December 2025 to 2 February 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
22
across the posts below
Posts paid on
1
of 1 we hold a reading for · 100%
Most on one post
22
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @bioRtx666. 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 2 most recent posts we hold for this entry, published 15 December 2025 to 2 February 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

2 Feb 2026, 19:43 UTC705 views39 reactions22 Starsread 12 August 2026
Video

🩸❓ 🅱️🩸🩸 my name:🩸🩸🩸 age:1️⃣6️⃣ my birthday:3️⃣1️⃣/🅾️8️⃣ ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ my proofs: ТЫК ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ my chat: ТЫК ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ my scamBase: ТЫК ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ my nickname:STRONGG050 ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ my username:@rtx_1337 ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ my discord:rtx.nishiy ⚡️⚡️⚡️⚡️⚡️⚡️ 🤩🤩🤩🤩🤩🤩🤩🤩 🤩🤩🤩🤩🤩🤩🤩🤩 🤩🤩🤩🤩🤩🤩🤩🤩 🤩🤩🤩🤩🤩🤩🤩🤩

custom 546517493587170361218custom 54653786676453888537custom 54561454156719246325custom 54543823573667270353custom 53525303991027885262custom 54655932270316281872custom 54677311243126212092

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

Mentions

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

“bio rtx” (@bioRtx666), 9 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/bioRtx666.

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.