Telegram RegisterThe public register of Telegram
Telegram profile photo for summer coolness🍉

Channel

summer coolness🍉

@Summercoolness

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

26subscribers

-4 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1004293520421
TypeChannel
Username@Summercoolness
Created3 June 2026measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live12 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 12 September 2026
On Telegramt.me/Summercoolness

Growth

263329.511 August 2026 — 30 subscribers12 August 2026 — 29 subscribers19 August 2026 — 33 subscribers27 August 2026 — 32 subscribers3 September 2026 — 27 subscribers12 September 2026 — 26 subscribers11 August 202612 September 2026
6 measurements spanning 31 days, net -4. 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 25–34 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Sept 2026, 02:0126-1
3 Sept 2026, 13:4227-5
27 Aug 2026, 18:4432-1
19 Aug 2026, 20:4733+4
12 Aug 2026, 05:4829-1
11 Aug 2026, 14:4630first reading

Engagement

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

Recent posts

25 Jun 2026, 17:58 UTC276 viewsread 11 August 2026
Photo

ADMINI summer coolness STRATION • Администрация отвечает за порядок, развитие и комфортную атмосферу во флуде. Все решения администрации обязательны к исполнению. Обсуждение действий администрации в негативном ключе запрещено – при несогласии можно обратиться к старшему составу или владельцу. 💦own— Авантюрин @Solem_N Отвечает за общее управление флудом и его развитие, а также за функционирование ф

25 Jun 2026, 17:58 UTC280 viewsread 11 August 2026
Photo

SET summer coolness SET •𐌱 данный ꭑомент набор 💦 Закрыт Открыт . 🐬 𝒂𝗱𝗺: @Solem_N 𝗰𝒓: 𝘁𝒶𝗴s : #хср

25 Jun 2026, 17:58 UTC291 viewsread 11 August 2026
Photo

Re summer coolness ST • Ресты участников our flood Фаенон - 11 августа Анакса - 17 августа Капитано - 20 августа Блейд - 20 августа Панталоне - 24 августа Юнь Цзинь - 27 августа Яо Гуан - ± до конца лета . 🐬 𝒂𝗱𝗺: @Solem_N 𝗰𝒓: 𝘁𝒶𝗴s : #хср

25 Jun 2026, 17:58 UTC235 viewsread 11 August 2026
Photo

NAVI summer coolness GATION •навигация по инфо канальчику, где сможете найти нужную информацию для вступления💦 . 𝒂𝗱𝗺: @Solem_N 𝗰𝒓: 🐬 𝘁𝒶𝗴s : rules Roles set administration boost life tik tok.1 rest tik tok.2

25 Jun 2026, 17:58 UTC247 viewsread 11 August 2026
Photo

RU summer coolness LES 𝗰𝒓: 𝘁𝒶𝗴s : незнание пթавилㅤне освобождаетㅤот 𖦹тветственности🐬 💦 ㅤдля удобства была создана ɕтатьяᵗᵃᵖ. ㅤㅤㅤㅤ . мы имеем право не Впустить вас во флуд、если вы покажетесь сомнительной ꪒичностью. 💦

25 Jun 2026, 17:58 UTC251 viewsread 11 August 2026

RO summer coolness LES ㅤㅤзанято – 😅 ㅤㅤбронь – 🌸 ㅤㅤждëм – 🥰 💦 List of occupied roles: 🤩enshin impact : Капитано - 😅 Панталоне - 😅 Лоэн - 😅 Юнь Цзинь - 😅 Дурин - 😅 Варка - 😅 Флинс - 😅 🤩onkai star rail : own.Авантюрин - 😅 Фаенон - 😅 Блейд - 😅 coown.Зарянка - 😅 adm.Темень - 😅 adm.Стелла - 😅 Георгина - 😅 Эванесса - 😅 Анакса - 😅 Яо Гуан - 😅 Кафка - 😅 Лоча - 😅 Мидей - 😅 Кастория - 😅 Великая Герта - 😅 Сандей - 😅 Фуга

Showing the 8 most recent of 8 posts we hold for @Summercoolness. 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.

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.

Named by

Channels on the register whose posts name this channel's handle.

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

“summer coolness🍉” (@Summercoolness), 26 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/Summercoolness.

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.