Telegram RegisterThe public register of Telegram
Telegram profile photo for 誠実 lost prince & ferret !

Channel

誠実 lost prince & ferret !

@vrsprince

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

108subscribers

-6 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-1003283393393
TypeChannel
Username@vrsprince
CreatedBetween 1 October 2025 and 31 January 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live16 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/vrsprince

Growth

1081141117 August 2026 — 114 subscribers9 August 2026 — 114 subscribers16 August 2026 — 108 subscribers7 August 202616 August 2026
3 measurements spanning 8 days, net -6. 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 107–115 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 03:36108-6
9 Aug 2026, 06:01114no change
7 Aug 2026, 15:56114first reading

Engagement

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

Reaction mix

22 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 63.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54610440320314546021463.6%
custom 5461093729098037118836.4%

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 areTelegram’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 5 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 22reactions 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 24 February 2026 to 20 March 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

12 Mar 2026, 07:29 UTC184 viewsread 9 August 2026

кто подписал, киньте в комментарии скрины прошу

11 Mar 2026, 16:59 UTC182 viewsread 9 August 2026

подпишите петицию пожалуйста, для возвращения хисына https://www.change.org/p/allow-heeseung-to-pursue-solo-activities-without-leaving-enhypen?recruiter=1404765037&recruited_by_id=e03b1490-1c6c-11f1-9593-65f1131953b4&utm_source=share_petition&utm_campaign=starter_onboarding_share_personal&utm_medium=copylink&share_id=DCPjjdQg44

11 Mar 2026, 06:16 UTC115 viewsread 9 August 2026

до 20 марта я подготовлю какой-нибудь интересный пост к др джинни, как делала это раньше

11 Mar 2026, 06:15 UTC106 viewsread 9 August 2026

я хочу написать в контру, сказать что хочу вернуться и чтобы мне подсказали, буду держать вас в курсе

11 Mar 2026, 06:15 UTC101 viewsread 9 August 2026

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

11 Mar 2026, 06:14 UTC98 viewsread 9 August 2026

говорят, что сейчас архивы не популярны и неактуальны 😭

11 Mar 2026, 06:13 UTC97 views2 reactionsread 9 August 2026

я долго думала, очень долго, пыталась все взвесить, понять надо или не надо в июле 25 года я создала новый канал, где планировала вернуться в арх км, через какое-то время пыталась купить звезды для будущего продвижения канала, но у меня просто не выходит купить их ( даже через бот, как мне и говорили ) so я забыла об этом но тут появилась новость о амбассадорстве хвана с гесс ( понимаете какое название я планирую )

custom 54610440320314546022

11 Mar 2026, 06:06 UTC77 viewsread 9 August 2026

привет, у меня к вам серьезный разговор

10 Mar 2026, 22:04 UTC69 viewsread 9 August 2026
Forwarded from @sonhomes

тяжело будет несколько дней и мы это знаем, а может даже больше «несколько», но я верю, что мы справимся, что энджин рядом и как хорошо, что мы есть друг у друга 💞 я знаю, что тут мало людей, которые стэнят энхайпен, которые мало разбираются в происходящем, но пожалуйста выводите хэштеги везде, пишите петицию в хайб, чтобы вернули хисына я верю, что у нас получится, если мы будем действовать вместе ( хэштеги и сс на

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

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.

Mentions

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

“誠実 lost prince & ferret !” (@vrsprince), 108 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/vrsprince.

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.