Telegram RegisterThe public register of Telegram

Channel

𐌿᧐дʙᥲ᧘ Ꮢocksik!

@Rocksiks

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

112subscribers

+0 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1002651773129
TypeChannel
Username@Rocksiks
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 9 August 2026
On Telegramt.me/Rocksiks

Growth

1129 Aug 2026, 07:47 — 112 subscribers9 Aug 2026, 11:53 — 112 subscribers9 Aug 2026, 07:479 Aug 2026, 11:53
2 measurements taken within a single day. 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 111–113 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 11:53112no change
9 Aug 2026, 07:47112first reading

Engagement

17 posts held, back to 14 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
73.3%
avg views ÷ 112 subscribers
Avg views / post
82.1
16 posts measured
Reaction rate
8.63%
reactions ÷ views · ER floor
Posts in window
17
of 17 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 13 of 16 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 7 August 2026
Posts held17 (14 July 20267 August 2026)
Views total1,313
Reactions total96
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 07:47 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

96 reactions across 13 posts, in 8 distinct kinds. The most used accounts for 38.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3738.5%
custom 54561705498205385632627.1%
custom 54071266318001585292020.8%
👀66.25%
🔥33.13%
😎22.08%
💘11.04%
😇11.04%

Custom emoji. 2 of the rows above are 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 13 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 96reactions 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 14 July 2026 to 7 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

7 Aug 2026, 17:59 UTC30 views5 reactionsread 9 August 2026
Forwarded from @whiterevelation

ищем нам шикарных дам, пишите 🌟

3custom 54071266318001585291custom 54561705498205385631

7 Aug 2026, 12:09 UTC26 views3 reactionsread 9 August 2026
Forwarded from @penek_cosPhoto

𖦹 🌟꩜ ₊ — 🔤🔤🔤🔤🔤—- 𖦹 привет! мы ищем трех нпсишек для нашего номера по эпику на клюкво 2027 ꒰ требования:: — ответственность — платежеспособность — проживать в череповце или в ВО — 16+! 🌟🌟🌟🌟🌟🌟 ꒰ костюмы:: белые платья в греческом стиле, золотые украшения пошив не требуем! все репетиции будут проходить в череповце! ⋆ ꩜ׂׂׂׂ ׅ—- 💒 - 𖣠 —— ꒱ . . ꒰ писать в лс:: @p0nekk // @Rocksiik максимальный рт!!!!! #поиск

2custom 54561705498205385631

7 Aug 2026, 10:03 UTC24 views4 reactionsread 9 August 2026
Forwarded from @mgsakaiyoukai35Photo

🍰 С днем рождения! 🍰 Сегодня мы поздравляем нашу королеву вампиров Тилли 💜 От всех, покорённых ею душ, желаем крепкого здоровья для всей семьи, искреннего счастья каждый день, много путешествий и чтобы сбывались все мечты! 🥳

4

6 Aug 2026, 10:01 UTC68 views25 reactionsread 9 August 2026
Photo

😊||• 💙💙💬💙💙🌟`|🏠 — Мы жᴇ ᴨᴏдᴩᴏᴄᴛᴋи. 💙💙У нᴀᴄ нᴇᴛ нᴏᴩʍᴀᴧьных чуʙᴄᴛʙ, 💙💙ᴛᴏᴧьᴋᴏ ᴄᴛᴩᴀнныᴇ ɜᴀᴦᴏны. ───────🤍••ღ 🤍 ღ••🤍─────── 𝑃ℎ𝑜𝑡𝑜𝑔𝑟𝑎𝑝ℎ𝑒𝑟 - Миша 𝑟𝑒𝑡𝑜𝑢𝑐ℎ𝑖𝑛𝑔 - Миша #косплей #Венди #ɸᴏᴛᴏᴄ

custom 545617054982053856397👀6😎2custom 54071266318001585291

5 Aug 2026, 14:17 UTC33 viewsread 9 August 2026
Forwarded from @lunamoonshade

👽🧦™️🦄🛼🥑🐈™️🪀🍷 Представь, что мы делаем с тобой парный косплей. Кого будем делать и почему? 👁 Или кем ты меня видишь в пару к уже своему сделанному образу? 😇

2 Aug 2026, 22:27 UTC45 views3 reactionsread 9 August 2026
Photo

Photo, posted without a caption

custom 540712663180015852921

31 Jul 2026, 19:24 UTC58 views13 reactionsread 9 August 2026
Forwarded from @whiterevelation

сидишь, пьёшь кофе, рассуждаешь о жизни, а тут оп и проект жизнь счастливее и трава зеленее 🥰

custom 540712663180015852954custom 54561705498205385634

28 Jul 2026, 21:00 UTC60 views3 reactionsread 9 August 2026
Forwarded from @penek_cosPhoto

🔤🔤🔤🔤🔤 🔤🔤🔤🔤🔤🔤🔤 • сегодня 29 июля, а это значит, что сегодня мне исполняется 15! +🔤🤩 🔤 ₊ 🤩 。+🔤⭐️🔤 за этот год я узнала много новых чудесных людей, поэтому хочу сказать спасибо всем своим друзьям, я безумно люблю вас "° — 🫐 - 𖦹 ꩜ ₊ 🤩 𖦹 • лучший подарок для контентмейкера — это репост его работ, так что я буду очень рада каждому рт!! ꩜ ⋆ ׂׂׂׂ🤩 ׅ 𖣠 ——— ⭐️ —— ꒱ . . также !! можете меня порадовать донатиком 5536917

2💘1

24 Jul 2026, 23:18 UTC75 viewsread 9 August 2026
Forwarded from @bredni_sheldyPhoto

в связи с проблемами с Алией и нашей Эннеадой…. я покажу своей малышке кафедре сцену. Я ей обещаю 😭

23 Jul 2026, 22:53 UTC113 views3 reactionsread 9 August 2026

Дуɯᴇньᴋᴀ нᴀᴋᴏнᴇц ᴛᴏ идёᴛ ᴄᴨᴀᴛь❤️

🔥3

23 Jul 2026, 21:27 UTC169 views6 reactionsread 9 August 2026
Video message

Video message, posted without a caption

custom 54561705498205385635😇1

23 Jul 2026, 21:27 UTC71 views3 reactionsread 9 August 2026
Forwarded from @penek_cosVideo message

Video message, posted without a caption

custom 54561705498205385633

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

Citation-graph rank

Citation-graph rank — 921,798 of 1,160,990entries 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

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 3 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.

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

“𐌿᧐дʙᥲ᧘ Ꮢocksik!” (@Rocksiks), 112 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/Rocksiks.

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.