Telegram RegisterThe public register of Telegram
Telegram profile photo for Rocksnow Client

Channel

Rocksnow Client

@rocksnowclient

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

1,967subscribers

+24 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1003118086822
TypeChannel
Username@rocksnowclient
CreatedBetween 1 September 2025 and 30 November 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live18 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 18 August 2026
On Telegramt.me/rocksnowclient

Growth

1,9431,9671,95510 August 2026 — 1,943 subscribers11 August 2026 — 1,946 subscribers15 August 2026 — 1,952 subscribers18 August 2026 — 1,967 subscribers10 August 202618 August 2026
4 measurements spanning 7 days, net +24. 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,939–1,971 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Aug 2026, 01:071,967+15
15 Aug 2026, 00:041,952+6
11 Aug 2026, 06:141,946+3
10 Aug 2026, 15:311,943first reading

Engagement

20 posts held, back to 6 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
111.4%
avg views ÷ 1,967 subscribers
Avg views / post
2,190
5 posts measured
Reaction rate
0.165%
reactions ÷ views · ER floor
Posts in window
6
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 4 of 5 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held20 (6 July 20266 August 2026)
Views total10,952
Reactions total14
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 15:31 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

55 reactions across 15 posts, in 6 distinct kinds. The most used accounts for 63.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3563.6%
❤‍🔥916.4%
🤡59.09%
🆒35.45%
🤮23.64%
🎉11.82%

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

Measured over the 20 most recent posts we hold, published 6 July 2026 to 6 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

6 Aug 2026, 13:54 UTC662 views1 reactionsread 10 August 2026

На 2000 подписчиков релизаем обнову Наш чат Дев-логи Ссылка для друга

1

Signed скальнаяпещера1337

25 Jul 2026, 22:25 UTC≈2,470 viewsread 10 August 2026

Всем привет! В нашем комьюнити появилось сообщество RuVisuals☀️ 🖥 В этом сообществе будут публиковаться новости о состоящих в нем визуалах - новости, важные события в комьюнити и многое другое 🔗 RuVisuals

Signed скальнаяпещера1337

23 Jul 2026, 11:30 UTC≈2,560 views4 reactionsread 10 August 2026
Forwarded from @rockdevlogs

Обнова почти готова! Нам осталось купить хостинг, протестить баги, пофиксить баги что найдем, после этого выпускаем обнову и уходим в разработку 3.0, скорее всего еще будет Rocksnow 2.1

🆒3❤‍🔥1

Signed скальнаяпещера1337

20 Jul 2026, 16:03 UTC≈2,730 views3 reactionsread 10 August 2026

Сегодня весь день писал разным серверам по поводу разрешения визуалов, GulPvP, SlimeWorld, FakeTime одобрили визуалы А вот по поводу HOWEMINE, ASTRUMMC могу сказать так, я че ебу как там подавать на разрешение, там буквально этого нету, у Astrum был список запрещенных модов/визуалов, это ладно, по списку вырезал, но у поддержки не спрашивал, на счет банов сказать не могу, HOWEMINE я даже правил не нашел, вырезал вс

3

Signed скальнаяпещера1337

20 Jul 2026, 08:42 UTC≈2,530 views6 reactionsread 10 August 2026

Накидайте айпи серверов, где бы вы хотели чтобы визуалы были разрешены (кроме фт)

2🤡2🤮2

Signed скальнаяпещера1337

18 Jul 2026, 18:16 UTC≈2,550 views5 reactionsread 10 August 2026

Напоминаю, после следующего обновления будет долгий перерыв в связи с разработкой 3.0, так что если вы заметили какой-то баг, скажите об этом (в версии 1.21.11 куча багов, мы знаем, на данный момент пофиксили уже вроде все)

❤‍🔥3🤡2

Signed скальнаяпещера1337

18 Jul 2026, 08:45 UTC≈2,470 views5 reactionsread 10 August 2026

после обновы Rocksnow 2.0 получится так, что Rocksnow 2.0 - лучшие фри визуалы на 1.21.4-1.21.11 и по визуалам, и по функционалу (повторюсь, обнова выйдет на 1.21.11, затем все с обновы перенесу обратно на 1.21.4)

4🤡1

Signed скальнаяпещера1337

16 Jul 2026, 09:36 UTC≈2,600 viewsread 10 August 2026

⚠️ Открыт набор в Media клиента ❓ Что требуется: 200 просмотров в TikTok/YouTube на тематику Minecraft 🔗 Подать заявку

Signed фризикс

15 Jul 2026, 20:10 UTC≈2,460 views1 reactionsread 10 August 2026

Короче решил сделать так: Сделаю в этом обновлении все, что хотел когда либо реализовать, добавлю туда обнову связанную с индикацией юзеров, после чего фулл уход в разработку 3.0, поверьте, обновление будет сочным

❤‍🔥1

Signed скальнаяпещера1337

13 Jul 2026, 12:11 UTC≈2,890 views6 reactionsread 10 August 2026

Вопросы которые часто спрашивают: 1. Где скачать 1.21.4? • Тут 2. Где скачать 1.21.11? • Тут 3. Где скачать версию под HolyWorld чтобы не банили? • Тут 4. Как убрать 2 экран? • Удалить мод Immediately Fast 5. В чем смысл делать обычную "пасту рокстара"? • Мы не паста рокстара, мы не отрицаем что написаны на базе летнего рокстара, но мы поменяли почти всю базу подогнав ее вид под новый рокстара, подробнее расписал тут

6

Signed rockcave1337

11 Jul 2026, 15:54 UTC≈2,510 views2 reactionsread 10 August 2026

Следующее обновление будет на версии 1.21.11 (фикс всех багов + куча функций), в этом обновлении фикса индикации не будет, а вот в обновлении что будет после этого обновления будет кое-что интересное)

2

Signed rockcave1337

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

9 Jul 2026, 21:31 UTCFinal Results220 voters

Прекращаем поддержку 1.21.4?

  1. Да, кому вообще нужна 1.21.437%
  2. Неет, мне 1.21.4 нравится больше чем 1.21.1163%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 6 July 2026 to 6 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 1,266,248 of 1,549,704entries 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

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

Named by 1 registered channel — 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.

Named by

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

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

“Rocksnow Client” (@rocksnowclient), 1,967 subscribers as measured 18 August 2026. Telegram Register, tgregister.com/channel/rocksnowclient.

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.