Telegram RegisterThe public register of Telegram
Telegram profile photo for REY

Channel

REY

@REYyy_52

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

1,132subscribers

-26 since we began measuring on 10 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002973407814
TypeChannel
Username@REYyy_52
CreatedBetween 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live18 September 2026
Measurements held13
Confirmed unchanged2 times, most recently 18 September 2026
On Telegramt.me/REYyy_52

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 18 September 2026 and assigned it the closest of 31 fixed categories, at 83% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

1,1321,1581,14510 August 2026 — 1,158 subscribers10 August 2026 — 1,158 subscribers10 August 2026 — 1,156 subscribers13 August 2026 — 1,154 subscribers16 August 2026 — 1,153 subscribers19 August 2026 — 1,152 subscribers22 August 2026 — 1,148 subscribers25 August 2026 — 1,145 subscribers28 August 2026 — 1,144 subscribers31 August 2026 — 1,143 subscribers4 September 2026 — 1,141 subscribers10 September 2026 — 1,137 subscribers14 September 2026 — 1,132 subscribers10 August 202614 September 2026
13 measurements spanning 35 days, net -26. 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 1,128–1,162 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Sept 2026, 07:411,132-5
10 Sept 2026, 06:371,137-4
4 Sept 2026, 16:411,141-2
31 Aug 2026, 21:541,143-1
28 Aug 2026, 20:561,144-1
25 Aug 2026, 13:061,145-3
22 Aug 2026, 15:031,148-4
19 Aug 2026, 12:221,152-1
16 Aug 2026, 18:251,153-1
13 Aug 2026, 15:461,154-2
10 Aug 2026, 12:111,156-2
10 Aug 2026, 08:001,158no change
10 Aug 2026, 07:461,158first reading

Engagement

19 posts held, back to 30 March 2026 — 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 19 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
8s
Average length
8s

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

2,392 reactions across 19 posts, in 7 distinct kinds. The most used accounts for 41.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 528293605041348243599341.5%
custom 547202947604285638849820.8%
custom 527835003036370975633414.0%
custom 521770902203927537127711.6%
custom 54676717592746618662118.82%
custom 5215522604512736463572.38%
custom 5298813225951838934220.92%

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 19 of the 19 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 2,392 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 30 March 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.

Recent posts

8 Aug 2026, 22:57 UTC344 views101 reactionsread 10 August 2026

Posted without readable text

custom 547202947604285638872custom 546767175927466186615custom 528293605041348243510custom 52155226045127364634

8 Aug 2026, 22:53 UTC354 views95 reactionsread 10 August 2026

Posted without readable text

custom 547202947604285638859custom 521770902203927537119custom 546767175927466186613custom 52155226045127364634

22 Jul 2026, 20:26 UTC≈1,040 views150 reactionsread 10 August 2026

Posted without readable text

custom 528293605041348243584custom 546767175927466186626custom 521552260451273646321custom 52783500303637097569custom 52177090220392753715custom 54720294760428563885

22 Jul 2026, 20:25 UTC946 views127 reactionsread 10 August 2026
Photo

Photo, posted without a caption

custom 527835003036370975675custom 547202947604285638826custom 528293605041348243521custom 52177090220392753714custom 54676717592746618661

28 Jun 2026, 09:33 UTC≈1,440 views210 reactionsread 10 August 2026
Photo

первая моделька в моей жизни !!!

custom 5282936050413482435138custom 521770902203927537137custom 547202947604285638830custom 52783500303637097564custom 54676717592746618661

21 Jun 2026, 15:02 UTC≈1,510 views72 reactionsread 10 August 2026

Артик ушел на футболочки, когда будет инфо от милой заказчицы… ОБЯЗАТЕЛЬНО вам все кину!! 😩

custom 528293605041348243548custom 521770902203927537112custom 54676717592746618668custom 54720294760428563884

15 Jun 2026, 11:58 UTC≈1,710 views33 reactionsread 10 August 2026
Sticker

Sticker, posted without a caption

custom 546767175927466186623custom 54720294760428563886custom 52829360504134824354

15 Jun 2026, 11:57 UTC≈1,730 views116 reactionsread 10 August 2026

я надеюс вы помните о моем существовании, а то чет очень много ребят подумали, что я умерла и ливанули 😱

custom 528293605041348243585custom 547202947604285638821custom 546767175927466186610

15 Jun 2026, 11:42 UTC≈1,910 views189 reactionsread 10 August 2026
Photo

випочка

custom 5282936050413482435133custom 547202947604285638828custom 521770902203927537121custom 52783500303637097563custom 52155226045127364632custom 54676717592746618662

31 May 2026, 10:32 UTC≈1,670 views119 reactionsread 10 August 2026
Video

Video, posted without a caption

custom 528293605041348243574custom 547202947604285638827custom 521770902203927537111custom 52155226045127364635custom 54676717592746618662

30 May 2026, 18:32 UTC≈1,500 views192 reactionsread 10 August 2026
Photo

Photo, posted without a caption

custom 5282936050413482435111custom 527835003036370975639custom 547202947604285638824custom 52155226045127364638custom 52177090220392753716custom 54676717592746618664

29 May 2026, 10:24 UTC≈1,430 views149 reactionsread 10 August 2026
Photo

Вот еще одна випочка!!

custom 547202947604285638897custom 528293605041348243532custom 521770902203927537113custom 52155226045127364634custom 54676717592746618663

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

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.

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

“REY” (@REYyy_52), 1,132 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/REYyy_52.

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.