Telegram RegisterThe public register of Telegram
Telegram profile photo for Святогніздя (Sviaks)

Channel

Святогніздя (Sviaks)

@sviaks

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

78subscribers

+0 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-1002257546986
TypeChannel
Username@sviaks
Descriptiontwitch.tv/sviaks
CreatedBetween 1 October 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live1 September 2026
Measurements held2
On Telegramt.me/sviaks

Growth

788 Aug 2026, 12:16 — 78 subscribers9 Aug 2026, 20:02 — 78 subscribers8 Aug 2026, 12:169 Aug 2026, 20:02
2 measurements spanning 1 day. 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 77–79 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 20:0278no change
8 Aug 2026, 12:1678first reading

Engagement

20 posts held, back to 21 July 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 1 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
305
Videos
5
Links
327

Lifetime counters from Telegram’s own channel header, read 9 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

96 reactions across 16 posts, in 11 distinct kinds. The most used accounts for 39.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3839.6%
😁2020.8%
😭1010.4%
👍88.33%
🥰88.33%
💔66.25%
🔥22.08%
custom 537109936378951260111.04%
custom 537311969063574660811.04%
🌚11.04%
💅11.04%

Custom emoji. 2 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 16 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 96 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 21 July 2026 to 1 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

1 Aug 2026, 08:15 UTC57 views15 reactionsread 9 August 2026

Ну походу ноу стрим, на жаль До 5 ранку не спалось, тепер тривоги шмавоги, русня гниль Всі після ночі живі? Ви як?

9💔6

30 Jul 2026, 17:36 UTC70 viewsread 9 August 2026
Photo

▶️ ЗАПУСТИВ! - Продовження яйця, але в коопі... 🌝 ДИВИТИСЬ ТУТ 🌚

30 Jul 2026, 16:42 UTC60 views4 reactionsread 9 August 2026

Трііішки посуну на ± 30 хвилин, в коридорі тусуюсь

👍4

30 Jul 2026, 16:00 UTC57 views8 reactionsread 9 August 2026

Через годинку стрим, єбац веселий кооп має бути Аби на спокійному все було, а не "посваритись за 3.5 хв"... До шо? До зустрічі

🥰8

29 Jul 2026, 12:34 UTC68 views4 reactionsread 9 August 2026

Поняв, найближча зарплатня розподілена на книги, бо купа трилогій Стрім через місяць, буду читати (пизжу, побачимось сьогодні скоріш за все, а стрим завтра) 🖤 Дякую всім велике за поради! Купа цікавих і різноманітних варіантів, шо я вже лізу в акцію 4=8...

4

29 Jul 2026, 11:23 UTC54 viewsread 9 August 2026

📚Потрібна порада на книжку від знавців. Яку книгу прочитали нещодавно і кайфанули? Я хочу одну взять, але там акція 2=4, тому очевидно що мені треба ще 3 штуки...

28 Jul 2026, 17:05 UTC61 viewsread 9 August 2026

▶️ ЗАПУСТИВ! - Відео про януковича - Кооп машинки з вамосом, якщо в нього не буде боліти голова - і ще гамєс "Не спи з рибами" 🌝 ДИВИТИСЬ ТУТ 🌚

27 Jul 2026, 15:33 UTC65 views6 reactionsread 9 August 2026

Стрім шо? Правильно, завтра в 20:00, але хочу подовше почати робити їх по таймінгах і аля по 4 години Завтра подивимось, що вийде з цього 😳 До зустрічі, дотєри, ксєри, рокетлігєри, хоррорлавери, аколифільмєри, крінжуможеподивимось

5💅1

25 Jul 2026, 09:37 UTC80 views1 reactionsread 9 August 2026

▶️ ЗАПУСТИВ! Адреналін колю на стримі (три гри одночасно) 🌝 ДИВИТИСЬ ТУТ 🌚

1

24 Jul 2026, 17:18 UTC71 views3 reactionsread 9 August 2026

Ну нарешті справжній IRL, але у twitch.tv/didusyk Каже, що буде ходити по заброшках 🇮🇱Ізраїлю, але можливо щось інше

3

24 Jul 2026, 09:06 UTC73 views12 reactionsread 9 August 2026
Photo

Завтра орієнтовно в 1️⃣2️⃣🔤0️⃣0️⃣➖1️⃣3️⃣🔤0️⃣0️⃣ граємо в 3️⃣ гри одночасно: Підготовка: 2 енергоса, 1 кава, 1 заспокійливе Ігри: Hearthstone, Clash Royale, Шахи... Гравці: Свят, Стас, Славік upd: судоми через 15 хв стріма для сабів ✅ Twitch | 🎵 TikTok | 🤩 YouTube

9🔥2😁1

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Republishes

Channels on the register whose posts this channel has forwarded.

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.

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

“Святогніздя (Sviaks)” (@sviaks), 78 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/sviaks.

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.