Telegram RegisterThe public register of Telegram
Telegram profile photo for evnne more

Channel

evnne more

@ennvecore

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

52subscribers

+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-1001827855609
TypeChannel
Username@ennvecore
Descriptionлюблю ивен основной канал — https://t.me/evnneparkbin
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live21 August 2026
Measurements held2
On Telegramt.me/ennvecore

Growth

527 August 2026 — 52 subscribers10 August 2026 — 52 subscribers7 August 202610 August 2026
2 measurements spanning 3 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 51–53 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 10:0252no change
7 Aug 2026, 03:1652first reading

Engagement

18 posts held, back to 11 February 2025the 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 18 posts for this entry, the most recent from 3 March 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
674
Videos
116
Links
41

Lifetime counters from Telegram’s own channel header, read 10 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
1m 13s
Average length
12s

Measured directly from 6 videos 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

254 reactions across 18 posts, in 6 distinct kinds. The most used accounts for 51.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
13051.2%
💘7529.5%
💋3011.8%
🔥114.33%
❤‍🔥62.36%
👍20.787%

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

Measured over the 18 most recent posts we hold, published 11 February 2025 to 3 March 2025, 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

3 Mar 2025, 12:02 UTC250 views23 reactionsread 10 August 2026

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

12💘6🔥3💋2

3 Mar 2025, 12:02 UTC243 views20 reactionsread 10 August 2026
Video

без комментариев

12💘4💋2🔥2

1 Mar 2025, 08:19 UTC200 views12 reactionsread 10 August 2026
Forwarded from @evnneparkbinPhoto

🎁 birthday present from hanbin 🎀 to open it click below ⤵️

8💘4

1 Mar 2025, 08:18 UTC131 views5 reactionsread 10 August 2026

после дршки ханбина точно на рест

💘5

1 Mar 2025, 08:16 UTC123 views11 reactionsread 10 August 2026

я написала что ханбин тайм уходит на рест и сделала постов больше чем до реста

6💘3👍2

1 Mar 2025, 07:26 UTC112 views9 reactionsread 10 August 2026
Video

Video, posted without a caption

5💋2💘2

1 Mar 2025, 07:25 UTC97 views10 reactionsread 10 August 2026
Photo

Photo, posted without a caption

6💋2💘2

1 Mar 2025, 07:24 UTC70 views15 reactionsread 10 August 2026
Photo

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

10💋3💘2

21 Feb 2025, 10:04 UTC86 views16 reactionsread 10 August 2026
Video

🌙 : наши энви!! очень много людей пришли поддержать нас сегодня, и многие наверняка смотрят из дома. спасибо, что всегда поддерживаете нас и спасибо за то, что подарили нам первое место. я люблю вас всегда

11💘5

21 Feb 2025, 10:01 UTC59 views16 reactionsread 10 August 2026
Forwarded from @evnneparkbinVideo

ХАТ МЕСС ФЕРСТ ВИН

11💘3🔥2

20 Feb 2025, 12:02 UTC68 views16 reactionsread 10 August 2026
Forwarded from @evnneparkbinVideo

сепарация отменяется ивен всегда будут вместе

12💘4

Showing the 12 most recent of 18 posts we hold for @ennvecore. 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 — 331,740 of 1,583,249entries 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.

Republishes

Channels on the register whose posts this channel has forwarded.

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

“evnne more” (@ennvecore), 52 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/ennvecore.

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.