Telegram RegisterThe public register of Telegram
Telegram profile photo for gred.z ૮ ˶´ ᵕˋ ˶ა

Channel

gred.z ૮ ˶´ ᵕˋ ˶ა

@revealy

On this record: Growth · Engagement · Posts · Citations · Cite this entry

53subscribers

-3 since we began measuring on 15 August 2026

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

Register entry

Telegram ID-1001957987624
TypeChannel
Username@revealy
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 August 2026
Last confirmed live18 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/revealy

Growth

535654.515 August 2026 — 56 subscribers15 August 2026 — 56 subscribers30 August 2026 — 55 subscribers9 September 2026 — 54 subscribers18 September 2026 — 53 subscribers15 August 202618 September 2026
5 measurements spanning 34 days, net -3. 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 53–56 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 13:1653-1
9 Sept 2026, 19:3554-1
30 Aug 2026, 23:1655-1
15 Aug 2026, 09:3056no change
15 Aug 2026, 09:1856first reading

Engagement

20 posts held, back to 7 February 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 20 posts for this entry, the most recent from 5 April 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

7 Mar 2026, 17:17 UTC125 viewsread 15 August 2026

Yuyur lucuk ada @syklus datang ke sini setelah sekian lama nya

5 May 2025, 14:05 UTC293 views0 reactionsread 15 August 2026

Woww @yoopchan @yooqchan @yoogchan @yooochanchu @chuyoochana @yyonghoonjang @seonghlyeon @seonghuyeon avail to sell Kalo ada yang minat bisa chat @markauan

21 Mar 2025, 19:11 UTC301 viewsread 15 August 2026

See u @.iakesim @.jungekn @.juniahyeon @.yoowuha @.jaehyunyyung @.yoocchanchu @.nkimsooin @.jinyoune

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

Named by

Channels on the register whose posts name this channel's handle.

ALEE TAEGEON
@aLEETAEGEON · 11 postKim jiyongm
@kimjiyongm · 11 postMkim jiyong
@mkimjiyong · 11 postnkim jiyong
@nkimjiyong · 11 postSeokjunep
@seokjunep · 11 postSuzuki kaLra
@SUZUKIKAlRA · 11 postSuzukL kaira
@SUZUKlKAIRA · 21 postTAEGbEON
@TAEGbEON · 11 postTaegezon
@taegezon · 11 postTaegkeon
@TAEGkEON · 11 postTalegeon
@TAlEGEON · 11 postTAmEGEON
@TAmEGEON · 11 postVJominjae
@vjominjae · 21 postWokoju
@wokoju · 11 postYoogchan
@YOOgCHAN · 11 postYooochanchu
@YOOoCHANchu · 11 postYooqchan
@YOOqCHAN · 11 postYusa yoo
@yusayoo · 11 postYyonghoonjang
@yyonghoonjang · 11 post

Names

Channels on the register whose handles appear in this channel's posts.

Chu yoochan a
@CHUYOOCHANa · 12 postsTAbEGEON
@TAbEGEON · 12 postsTaegecon
@taegecon · 12 posts.
@taegelon · 12 postsTalegeon
@TAlEGEON · 12 postsTAmEGEON
@TAmEGEON · 12 postsYoogchan
@YOOgCHAN · 12 postsYooochanchu
@YOOoCHANchu · 12 postsYoopchan
@YOOpCHAN · 12 postsYooqchan
@YOOqCHAN · 12 postsYyonghoonjang
@yyonghoonjang · 12 postsAbang
@abasng · 21 postKeep
@kimjiyongc · 11 postKim jiyongm
@kimjiyongm · 11 postMkim jiyong
@mkimjiyong · 11 postnkim jiyong
@nkimjiyong · 11 postsemin.
@semfn · 71 postSuzuki kaLra
@SUZUKIKAlRA · 11 postSuzukL kaira
@SUZUKlKAIRA · 21 postTaegeon
@taegeron · 11 postTaegezon
@taegezon · 11 postTaegkeon
@TAEGkEON · 11 postVJominjae
@vjominjae · 21 postKeep
@vkimjiyong · 11 post

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

“gred.z ૮ ˶´ ᵕˋ ˶ა” (@revealy), 53 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/revealy.

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.