Telegram RegisterThe public register of Telegram
Telegram profile photo for Castella

Channel

Castella

@caste11a

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

103subscribers

-39 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-1004350506021
TypeChannel
Username@caste11a
Created14 June 2026measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live1 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 1 September 2026
On Telegramt.me/caste11a

Growth

103142122.59 August 2026 — 142 subscribers9 August 2026 — 141 subscribers17 August 2026 — 122 subscribers24 August 2026 — 110 subscribers1 September 2026 — 103 subscribers9 August 20261 September 2026
5 measurements spanning 23 days, net -39. 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 97–148 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Sept 2026, 01:06103-7
24 Aug 2026, 14:25110-12
17 Aug 2026, 14:16122-19
9 Aug 2026, 07:53141-1
9 Aug 2026, 01:45142first reading

Engagement

8 posts held, back to 14 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 4 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

49 reactions across 5 posts, in 11 distinct kinds. The most used accounts for 16.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5235753949176293466816.3%
custom 5422789535715064830816.3%
custom 5868237245571407238714.3%
custom 5422784373164375309510.2%
custom 532574368880501902548.16%
custom 581678082294599611248.16%
custom 586597700614698527648.16%
custom 581669983704266347136.12%
custom 521569095005088186524.08%
custom 540694881156415616824.08%
custom 540924080797675092024.08%

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 5 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 49 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 14 June 2026 to 4 July 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

4 Jul 2026, 08:56 UTC236 views2 reactionsread 9 August 2026

Союзники,рада была с вами сотрудничать 🤩

custom 52156909500508818652

Signed elyséa

4 Jul 2026, 08:49 UTC268 viewsread 9 August 2026

все союзы разрыв, кф закрывается по личным причинам, спасибо всем кто были с нами, патент за нами.

27 Jun 2026, 20:19 UTC494 views3 reactionsread 9 August 2026

на ежедневный репост https://t.me/caste11a/360 https://t.me/caste11a/361

custom 52357539491762934663

27 Jun 2026, 20:17 UTC786 views3 reactionsread 9 August 2026

заключаем союзы🤩 правила 🔞 связь 🔞 лист

custom 52357539491762934663

27 Jun 2026, 20:15 UTC≈1,410 views22 reactionsread 9 August 2026
Photo

🤩elcome to Castella✔️ Subscribe to the channel🤩 Read the rules🎁 Send a request to the chat 🤩

custom 54227895357150648305custom 54227843731643753094custom 58682372455714072383custom 53257436888050190252custom 54092408079767509202custom 58166998370426634712custom 58167808229459961122custom 54069488115641561681

27 Jun 2026, 20:14 UTC407 views19 reactionsread 9 August 2026
Photo

Navigation Castella🤩 🔤atient 🔤ules 🔤hat 🔤non 🔤dmins 🔤rchive 🤩oost 🤩nion 🔤iktok

custom 58682372455714072384custom 54227895357150648303custom 58659770061469852763custom 52357539491762934662custom 53257436888050190252custom 58167808229459961122custom 54069488115641561681custom 54227843731643753091

Showing the 8 most recent of 8 posts we hold for @caste11a. 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 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 1 September 2026 — this entry's latest reading, not the date you are reading this.

“Castella” (@caste11a), 103 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/caste11a.

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.