Telegram RegisterThe public register of Telegram

Channel

🔒`!ce cr3am k1o しろい

@c3rk1o

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

83subscribers

-1 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-1003054622772
TypeChannel
Username@c3rk1o
CreatedBetween 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/c3rk1o

Growth

838483.57 August 2026 — 84 subscribers9 August 2026 — 84 subscribers14 August 2026 — 83 subscribers7 August 202614 August 2026
3 measurements spanning 7 days, net -1. 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 83–84 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 09:4783-1
9 Aug 2026, 17:3184no change
7 Aug 2026, 17:5684first reading

Engagement

18 posts held, back to 14 February 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 18 posts for this entry, the most recent from 21 May 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
42s
Average length
42s

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

946 reactions across 9 posts, in 17 distinct kinds. The most used accounts for 13.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 537995425491402097412413.1%
custom 540457223436057883011912.6%
custom 532362184181681480211211.8%
custom 54318968850172096039910.5%
custom 5460654049000977217949.94%
custom 5379698541151153870889.30%
custom 5323697085348869961869.09%
custom 5470115604256028448626.55%
custom 5413442862245253787464.86%
custom 5425010197015849631363.81%
custom 5276527972092770383242.54%
custom 5994703201847219462151.59%
custom 520863117486746692790.951%
custom 531448037758943397790.951%
custom 531250428890635387880.846%
custom 547446328798061786480.846%
custom 531028754032076516770.74%

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

Measured over the 18 most recent posts we hold, published 14 February 2026 to 21 May 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.

Telegram Stars

Stars received
86
across the posts below
Posts paid on
4
of 18 we hold a reading for · 22%
Most on one post
60
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @c3rk1o. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 18 most recent posts we hold for this entry, published 14 February 2026 to 21 May 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

21 May 2026, 08:20 UTC79 viewsread 9 August 2026

доброго денечка! если тут кто остался живой, я открыла новый канал ( @c3al1n ), буду рада если перейдете туда! можем возобновить сотрудничества, только напишите в лс/анон

2 Mar 2026, 11:33 UTC567 views139 reactions5 Starsread 9 August 2026
Photo

Photo, posted without a caption

custom 537995425491402097427custom 546065404900097721727custom 532362184181681480223custom 54134428622452537879custom 53236970853488699618custom 54045722343605788308custom 54701156042560284488custom 54744632879806178648

2 Mar 2026, 11:33 UTC602 views115 reactionsread 9 August 2026

☕️☕️ see, right n0w, i need you, ☕️☕️ i'll meet you som3where now you up now, i see you, i get you, 🤩 take care now, slow down, be c0ol, 🔤 m4ss you, c0me here now (

custom 532362184181681480221custom 537995425491402097421custom 546065404900097721720custom 547011560425602844813custom 53236970853488699618custom 54045722343605788308custom 54134428622452537878custom 54318968850172096038

2 Mar 2026, 11:33 UTC450 views69 reactionsread 9 August 2026
File

File, posted without a caption

custom 532362184181681480215custom 540457223436057883015custom 547011560425602844815custom 537969854115115387010custom 53799542549140209746custom 54606540490009772175custom 53236970853488699613

28 Feb 2026, 17:28 UTC369 views124 reactionsread 9 August 2026
Photo

Photo, posted without a caption

custom 543189688501720960325custom 537995425491402097424custom 540457223436057883024custom 546065404900097721711custom 53236970853488699618custom 53796985411511538707custom 54134428622452537877custom 54701156042560284487

28 Feb 2026, 17:28 UTC433 views57 reactionsread 9 August 2026
File

File, posted without a caption

custom 543189688501720960316custom 537995425491402097414custom 532369708534886996113custom 54701156042560284486custom 53796985411511538704custom 54045722343605788304

28 Feb 2026, 17:28 UTC372 views69 reactionsread 9 August 2026

🤩🤩я сх0жу с ума и мне пора лечить гол0ву, я ст4раюсь быть ч4стной (🤩🤩)

custom 532362184181681480220custom 532369708534886996119custom 546065404900097721717custom 54134428622452537877custom 52765279720927703836

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Mentions

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

“🔒`!ce cr3am k1o しろい” (@c3rk1o), 83 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/c3rk1o.

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.