Telegram RegisterThe public register of Telegram
Telegram profile photo for 𐙚͏ ᜔ֹ 𝓒1ȶ ‎͜͝ʂ3֪ოᖯ᷒ᰰ0Ɩʂ ͜͡⠳ั ͜͡ ࣮ ྀི᪻

Channel

𐙚͏ ᜔ֹ 𝓒1ȶ ‎͜͝ʂ3֪ოᖯ᷒ᰰ0Ɩʂ ͜͡⠳ั ͜͡ ࣮ ྀི᪻

@c1t_s3mb0ls

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

870subscribers

+281 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-1003964477395
TypeChannel
Username@c1t_s3mb0ls
CreatedBetween 1 April 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 November 2026
Measurements held15
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/c1t_s3mb0ls

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 20 September 2026 and assigned it the closest of 31 fixed categories, at 96% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

589870729.57 August 2026 — 589 subscribers8 August 2026 — 589 subscribers8 August 2026 — 590 subscribers15 August 2026 — 607 subscribers21 August 2026 — 646 subscribers28 August 2026 — 662 subscribers6 September 2026 — 677 subscribers13 September 2026 — 706 subscribers27 September 2026 — 756 subscribers8 October 2026 — 806 subscribers15 October 2026 — 823 subscribers23 October 2026 — 846 subscribers29 October 2026 — 851 subscribers5 November 2026 — 853 subscribers15 November 2026 — 870 subscribers7 August 202615 November 2026
15 measurements spanning 100 days, net +281. 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 547–912 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Nov 2026, 10:49870+17
5 Nov 2026, 23:35853+2
29 Oct 2026, 13:38851+5
23 Oct 2026, 04:18846+23
15 Oct 2026, 03:41823+17
8 Oct 2026, 10:57806+50
27 Sept 2026, 00:21756+50
13 Sept 2026, 06:19706+29
6 Sept 2026, 08:00677+15
28 Aug 2026, 06:53662+16
21 Aug 2026, 17:55646+39
15 Aug 2026, 02:25607+17
8 Aug 2026, 15:03590+1
8 Aug 2026, 03:18589no change
7 Aug 2026, 18:36589first reading

Engagement

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

Reaction mix

1,050 reactions across 17 posts, in 12 distinct kinds. The most used accounts for 13.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 536637491694381356114113.4%
custom 522425830599978571013412.8%
custom 524911332039645399313312.7%
custom 528744238164006885311110.6%
custom 615447773760507793110910.4%
custom 5285279401750070334969.14%
custom 5249080167543896296928.76%
custom 5433922249860095779928.76%
custom 5350332621387756383898.48%
custom 6307843787020313546201.90%
custom 6307443727996558526171.62%
custom 6307725108483990676161.52%

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 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 17 of the 19 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 1,050 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 31 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, 20:46 UTC46 views6 reactionsread 8 August 2026

Я на вас обиделась

custom 53503326213877563835custom 61544777376050779311

5 Aug 2026, 07:35 UTC292 views77 reactionsread 8 August 2026
File

͜ ུ ఇ 𝂅 𝓒ɾ𝗲ᥲ𝕞 、、 . 𓏏 𝒸

custom 615447773760507793132custom 528527940175007033423custom 535033262138775638322

5 Aug 2026, 07:35 UTC292 views74 reactionsread 8 August 2026

⏜᷼︵ ᨰׁ𝓱ᥲ𝒍ᧉ ͜͡♡ ̼ ㅤか

custom 615447773760507793130custom 535033262138775638323custom 528527940175007033421

5 Aug 2026, 07:35 UTC289 views67 reactionsread 8 August 2026

𖹭 ֙꣼ ꬶ𝘳𝜚𝓪ȶ 𓈀 𝒍ᨵ𝜐ᧉ ༢ ּ 𝓾 ྀ ︶ ‌𝗵ս𝕞ᥲ𝓗 ‌۫۫ ︡

custom 528527940175007033428custom 615447773760507793120custom 535033262138775638319

5 Aug 2026, 07:35 UTC294 views70 reactionsread 8 August 2026
File

⌣ ⌣ ꬶᨵ𝒍d𝗲ꪀ ₍̨ ᴖ֥ᵔִ₎ 𝑑𝗮ׄ͜ᥡ ︐ ᘡㅤ𝓮

custom 615447773760507793126custom 528527940175007033424custom 535033262138775638320

4 Aug 2026, 05:48 UTC258 views16 reactionsread 8 August 2026
Sticker

Sticker, posted without a caption

custom 63074437279965585267custom 63078437870203135465custom 63077251084839906764

4 Aug 2026, 05:48 UTC329 views37 reactionsread 8 August 2026

݂. Ი‌፝֟Ი ݀۬ . ꨴ 𝓝𝗲w 𝗲ოׄ𑄹‌ִ‌‌j𝗶 𝓹𝗮‌ׄ𝐜‌𝐤 .ㅤׅ᨞ᩤᩣ 𐙚 ი𑄹‌н𝓹ɑ𝐁𝘂‌ꪒ𝐜߬ᦸ 𝒏꛱ɑ𝐤 ? 𝐜߬ 𝐁𝗮‌ׄ‌ɕ ӄ𑄹‌ຕℳᩘ! ࿙‌࿚݃࿙‌࿚݃ ፝֟ ࿙⃛‌࿚⃛ ꒰‌︨-ིིྀ-‌︧꒱ ࿙⃛‌࿚⃛ ፝֟ ࿙‌࿚݃࿙‌࿚݃ ㅤ᷼ ︵ ִׁ C‌𝗵𝐢‌𝗵𝐢𝘳ᨵ ︵᷼ ׁ୧

custom 630784378702031354615custom 630772510848399067612custom 630744372799655852610

2 Aug 2026, 12:51 UTC404 views54 reactionsread 8 August 2026

͡ ͝ ۫ 𓈅Nᥲ𝜐𝐢ᥲㅤ۫ ㅤ۫लयㅤᤴ ㅤ

custom 543392224986009577925custom 528744238164006885315custom 524908016754389629614

2 Aug 2026, 12:51 UTC418 views52 reactionsread 8 August 2026

︵⃨ . ᜊ𝕞𝓐︩︪𝘳𝑚͡ᥲ𝒍ᥲdׂ݂ᧉ֗ ֢ ᡴꪫ ༌

custom 524908016754389629621custom 528744238164006885317custom 543392224986009577914

2 Aug 2026, 12:51 UTC421 views53 reactionsread 8 August 2026

۫ ོ ִ ‛‛ 𝒍𝐢ꪀׁᧉ ᨵ𝙛 𝙛ᥲȶᧉ֗ 𝕷𑁁

custom 528744238164006885323custom 524908016754389629617custom 543392224986009577913

2 Aug 2026, 12:51 UTC417 views50 reactionsread 8 August 2026

݂. Ი‌፝֟Ი ɕִ𝘳ᨵ𝐢𝕤𝕤ᥲꪀׁȶ𝕤 ፝֟ ࿙‌୧ . 𝜚

custom 528744238164006885324custom 524908016754389629613custom 543392224986009577913

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

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.

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

“𐙚͏ ᜔ֹ 𝓒1ȶ ‎͜͝ʂ3֪ოᖯ᷒ᰰ0Ɩʂ ͜͡⠳ั ͜͡ ࣮ ྀི᪻” (@c1t_s3mb0ls), 870 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/c1t_s3mb0ls.

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.