Telegram RegisterThe public register of Telegram
Telegram profile photo for <𝓛𝓪𝔂𝓯 𝓴𝓪𝓷𝓪𝓵 𝓨𝓪𝓭𝓻𝓸 𝓢𝓲𝓵𝔂 𝓝𝓪𝓬𝓾>

Channel

<𝓛𝓪𝔂𝓯 𝓴𝓪𝓷𝓪𝓵 𝓨𝓪𝓭𝓻𝓸 𝓢𝓲𝓵𝔂 𝓝𝓪𝓬𝓾>

@SpletniFludaNatsu

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

12subscribers

-1 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-1003791116135
TypeChannel
Username@SpletniFludaNatsu
CreatedBetween 1 February 2026 and 15 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live11 September 2026
Measurements held5
Confirmed unchanged2 times, most recently 11 September 2026
On Telegramt.me/SpletniFludaNatsu

Growth

12141312 August 2026 — 13 subscribers13 August 2026 — 13 subscribers20 August 2026 — 14 subscribers26 August 2026 — 13 subscribers1 September 2026 — 12 subscribers12 August 20261 September 2026
5 measurements spanning 20 days, net -1. 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 12–14 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Sept 2026, 03:5712-1
26 Aug 2026, 03:5313-1
20 Aug 2026, 03:2414+1
13 Aug 2026, 10:3313no change
12 Aug 2026, 12:4713first reading

Engagement

10 posts held, back to 15 June 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 10 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 11s
Average length
14s

Measured directly from 5 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

13 reactions across 10 posts, in 3 distinct kinds. The most used accounts for 76.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💘1076.9%
🕊215.4%
❤‍🔥17.69%

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

Measured over the 10 most recent posts we hold, published 15 June 2026 to 7 August 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

7 Aug 2026, 09:49 UTC5 views1 reactionsread 12 August 2026
Photo

Сегодня мы заключили союз с 🌕𝗠𝗢𝗢𝗡𝗟𝗜𝗧🌔𝗦𝗧𝗥𝗘𝗔𝗠𝗙𝗟𝗨𝗗 Желаем им удачи 𓏵۫۫⋮Iꬻׂׅ𝑓𑄹̸ִ - тык 𓏵۫۫⋮ℒ𝑖࣭۫𝑓ꫀ - тык

🕊1

4 Aug 2026, 17:43 UTC7 views1 reactionsread 12 August 2026
Video

ТТ флуда — тык 🤩🤩🤩🤩🤩🤩🤩🤩

💘1

3 Aug 2026, 10:45 UTC9 views3 reactionsread 12 August 2026
Photo

Сегодня мы заключили союз с Trafi flood Инфо — тык Лайф — тык Юз влд — @gomu_gum

❤‍🔥1💘1🕊1

21 Jun 2026, 16:21 UTC33 views1 reactionsread 12 August 2026

ᥰρᥙʙᥱᴛ-ᥰρᥙʙᥱᴛ! ᥙщᥱɯь κ᧐ʍɸ᧐ρᴛныᥔ ᥙ ᥲκᴛᥙʙныᥔ ɸ᧘уд? ᴛᥱδᥱ κ нᥲʍ! ᥰρᥱдᥴᴛᥲʙ᧘яю ʙᥲɯᥱʍу ʙнᥙʍᥲнᥙю ɸ᧘уд ᥰ᧐ ᥲнᥙʍᥱ "ᴛ᧐κᥙᥔᥴκᥙᥱ ʍᥴᴛᥙᴛᥱ᧘ᥙ". ᥰ᧐чᥱʍу жᥱ ʍы? ᥱᥴ᧘ᥙ ʙᥲʍ нᥱκ᧐ʍɸ᧐ρᴛн᧐ δыᴛь ʙ δ᧐᧘ьɯᥙх ɸ᧘удᥲх, ᴛ᧐ нᥲɯ ʙᥲʍ ᴛ᧐чн᧐ ᥰ᧐д᧐ᥔдёᴛ! 16 учᥲᥴᴛнᥙκ᧐ʙ. нᥱδ᧐᧘ьɯᥲя н᧐ρʍᥲ! 100 ᥴ᧐᧐ ʙ нᥱдᥱ᧘ю. ᧘ᥱᴦчᥱ ᧘ᥱᴦκ᧐ᴦ᧐ нᥲδρᥲᴛь! κ᧐ʍɸ᧐ρᴛныᥱ ᥲдʍᥙны, κ᧐ᴛ᧐ρыᥱ ʙᥴᥱᴦдᥲ ᥰρᥙᥴ᧘уɯᥲюᴛᥴя! ʙ ᧐ᥴ᧐δᥱнн᧐ᥴᴛᥙ х᧐чу ʙыдᥱ᧘ᥙᴛь ʙ᧘ᥲдᥱ᧘ьцᥱʙ ɸ᧘уд᧐ʙ, κ᧐ᴛ᧐ρых ᴛᥲκ ᥙ х᧐чᥱᴛᥴя ɜᥲᴛᥙᥴκᥲᴛь! ᥰρ᧐ᥴ…

💘1

21 Jun 2026, 16:21 UTC31 views1 reactionsread 12 August 2026
Photo

☺️☺️☺️☺️☺️ 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 🌕🤩𐌿ⲟдвᥲ᧘ δⲟнтᥱн™ 02.01.26-??? Инфо-тык 〰️〰️〰️〰️〰️〰️〰️〰️〰️〰️ ☺️то такое союзы и для чего они нужны? ☺️оюз- взаимовыгодная реклама флудов. ☺️о время союза флуды могут совместно участвовать в конкурсах/видео/голосованиях и тд.

💘1

17 Jun 2026, 11:05 UTC32 views1 reactionsread 12 August 2026
Video

✨✨✨✨✨ ✨✨✨✨✨ Тт флуда — тык Автор: Майки 🤩🤩🤩🤩 🤩🤩🤩🤩 🤩🤩🤩🤩 🤩🤩🤩🤩

💘1

16 Jun 2026, 09:55 UTC31 views2 reactionsread 12 August 2026
Video

✨✨✨✨✨ ✨✨✨✨✨ Тт флуда — тык Автор: Нацу Драгнил 🤩🤩🤩🤩 🤩🤩🤩🤩 🤩🤩🤩🤩 🤩🤩🤩🤩

💘2

15 Jun 2026, 17:42 UTC31 views1 reactionsread 12 August 2026
Video

✨✨✨✨✨ ✨✨✨✨✨ Тт флуда — тык Автор: Нацу Драгнил 🤩🤩🤩🤩 🤩🤩🤩🤩 🤩🤩🤩🤩 🤩🤩🤩🤩

💘1

15 Jun 2026, 17:37 UTC38 views1 reactionsread 12 August 2026
Photo

✨✨✨✨ ✨✨✨✨✨ Всех приветствует администрация флуда Core of Power Natsu🩷 Мы рады, что вы присоединились к нам☑️ 🤍🤍🤍🤍🤍🤍🤍🤍 Здесь будет опубликовываться вся информация/видео/новости и многое другое касаемое флуда. 🤩🤩🤩🤩🤩🤩🤩🤩🤩 🤩🤩🤩🤩🤩🤩🤩🤩🤩 🤩🤩🤩🤩🤩🤩🤩🤩🤩

💘1

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

“<𝓛𝓪𝔂𝓯 𝓴𝓪𝓷𝓪𝓵 𝓨𝓪𝓭𝓻𝓸 𝓢𝓲𝓵𝔂 𝓝𝓪𝓬𝓾>” (@SpletniFludaNatsu), 12 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/SpletniFludaNatsu.

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.