Telegram RegisterThe public register of Telegram

Channel

ℜ𝔲𝔟𝔲𝔰🥀

@rubyboobi

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

380subscribers

+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-1002321597016
TypeChannel
Username@rubyboobi
Descriptionблять где я вообще 18+!!! Сидя здесь, вы подтверждаете, что вам есть 18 Ничего не пропагандирую, никого ни к чему не призываю!!
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live6 August 2026
Measurements held2
On Telegramt.me/rubyboobi

Growth

3806 Aug 2026, 08:37 — 380 subscribers6 Aug 2026, 20:18 — 380 subscribers6 Aug 2026, 08:376 Aug 2026, 20:18
2 measurements taken within a single day. 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 379–381 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Aug 2026, 20:18380no change
6 Aug 2026, 08:37380first reading

Engagement

15 posts held, back to 12 May 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.

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

What this channel posts

Photos
430
Videos
2
Links
38

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

Reaction mix

332 reactions across 15 posts, in 2 distinct kinds. The most used accounts for 73.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 522453454541135629024373.2%
custom 53125059725335265098926.8%

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 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 332reactions 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 12 May 2026 to 12 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

12 Jul 2026, 00:50 UTC215 views33 reactionsread 6 August 2026
Photo

у меня ничего нет, мне нечем вас кормить есть тестамент, ешьте его

custom 522453454541135629033

12 Jul 2026, 00:37 UTC175 views7 reactionsread 6 August 2026
Forwarded from @p3lyaPhoto

френдли фаер для рубуса @rubyboobi покорми мышу

custom 52245345454113562907

12 Jul 2026, 00:37 UTC168 views8 reactionsread 6 August 2026

яяя я ряльно в восторге real тоже хочу на артфайт рисовать, но я немощ😭😭

custom 52245345454113562908

29 Jun 2026, 03:38 UTC442 views40 reactionsread 6 August 2026
Photo

омг это что спойлер в #OVERWATCHEROZINE ....🥀🕯️

custom 522453454541135629040

22 Jun 2026, 19:25 UTC354 views10 reactionsread 6 August 2026

СМОТРИТЕ СМОТРИИИТЕЕЕ

custom 53125059725335265096custom 52245345454113562904

22 Jun 2026, 19:25 UTC407 views36 reactionsread 6 August 2026
Forwarded from @kiriuwoPhoto

ДАА закончила ураа гифтик скетч для крутышки и её супер пупер мальчика мыш

custom 522453454541135629022custom 531250597253352650914

16 Jun 2026, 12:54 UTC287 views5 reactionsread 6 August 2026

я умру от количества ивентов в своей жизни, но я просто невероятно сильно рада боже мой

custom 52245345454113562905

16 Jun 2026, 12:54 UTC403 views5 reactionsread 6 August 2026
Forwarded from @xlov_zinePhoto

♟ Фигуры расставлены: Знакомьтесь с авторами зина XLOV! 🖤 Партия началась! С трепетом представляем вам тех, кто воплотит историю XLOV в жизнь. • Формат: печатная книга А5 + набор эксклюзивного мерча • Концепт: вся история XLOV от дебюта до сегодня (все эры и дуо!) • Рейтинг: 12+ 🌷Художники: 🔣тимьян 🔣user safael 🔣arkashamn 🔣mirai_devil 🔣Муниликса 🔣rimkkn 🔣Yori Maru 🔣ёкмакарёк 🔣Стейн 🔣alueella 🔣Fairyhell 🔣eustace 🔣m

custom 52245345454113562904custom 53125059725335265091

15 Jun 2026, 01:22 UTC508 views44 reactionsread 6 August 2026
Photo

с прошедшим днём рожденя мою любимую женщину @axxiommas 😃😃😃

custom 522453454541135629025custom 531250597253352650919

13 Jun 2026, 10:42 UTC373 views55 reactionsread 6 August 2026
Photo

Ну? Ещё надо? Фуллы в комментах🤫🤫

custom 522453454541135629037custom 531250597253352650918

5 Jun 2026, 20:32 UTC460 views18 reactionsread 6 August 2026

Мне ебейше нужен новый ссдшник, чтоб я могла и дальше рисовать, а то мой комп уже нихуя не вывозит клип студио🥹🥹🥹

custom 531250597253352650918

5 Jun 2026, 18:28 UTC≈1,190 views22 reactionsread 6 August 2026
Photo

🤩 🤩🤩🤩🤩 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 🤩 🤩🤩🤩🤩🤩🤩🤩🤩 🤍 ℌ𝔞𝔩𝔣: 3️⃣0️⃣0️⃣0️⃣🤩 🤍 𝔉𝔲𝔩𝔩 𝔟𝔬𝔡𝔶: 4️⃣0️⃣0️⃣0️⃣🤩 🤍🤍 Занято слотов: ℌ𝔞𝔩𝔣: 0/3 𝔉𝔲𝔩𝔩 𝔟𝔬𝔡𝔶: 0/2 🎀🎀🎀✝️🎀🎀🎀 🤩𝔇𝔢𝔞𝔡𝔩𝔦𝔫𝔢: 2 месяца 🤩𝔒𝔭𝔩𝔞𝔱𝔞: 50% до начала работы, 50% после скетча Писать в лс мне: @malinka_trap

custom 522453454541135629022

Showing the 12 most recent of 15 posts we hold for @rubyboobi. 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 — 160,050 of 1,151,006entries 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 34 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“ℜ𝔲𝔟𝔲𝔰🥀” (@rubyboobi), 380 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/rubyboobi.

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.