27 May 2026, 17:56 UTC46 viewsread 13 August 2026
Ресты: (здесь появятся участники в ресте.)
Channel
𝓙𝓮𝓵𝓵𝔂𝓼𝓸𝓵𝓽𝓲𝓬𝓮 𝓕𝓵𝓸𝓸𝓭 🌄 Info ⟢
@Jellysoltice_flood
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
5subscribers
+0 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003930986059 |
|---|---|
| Type | Channel |
| Username | @Jellysoltice_flood |
| Created | 20 May 2026 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Jellysoltice_flood |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 02:48 | 5 | no change |
| 12 Aug 2026, 12:50 | 5 | first reading |
Engagement
7 posts held, back to 20 May 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 7 posts for this entry, the most recent from 27 May 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 5
- Links
- 1
Lifetime counters from Telegram’s own channel header, read 13 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.
Recent posts
27 May 2026, 17:54 UTC46 viewsread 13 August 2026
Photo
𝑳 𝑰 𝑺 𝑻 𝑶 𝑭 𝑹 𝑶 𝑳 𝑬 𝑺 :: 𝗕𝘂𝘀𝘆 / Зᴀняᴛᴏ :: { 🪼 } 𝗙𝗿𝗲𝗲 / Сʙᴏбᴏднᴏ :: { } 𝗥𝗲𝘀𝗲𝗿𝘃𝗮𝘁𝗶𝗼𝗻 / Бᴩᴏнь :: {🫧} начальный Шелли- редкие Нита- Кольт- Булл- Брок- Эль Примо- Барли- Поко-🪼(совлд) Роза- сверхредкие Джесси- Динамайк- Тик- 8бит- Рико- Дэррил- Пенни- Карл- Джеки- Гас- эпические Мэнди- Анджело- Бо- Грифф- Гром- Эмз- Мэйси- Хэнк- Сту- Пайпер- Бонни- Гэйл- Ларри и лори- Колетт- Пэм- Белль- Берри- Биби- Шейд-🪼 Мип…
27 May 2026, 17:51 UTC26 viewsread 13 August 2026
Photo
АДМИНИСТРАЦИЯ 🌀 Владелец — @Silly_Crawlerr Совлд. — @AnechkaPypsikk ◍ ИЩЕМ МОНТАЖËРА!👤 Если вы хотите стать администратором или модератором то пишите Владельцу или Совладельцу. Напишите причину, почему и для чего вы хотите стать админом/модератором. Что то по типу: Привет, хочу стать администиатором. Я буду следить за чатом, что бы ребята не нарушали правила. (Или же любую другую причину.)
27 May 2026, 17:43 UTC28 viewsread 13 August 2026
Photo
𝑹𝑼𝑳𝑬𝑺 🎐🧂 основные запреты (ОБЯЗАТЕЛЬНО прочитайте правила в самóм чате флуда написав слово "Правила") - спам - отправка более трех одинаковых сообщений подряд, бессмысленный контент. Спам негативными реакциями чуть ли не под каждое сообщение тоже считается. - конфликты - оскорбления, агрессия, провокации, троллинг. - контент 18+ - непристойный, шокирующий или жестокий материал без предупреждения и блюра. - рекл…
27 May 2026, 17:41 UTC28 views0 reactionsread 13 August 2026
Photo
НОРМА И РЕСТ 🧊🌌 ➤ норма - норма составляет 100 сообщений в неделю. Нету нормы — варн. Если не хватает от 1 до 5 сообщений то варна не дают. (3 варна = бан) - чистка проводится в любое удобное время в воскресенье. за 1 час до чистки вас оповестит администратор каллом и назовет точное время проведения по московскому времени. - неактив 12+ дней без реста - бан - Если у вас +6 дней во флуде то чистка вас касается (е…
27 May 2026, 17:39 UTC24 views0 reactionsread 13 August 2026
Photo
🫧 НАВИГАЦИЯ 🫧 Всех приветствуем в инфо канале! Будем рады новым участникам🪷 ◌ норма и рест ◌ правила ◌ администрация ◌ роли (Designer For Pfp And Banner Is @shitochann_designer Thanks For Help💜) Тикток - Here!
20 May 2026, 06:27 UTCviews —
Channel created
Showing the 7 most recent of 7 posts we hold for @Jellysoltice_flood. 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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“𝓙𝓮𝓵𝓵𝔂𝓼𝓸𝓵𝓽𝓲𝓬𝓮 𝓕𝓵𝓸𝓸𝓭 🌄 Info ⟢” (@Jellysoltice_flood), 5 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/Jellysoltice_flood.
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.