Channel

WKND 𝘽𝙀𝙍𝙑𝙎𝙆𝙔𝙀 𝙁𝙈

@berv_skye

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

2,526subscribers

+122 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID	-1002512364548
Type	Channel
Username	@berv_skye
Created	31 March 2025 — measured — dated from the channel’s first post
First recorded	6 August 2026
Last confirmed live	6 September 2026
Measurements held	12
Confirmed unchanged	1 time, most recently 6 September 2026
On Telegram	t.me/berv_skye

Growth

12 measurements spanning 30 days, net +122. 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,353–2,558 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
6 Sept 2026, 08:19	2,526	-8
2 Sept 2026, 01:47	2,534	+32
30 Aug 2026, 09:26	2,502	+33
27 Aug 2026, 06:08	2,469	+44
23 Aug 2026, 23:47	2,425	-32
20 Aug 2026, 03:45	2,457	+44
16 Aug 2026, 19:48	2,413	+22
13 Aug 2026, 16:06	2,391	+14
10 Aug 2026, 10:40	2,377	-15
7 Aug 2026, 03:10	2,392	-12
6 Aug 2026, 22:30	2,404	no change
6 Aug 2026, 22:18	2,404	first reading

Engagement

10 posts held, back to 31 March 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 2 pages 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 10 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

3 Aug 2026, 11:40 UTCviews —

Channel name was changed to «REST 𝐁̲𝐄̍𝐑̲𝐕̶𝐒̷𝐊̷𝐘̸𝐄̍ 𝐅̶𝐌̍»

3 Aug 2026, 11:39 UTC117 viewsread 7 August 2026

Уходим в большой рест ребят, извиняемся, сейчас тяжёлые времена, вернёмся как только сможем

30 Jul 2026, 08:31 UTC362 viewsread 7 August 2026

File

Союзов мне 😽 Папка вз/рп 2:2 - 13:13 Правила 📤 связь

28 Jul 2026, 16:04 UTC407 viewsread 7 August 2026

Скз чат набор закрыт

17 Jul 2026, 20:49 UTC≈1,060 viewsread 7 August 2026

Photo

︎1. подписаться на канал 2. прочитать правила 3. подать заявку в один из чатов

30 Jun 2026, 23:06 UTC≈2,100 viewsread 7 August 2026

File

🌟BERVSKYE в поиске администрации 💬 🌟🌟🌟🌟🌟🌟🌟🌟 Общий чат Админ по активу 0/2 Админ по видео 0/1 Женский чат Админ по видео 0/1 Админ по активу 0/2 Скз чат Админ по чату 1/2 Админ по активу 0/2 Бтс чат Вся администрация Мужской чат Админ по чату 1/2 Админ по активу 0/2 Админ по видео 0/1 Обращаться и по вопросам: @b

30 Jun 2026, 22:57 UTC≈1,390 viewsread 7 August 2026

Sticker

Sticker, posted without a caption

30 Jun 2026, 22:56 UTC≈1,430 viewsread 7 August 2026

Sticker

Sticker, posted without a caption

30 Jun 2026, 22:55 UTC≈1,530 viewsread 7 August 2026

Photo

🔗🔗🔗🔗🔗🔗🔗🔗🔗🔗 🤩RULES 🎇ADMINISTRATION 🌟 ➕ PATENT 🎯TIK TOK ✅BOT 👍 ARCHIVE 🌟 UNIONS 🎁 FAMILY

31 Mar 2025, 04:04 UTCviews —

Channel created

Showing the 10 most recent of 10 posts we hold for @berv_skye. 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Архивы бервских
@bervskye_arch · 210 posts

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

Named by 30 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. The 23 listed below are the most frequent namers; the rest are counted above but not each listed.

Named by

Channels on the register whose posts name this channel's handle.

Names

Channels on the register whose handles appear in this channel's posts.

Info
@bervsky · 1603 posts Архивы бервских
@bervskye_arch · 21 post

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

“WKND 𝘽𝙀𝙍𝙑𝙎𝙆𝙔𝙀 𝙁𝙈” (@berv_skye), 2,526 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/berv_skye.

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.