Telegram RegisterThe public register of Telegram
Telegram profile photo for Prise

Channel

Prise

@Vp_here

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

2subscribers

+1 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1003975602102
TypeChannel
Username@Vp_here
Created9 July 2026measured — dated from the channel’s first post
First recorded15 August 2026
Last confirmed live4 September 2026
Measurements held3
Confirmed unchanged3 times, most recently 4 September 2026
On Telegramt.me/Vp_here

Growth

121.511 August 2026 — 1 subscribers15 August 2026 — 1 subscribers19 August 2026 — 2 subscribers11 August 202619 August 2026
3 measurements spanning 8 days, net +1. 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–2 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Aug 2026, 17:072+1
15 Aug 2026, 09:151no change
11 Aug 2026, 23:171first reading

Engagement

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

Recent posts

27 Jul 2026, 10:57 UTC14 viewsread 15 August 2026
Photo

Тада! Барбара здесь~ Доверь исцеление мне, я тебя не разочарую! Любишь Барбару?? Тогда скорее заходи в собор Фавония! Она тебя уже ждёт…

27 Jul 2026, 10:57 UTC14 viewsread 15 August 2026

Правила вп с @BarbaraTFDream Вп 0+ со всеми 01. Вп держится 6 часов 02. Не перекрывать вп 30 минут с обеих сторон 03. Могу отказать без указания причины 04. По поводу вп писать под этим постом, при желании можно указать, что именно ртшить 05. Ртшить пост ниже DNI: хейтеры Барбары/хейт каналы/рейд каналы/каналы связанные с политикой/хейтеры Мондштадта/ каналы с 18+ контентом/безкредитники

22 Jul 2026, 19:38 UTC989 viewsread 15 August 2026
Photo

"Там, где сияют звезды, повсюду таится зло!" Под сенью величественного небоскреба произнеси свои последние слова — *три выстрела* — победитель определен. Мои методы космического ниндзюцу постоянно меняются. В следующий раз тебе повезет больше... в следующей жизни. Раппа создала свой блог! Скорее заходи

22 Jul 2026, 19:32 UTC17 viewsread 15 August 2026

Правила вп с @Rappaninja Вп 0+ со всеми 01. Вп держится 6 часов 02. Не перекрывать вп 10-30 минут с обеих сторон 03. Могу отказать без указания причины 04. По поводу вп писать под этим постом, при желании можно указать, что именно ртшить 05. Ртшить пост ниже DNI: хейтеры Раппы/хейт каналы/рейд каналы/каналы связанные с политикой/хейтеры Пенаконии/ каналы с 18+ контентом/безкредитники

9 Jul 2026, 18:56 UTC490 viewsread 15 August 2026
Photo

🤩: Пока сверчок летит на пламя… жизнь стремится к смерти. Светлячок (также известная как Сэм) — полицейская в городе Лавендор, который погряз в беззаконии и несправедливости… Хотите последить за её жизнью? Тогда добро пожаловать. ❌❌❌Cr: selvha_ on X

9 Jul 2026, 18:54 UTC29 viewsread 15 August 2026

Правила вп с @FireflyLavendor Вп 0+ с каналами связанными с хойо-сетками, вп 20+ с остальными (со временем будет увеличиваться) 01. Вп держится 6 часов 02. Не перекрывать вп 30 минут с обеих сторон 03. Могу отказать без указания причины 04. По поводу вп писать под этим постом, при желании можно указать, что именно ртшить 05. Ртшить пост ниже DNI: хейтеры Светлячка/хейт каналы/рейд каналы/каналы связанные с политик

Showing the 11 most recent of 11 posts we hold for @Vp_here. 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 2 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.

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

“Prise” (@Vp_here), 2 subscribers as measured 19 August 2026. Telegram Register, tgregister.com/channel/Vp_here.

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.