Telegram RegisterThe public register of Telegram
Telegram profile photo for ᴩоᴋᴄи нᴀ ᴄʙязи🦭

Channel

ᴩоᴋᴄи нᴀ ᴄʙязи🦭

@roksizzs

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

139subscribers

-12 since we began measuring on 15 August 2026

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

Register entry

Telegram ID-1003582802154
TypeChannel
Username@roksizzs
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 August 2026
Last confirmed live19 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/roksizzs

Growth

13915114515 August 2026 — 151 subscribers15 August 2026 — 151 subscribers25 August 2026 — 148 subscribers1 September 2026 — 146 subscribers10 September 2026 — 141 subscribers19 September 2026 — 139 subscribers15 August 202619 September 2026
6 measurements spanning 35 days, net -12. 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 137–153 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 05:00139-2
10 Sept 2026, 19:37141-5
1 Sept 2026, 12:19146-2
25 Aug 2026, 01:15148-3
15 Aug 2026, 10:15151no change
15 Aug 2026, 10:02151first reading

Engagement

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

What this channel posts

Video runtime
14s
Average length
14s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

204 reactions across 7 posts, in 7 distinct kinds. The most used accounts for 35.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53643467131275451257235.3%
custom 52084183034033871685225.5%
custom 52964118539020716924321.1%
👀167.84%
🕊115.39%
🌚94.41%
custom 519720271356940851210.49%

Custom emoji. 4 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 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 7 of the 8 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 204 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 8 most recent posts we hold, published 18 June 2026 to 13 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

13 Aug 2026, 20:17 UTC35 views13 reactionsread 15 August 2026

Как вы? Что-то последние месяцы меня на канале совсем нет( Но я стараюсь вернуться, но такой мотивации как раньше уже к сожалению нет. Постараюсь делать больше интересных постов, ведь ради них вы тут. Так что терпения, мои хорошие. Скоро надеюсь будет светлые времена на моем канале. И может вы бы хотели что-то конкретное увидеть? Напишите пожалуйста в анон или коментарии, буду рада увидеть новые идеи

custom 536434671312754512513

3 Aug 2026, 10:41 UTC86 views14 reactionsread 15 August 2026
Video

Video, posted without a caption

custom 53643467131275451258custom 52964118539020716924custom 52084183034033871682

28 Jul 2026, 12:23 UTC127 views20 reactionsread 15 August 2026
Photo

Photo, posted without a caption

🕊8custom 53643467131275451256custom 52964118539020716925custom 51972027135694085121

11 Jul 2026, 10:44 UTC213 views40 reactionsread 15 August 2026
Photo

#pov переписка (вы в отношениях) ver: Aonung

👀15custom 536434671312754512510🌚8custom 52084183034033871684custom 52964118539020716922🕊1

10 Jul 2026, 13:15 UTC184 views31 reactionsread 15 August 2026
Photo

Headcanon что бы они ответили на : "Я так хочу тебя обнять" ver: Neteyam, Lo'ak, Aonung, Rotxo Neteyam: "солнце, я тоже хочу тебя обнять. Но к сожалению мы на расстоянии(" Lo'ak: "я тоже, буду через 5 минут" Aonung: "не буди мой тактильный голод, принцесса. Скоро увидимся" Rotxo: "тоже! Вот бы увидеться)"

custom 536434671312754512516custom 52964118539020716927custom 52084183034033871684🕊2🌚1👀1

26 Jun 2026, 15:56 UTC216 views34 reactionsread 15 August 2026
Photo

#headcanon отдых с ними ver: Neteyam, Lo'ak, Aonung, Rotxo

custom 520841830340338716815custom 529641185390207169211custom 53643467131275451258

18 Jun 2026, 16:14 UTC283 views52 reactionsread 15 August 2026
Photo

#pov ночная переписка ver: Neteyam, Lo'ak, Aonung, Rotxo

custom 520841830340338716827custom 529641185390207169214custom 536434671312754512511

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

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

“ᴩоᴋᴄи нᴀ ᴄʙязи🦭” (@roksizzs), 139 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/roksizzs.

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.