Telegram RegisterThe public register of Telegram
Telegram profile photo for рест//Crew13🫀

Channel

рест//Crew13🫀

@ccrew13

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

28subscribers

+0 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-1002151767525
TypeChannel
Username@ccrew13
DescriptionДальше Бога нет
CreatedBetween 1 April 2024 and 31 October 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live15 August 2026
Measurements held2
On Telegramt.me/ccrew13

Growth

287 August 2026 — 28 subscribers11 August 2026 — 28 subscribers7 August 202611 August 2026
2 measurements spanning 4 days. 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 27–29 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 06:1528no change
7 Aug 2026, 14:3528first reading

Engagement

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

What this channel posts

Photos
81
Videos
3
Links
4

Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

220 reactions across 12 posts, in 11 distinct kinds. The most used accounts for 23.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52381813186630866605223.6%
custom 52671504951174896363817.3%
custom 54588943235903761783214.5%
custom 54407352920571993352511.4%
🍓219.55%
custom 5368598520297180207177.73%
custom 5192786138569398343156.82%
❤‍🔥135.91%
custom 527169762853337781431.36%
🌭31.36%
🤬10.455%

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

Measured over the 12 most recent posts we hold, published 6 April 2025 to 5 April 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
6
across the posts below
Posts paid on
2
of 12 we hold a reading for · 17%
Most on one post
5
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @ccrew13. 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 12 most recent posts we hold for this entry, published 6 April 2025 to 5 April 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

5 Apr 2026, 17:06 UTC87 views6 reactions1 Starread 11 August 2026
Photo

🤩🤩🤩🤩🤩🤩🤩🤩 Седня у мене день рождения, хочу сказать спасибо всем, кто следит за этим уебищным тгк так ещё и активничает! Простите, шо админ дебил и постит арты раз в год. P.s. завтра ещё часть след арта скину. Как всегда буду очень благодарна репостам🤩🤩🤩

🍓3custom 54407352920571993353

14 Feb 2026, 17:10 UTC122 views9 reactions5 Starsread 11 August 2026
Photo

С пятницей 13, с днём всех влюблённых, с днём одиночек!!! 🐶🎀 (Ебучи тэгэ не хочет выкладывать посты)

🍓6custom 52671504951174896363

3 Jan 2026, 17:06 UTC151 views12 reactionsread 11 August 2026
Photo

Фух, чуть не выложила что то адекватное

custom 53685985202971802075custom 54588943235903761784custom 52381813186630866603

18 Dec 2025, 17:06 UTC123 views16 reactionsread 11 August 2026
Photo

Боже, дай бог до нг успеть дорисовать ..

custom 52671504951174896367❤‍🔥5🌭3🤬1

20 Nov 2025, 17:06 UTC173 views14 reactionsread 11 August 2026
Photo

🩸🥹🥹

❤‍🔥5custom 51927861385693983434custom 54588943235903761784custom 52381813186630866601

10 Nov 2025, 17:06 UTC120 views14 reactionsread 11 August 2026
Photo

Мой первый донат куда то кроме роблакса немного волнительно 🥰

custom 54588943235903761787custom 52381813186630866604custom 52671504951174896363

9 Oct 2025, 17:06 UTC135 views15 reactionsread 11 August 2026
Photo

Каллап с Рин 😝 Был очень милый и приятный коллаб, спасиба большое☺️☺️☺️

custom 52381813186630866609custom 51927861385693983433custom 52671504951174896363

20 Sept 2025, 17:06 UTC137 views18 reactionsread 11 August 2026
Photo

Декстер Морган (Внезапный дэб)

custom 53685985202971802079custom 52381813186630866606custom 52716976285333778143

26 Jun 2025, 09:50 UTC189 views18 reactionsread 11 August 2026
Photo

😱 #eyes_change

custom 51927861385693983438custom 54407352920571993357custom 53685985202971802073

23 Apr 2025, 17:06 UTC252 views26 reactionsread 11 August 2026
Photo

Всё, чистка закончена, кто отметился - тот молодец, держите арт А кто нет.......ну печально

custom 523818131866308666010custom 52671504951174896368custom 54588943235903761787custom 54407352920571993351

14 Apr 2025, 17:06 UTC223 views34 reactionsread 11 August 2026
Photo

У меня совсем нет времени рисоват🥀 Вот хоть чот

🍓12custom 545889432359037617810custom 52381813186630866609❤‍🔥3

6 Apr 2025, 04:15 UTC246 views38 reactionsread 11 August 2026
Photo

Ну блин у меня сегодня день рождения, там вроде у художников лучший подарок это репост работ🥺😮‍💨 Ну я не художник, поэтому можно просто соточку на карту кинуть 😇🌹 (шутк)

custom 526715049511748963614custom 544073529205719933514custom 523818131866308666010

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

“рест//Crew13🫀” (@ccrew13), 28 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/ccrew13.

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.