Telegram RegisterThe public register of Telegram
Telegram profile photo for vamp cave | W3

Channel

vamp cave | W3

@vampcavealfa

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

112subscribers

-2 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-1002290042804
TypeChannel
Username@vampcavealfa
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live11 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/vampcavealfa

Growth

1121141137 August 2026 — 114 subscribers9 August 2026 — 114 subscribers3 September 2026 — 113 subscribers11 September 2026 — 112 subscribers7 August 202611 September 2026
4 measurements spanning 35 days, net -2. 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 112–114 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 07:41112-1
3 Sept 2026, 11:36113-1
9 Aug 2026, 06:01114no change
7 Aug 2026, 18:14114first reading

Engagement

17 posts held, back to 30 May 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 17 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

20 reactions across 6 posts, in 5 distinct kinds. The most used accounts for 45.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5368627927938251912945.0%
custom 5368378751115607139525.0%
custom 5363965831132765983315.0%
custom 5224427772524376976210.0%
custom 536634408337356996315.00%

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 are Telegram’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 6 of the 17 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 20 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 30 May 2026 to 3 August 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

3 Aug 2026, 20:14 UTC51 viewsread 9 August 2026
Photo

😜 OpenSea получил code мб еще 5 баксов получу 😐 📱TWITTER |📱GIHUB 📱YOUTUBE |📱TWITCH

7 Jul 2026, 19:34 UTC152 views3 reactionsread 9 August 2026
Photo

R.I.P. GLIDER AMBASSADORS

custom 53686279279382519123

4 Jul 2026, 21:22 UTC150 viewsread 9 August 2026
Photo

😶‍🌫️BULK раздал aura 😶‍🌫️ результаты без роли так себе но если bulk по 10$ хпхпхп😐 2 акк кореша моя рефка на + aura

23 Jun 2026, 21:37 UTC191 views3 reactionsread 9 August 2026
Photo

ПЕНСИЯ ПРИШЛА ☺️

custom 53686279279382519123

18 Jun 2026, 18:31 UTC207 viewsread 9 August 2026
Photo

🌐 BYBIT MOMENT 🌐 Не написав бы в саппорт - хрен бы увидел этот реф бонус. Так что никогда не забивайте на свои награды, даже если там $30

17 Jun 2026, 09:28 UTC174 views1 reactionsread 9 August 2026

рандомно стало не засчитывать рефов , мб из-за верифа акков .

custom 53639658311327659831

15 Jun 2026, 19:27 UTC160 views5 reactionsread 9 August 2026
Photo

🙂 Лутаем до $50 от Wallet в Telegram В ТГ-кошельке стартовала отличная промо-акция. Актуалка для всех новых пользователей либо для тех, кто не заглядывал туда больше 3 месяцев. За простой круг Wallet насыпает до $50 в токене XAUT (стейблкоин, привязанный к золоту) + 90 бонусов для открытия кейсов. Что делать?😴 1. Регаемся в Wallet ➤ [ССЫЛКА] (если попросит вериф - быстренько проходим). 2. Заводим баланс: пополняем

custom 53683787511156071395

15 Jun 2026, 18:05 UTC135 viewsread 9 August 2026
Photo

🪙 Раздали $SPCX на Pionex Вышло поменьше, чем планировал, но в любом случае - приятная халява😐 По поводу возврата депозитов за участие😳 • средства полностью вернут до 16.06.2026 23:59 (UTC+8) • если после дедлайна пусто - ПИШИТЕ ИМ СРАЗУ В САППОРТ ЖДЕМ 😴 📱TWITTER |📱GIHUB 📱YOUTUBE |📱TWITCH

14 Jun 2026, 15:39 UTC147 views5 reactionsread 9 August 2026
Photo

🪙 PIONEX $SPCX промо Остался последний шанс забрать акции SpaceX через промо для новых пользователей Pionex. У них еще есть токены для распределения. Сейчас токен $SPCX торгуется в районе 166$, а распределение будет по 135$. Профит очевиден. ПРОМО: ТЫК ДОП ПРОМО : ТЫК Регаем новые аккаунты, делаем депозит и ждем завтра. Дедлайн 20 часов . Максимальный деп 10к$. Выглядит как легкие деньги, скипать такое глупо! 📱

custom 52244277725243769762custom 53639658311327659832custom 53663440833735699631

13 Jun 2026, 13:11 UTC148 viewsread 9 August 2026
Photo

😶‍🌫️BULK раздал aura 😶‍🌫️ Еще раз повторю: это фри бабки! Депнуть от 100$ будет вообще не лишним. Если есть банк больше - депаем больше, вывести можно моментально. моя рефка на + aura

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

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

“vamp cave | W3” (@vampcavealfa), 112 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/vampcavealfa.

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.