Telegram RegisterThe public register of Telegram
Telegram profile photo for ℂ𝕙𝕣𝕠𝕟𝕚𝕔𝕝𝕖𝕤 𝕠𝕗 ℂ𝕚𝕤𝕔𝕠 ⟦𝕒𝕣𝕔𝕙𝕚𝕧𝕖⟧

Channel

ℂ𝕙𝕣𝕠𝕟𝕚𝕔𝕝𝕖𝕤 𝕠𝕗 ℂ𝕚𝕤𝕔𝕠 ⟦𝕒𝕣𝕔𝕙𝕚𝕧𝕖⟧

@CiscoRamonEOT

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

30subscribers

-9 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003728196476
TypeChannel
Username@CiscoRamonEOT
CreatedBetween 1 February 2026 and 12 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live11 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/CiscoRamonEOT

Growth

303934.58 August 2026 — 39 subscribers10 August 2026 — 39 subscribers16 August 2026 — 37 subscribers24 August 2026 — 38 subscribers1 September 2026 — 37 subscribers11 September 2026 — 30 subscribers8 August 202611 September 2026
6 measurements spanning 34 days, net -9. 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 29–40 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 06:1730-7
1 Sept 2026, 13:5337-1
24 Aug 2026, 15:4438+1
16 Aug 2026, 17:5537-2
10 Aug 2026, 20:3039no change
8 Aug 2026, 10:5639first reading

Engagement

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

Reaction mix

134 reactions across 10 posts, in 19 distinct kinds. The most used accounts for 9.70% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 6021486789703769089139.70%
custom 6023940002008799618139.70%
🤓139.70%
custom 6021384767050618542118.21%
👾118.21%
custom 6023761060786346622107.46%
custom 602357925911567429785.97%
custom 602389790703433080585.97%
💯85.97%
🤯75.22%
🦄64.48%
🆒53.73%
🫡53.73%
👌42.99%
🤷‍♂42.99%
👨‍💻32.24%
🙏21.49%
🤡21.49%
custom 602185268226268259810.746%

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

Measured over the 20 most recent posts we hold, published 12 March 2026 to 31 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

31 Jul 2026, 21:36 UTC25 views6 reactionsread 10 August 2026

Саппорт: отряд не заметил потери бойца

🤓3👾2👨‍💻1

31 Jul 2026, 21:35 UTCviews —

Channel name was changed to «ℂ𝕙𝕣𝕠𝕟𝕚𝕔𝕝𝕖𝕤 𝕠𝕗 ℂ𝕚𝕤𝕔𝕠 ⟦𝕣𝕖𝕤𝕥⟧»

16 Jul 2026, 16:36 UTC61 views16 reactionsread 10 August 2026

😀😀😀😀😀🤍🤍🌟🌟🌟🌟 😀😀😀😀😀🔤уки едва двигались, 😀😀😀😀пока пытались ухватить 😀😀😀пятку обувки, дабы стянуть 😀😀её, но пальцы потеряли чувствительность от уличного холода. Какая жалость, что такие красивые варежки, которые мне дала Её Снежное Величество, оказались малополезными в суровый хлад северных земель. 😀– 🔤а полно вам, Ваша Морозность, – я попытался улыбнуться сквозь немоту своих холодных щёк, но наверняка это было похоже на

👾6custom 60239400020087996185🤓4🤯1

10 Jul 2026, 15:58 UTC69 views14 reactionsread 10 August 2026
Photo

🤍🤍🤍🤍🤍 🤍🤍🤍🤍🤍🤍🤍🤍 👁️ #BacktoSchool 👁️ 🌧️🌧️ beginning 🦋 end 🌧️ 👁️ #MedievalEOT 👁️ 🌧️🌧️ beginning 🦋 end 🌧️ 😀😀🤍🤍🤍🤍🤍🤍🤍🤍

💯5👌4🤓2🙏2👨‍💻1

10 Jul 2026, 15:57 UTC52 views13 reactionsread 10 August 2026
Photo

😀😀😀😀😀😀😀🌟🌟🌟🌟 😀😀😀😀😀#MedievalEOT 😀😀😀😀🔤риветствую, путник! 😀😀😀Добро пожаловать в 😀 Заснеженное Королевство! 😀Меня зовут Циско, и я бард при дворе великой Снежной королевы. Правда, звучит куда важнее, чем есть на самом деле, но не суть. 😀🔤, сразу дам совет: законы лучше не нарушай. Её Величество Фрост – дама грозная, и если решит, что ты доставляешь слишком много хлопот, то можешь быстро обернуться ледяной статуей... 😀🔤о

🆒5👾3💯3👨‍💻1🤓1

10 Jul 2026, 15:57 UTC21 viewsread 10 August 2026
Forwarded from @echoesoftomorrowPhoto

ᅠ🖤🖤 Доброго времени суток всем подписчикам EOT!🚬 Хотим с огромной радостью сообщить, что с сегодняшнего дня по 🤩🤩 августа у нас снова стартует ивент :: 🤩🤩🤩 ➿➿➿➿➿➿➿ 🎁 👀 🎁 ➿ 🍒🍒🍒🍒🍒🍒🍒🍒 🌺 На целый месяц наш привычный уклад уходит в прошлое — теперь здесь правит железо и кровь, магия и предательство. Мы переносимся в мрачное и величественное средневековье, где судьбы решаются на острие меча, а за каждым троном стои

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

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

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

“ℂ𝕙𝕣𝕠𝕟𝕚𝕔𝕝𝕖𝕤 𝕠𝕗 ℂ𝕚𝕤𝕔𝕠 ⟦𝕒𝕣𝕔𝕙𝕚𝕧𝕖⟧” (@CiscoRamonEOT), 30 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/CiscoRamonEOT.

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.