Telegram RegisterThe public register of Telegram

Channel

ENHYPEN PROJECTS.

@ENHYPENProjects

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

3subscribers

+0 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-1002132955155
TypeChannel
Username@ENHYPENProjects
DescriptionConnected to @ENHYPENProjectBot.
Created14 November 2023measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live13 August 2026
Measurements held2
On Telegramt.me/ENHYPENProjects

Growth

37 August 2026 — 3 subscribers13 August 2026 — 3 subscribers7 August 202613 August 2026
2 measurements spanning 6 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 2–4 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 11:323no change
7 Aug 2026, 03:183first reading

Engagement

8 posts held, back to 14 November 2023the 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 8 posts for this entry, the most recent from 16 November 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Videos
2
Links
1

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

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

32 reactions across 2 posts, in 11 distinct kinds. The most used accounts for 40.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤‍🔥1340.6%
🔥515.6%
412.5%
👍26.25%
👏26.25%
13.13%
🆒13.13%
🎉13.13%
💋13.13%
💘13.13%
🥰13.13%

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

Measured over the 8 most recent posts we hold, published 14 November 2023 to 16 November 2023, 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

16 Nov 2023, 07:36 UTC636 viewsread 13 August 2026

Bisa pakai 1/2 foto ya dalam 1 twb, jadi langsung send aja fotonya ke bot teman, jangan sungkan ataupun malu. Sunghoon & Jay kami enggak makan orang kok. 😁😁

16 Nov 2023, 07:22 UTC670 viewsread 13 August 2026

Kalau ada kendala di pengeditan twibbon bisa langsung ke bot ya @ENHYPENProjectBot.

15 Nov 2023, 08:13 UTC≈3,650 views31 reactionsread 13 August 2026

(𝐋𝐎𝐕𝐄 𝐋𝐎𝐒𝐓, 𝐅𝐀𝐓𝐄𝐃 𝐌𝐀𝐓𝐄 𝐎𝐁𝐒𝐂𝐔𝐑𝐄𝐃.) Therein lies the visceral truth—a narrative woven not with the delicate threads of romance but with the sinewy through the tapestry of time, their quest for ardor became a cyclical odyssey—discovering, losing, and rediscovering love, an ephemeral waltz with passion. The die cast, escape from the tendrils of a cursed existence proved an illusory endeavor, a fateful tether spanning the

❤‍🔥13🔥54👏21🎉1👍1💋1

15 Nov 2023, 08:13 UTC≈7,040 views0 reactionsread 13 August 2026
Video

𝖱𝖨𝖦𝖨𝖣 𝖤𝖬𝖡𝖱𝖠𝖢𝖤: 𝖠 𝖫𝖮𝖵𝖤'𝖲 𝖱𝖤𝖲𝖮𝖫𝖴𝖳𝖤 𝖢𝖮𝖭𝖳𝖨𝖭𝖴𝖴𝖬. "𝘋𝘈𝘙𝘒𝘕𝘌𝘚𝘚, 𝘈 𝘚𝘛𝘖𝘐𝘊 𝘈𝘓𝘓𝘠 𝘞𝘏𝘐𝘚𝘗𝘌𝘙𝘚." (Propelling into the dolorous journey ... 𓄂) A love not merely enduring, but a stalwart force transcending the very veil of death itself. In the crucible of each passionate liaison, an inevitable tragedy unfolds, casting an austere shadow upon the narrative of devotion. Will the nexus of their love, fortified by a resolute st

Showing the 8 most recent of 8 posts we hold for @ENHYPENProjects. 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 — 1,041,794 of 1,336,469entries 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

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

“ENHYPEN PROJECTS.” (@ENHYPENProjects), 3 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/ENHYPENProjects.

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.