Telegram RegisterThe public register of Telegram
Telegram profile photo for reynybead

Channel

reynybead

@reynyxxlez

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

121subscribers

+0 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1001626366709
TypeChannel
Username@reynyxxlez
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live17 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/reynyxxlez

Growth

121124122.512 August 2026 — 121 subscribers12 August 2026 — 121 subscribers18 August 2026 — 124 subscribers25 August 2026 — 123 subscribers31 August 2026 — 122 subscribers17 September 2026 — 121 subscribers12 August 202617 September 2026
6 measurements spanning 36 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 121–124 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 05:40121-1
31 Aug 2026, 05:04122-1
25 Aug 2026, 01:25123-1
18 Aug 2026, 15:14124+3
12 Aug 2026, 03:00121no change
12 Aug 2026, 02:48121first reading

Engagement

16 posts held, back to 19 February 2024the 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 16 posts for this entry, the most recent from 29 July 2024. An engagement rate over an empty window would be a number about nothing.

Reaction mix

156 reactions across 12 posts, in 10 distinct kinds. The most used accounts for 44.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💘7044.9%
🍓4126.3%
💋106.41%
🦄95.77%
👾85.13%
🍾74.49%
63.85%
🕊31.92%
🎃10.641%
👀10.641%

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 12 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 156 reactions 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 19 February 2024 to 29 July 2024, 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

29 Jul 2024, 10:14 UTC743 views5 reactionsread 12 August 2026

я всё ещё ждуу

💘4🎃1

Signed `'токсикк

4 May 2024, 13:24 UTC≈1,060 views12 reactionsread 12 August 2026

пните её, чтобы показала его уже.

🍓6💘42

Signed - ̗̀toxic queen.(7.03).

8 Apr 2024, 19:15 UTC≈1,240 views11 reactionsread 12 August 2026
Photo

И да, это опять букетик, много писать не буду но хочу сказать что мне очень понравилось их делать 🎀 Так что жду в коментариях какой букетик красивее, первый или второй?)😇

💋9💘2

Signed Гренус < ꒱

8 Apr 2024, 19:04 UTC766 views7 reactionsread 12 August 2026
Photo

😈😈😈

👾5💘2

Signed Гренус < ꒱

7 Apr 2024, 19:56 UTC680 views4 reactionsread 12 August 2026

Ставим много 🍓

💘4

Signed Гренус < ꒱

7 Apr 2024, 19:55 UTC669 views32 reactionsread 12 August 2026
Photo

Всем приветик!🌷 Хотела б показать вам роботку которую доделала только что🎀 И это мини букетик из бисера и проволки😘 Делала его +- 1-2 часа😶 Как по мне вышло прям эстетик🎀 Идейку на этот букетик увидела в Пинтерест и чота захотелось повторить)😅 Жду много комментариев и реакций на этот постик🤩

🍓24💘53

Signed Гренус < ꒱

27 Mar 2024, 19:26 UTC762 views16 reactionsread 12 August 2026

Гоу вернём актив, поставим 10 💘

💘11🍾5

Signed Гренус < ꒱

27 Mar 2024, 19:23 UTC742 views43 reactionsread 12 August 2026
Photo

Пупупу...🤔🤔🤔

💘32🦄9👾2

Signed Гренус < ꒱

15 Mar 2024, 19:37 UTC828 views5 reactionsread 12 August 2026

НО. она часто появляется на канале @starsbead , где является админом. так что если вы так сильно её любите, но подписывайтесь на канальчик.💕

💘5

Signed - ̗̀toxic queen.(7.03).

15 Mar 2024, 19:35 UTC683 views1 reactionsread 12 August 2026

она не захотела писать пост, так что я за нее.

1

Signed - ̗̀toxic queen.(7.03).

15 Mar 2024, 19:35 UTC629 viewsread 12 August 2026

ребят, канал закрыт, т.к. гренус ушла из бк. 🤷‍♂️ у нее нет желания плести, выгорание + пошли жесткие отписки. нет таких, для кого можно вести канал.😠 она устала. если захочет (бомбанет), то канал будет удален. просьба не ебать ей мозги. можете красиво ее проводить в коммах.🙂

Signed - ̗̀toxic queen.(7.03).

15 Mar 2024, 18:52 UTCviews —

Channel name was changed to «😶‍🌫️rensbead🤍🪿(закрыто йоу)»

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

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.

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.

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

“reynybead” (@reynyxxlez), 121 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/reynyxxlez.

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.