Telegram RegisterThe public register of Telegram
Telegram profile photo for снежанчик

Channel

снежанчик

@fuenderkk

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

111subscribers

-6 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002903125183
TypeChannel
Username@fuenderkk
CreatedBetween 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live8 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/fuenderkk

Growth

1111171146 August 2026 — 117 subscribers9 August 2026 — 117 subscribers14 August 2026 — 113 subscribers30 August 2026 — 112 subscribers8 September 2026 — 111 subscribers6 August 20268 September 2026
5 measurements spanning 33 days, net -6. 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 110–118 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 06:55111-1
30 Aug 2026, 03:57112-1
14 Aug 2026, 03:38113-4
9 Aug 2026, 05:02117no change
6 Aug 2026, 17:49117first reading

Engagement

16 posts held, back to 20 March 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 16 posts for this entry, the most recent from 28 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

338 reactions across 16 posts, in 4 distinct kinds. The most used accounts for 34.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤‍🔥11534.0%
🍓9126.9%
💘8926.3%
🎉4312.7%

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

Measured over the 16 most recent posts we hold, published 20 March 2026 to 28 July 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

28 Jul 2026, 11:19 UTC56 views18 reactionsread 9 August 2026
Photo

еще я забываю постоянно эту картинку выложить, это реквест лизы батончик который она написала в моем щитпосте, вы тоже можете там написать что вы хотите чтобы я нарисовала и я это нарисую 🥺 ( обещаю что нарисую, просто не сразу ) #данганронпа

🎉10🍓5❤‍🔥2💘1

28 Jul 2026, 11:15 UTC58 views13 reactionsread 9 August 2026
Photo

он действительно крутой и тд #ЮТТД

❤‍🔥8💘3🍓2

20 Jul 2026, 12:42 UTC95 views16 reactionsread 9 August 2026
Photo

не захожу в хср уже года два и понятия не имею что там происходит, просто тихонечько симплю по жуань мэй 🥹

💘10🍓5❤‍🔥1

11 Jul 2026, 21:04 UTC100 views14 reactionsread 9 August 2026
Forwarded from @privchonkiPhoto

С ДНЕМ РОЖДЕНИЯ СНЕЖА поздравьте снежу все

🍓8🎉4💘2

11 Jul 2026, 21:04 UTC112 views9 reactionsread 9 August 2026

МНЕ НРАВИТСЯ ОЧЕНЬ СИЛЬНО

🍓6🎉2💘1

10 Jul 2026, 19:59 UTC≈1,280 views9 reactionsread 9 August 2026
Photo

ДРУЗЬЯ!! я все забываю вам сказать, но я буду на хокку 12 июля как помощница у лизы за 15 столиком и принесу немного вот такого вот своего первого мерча 👅👅 так что кто планировал идти обязательно приходите к нам!!! а еще у меня день рождения в этот день 🙏😭 приносите ящик пива по возможности

💘8🍓1

20 Jun 2026, 10:48 UTC189 views20 reactionsread 9 August 2026
Photo

мозг чето вспоминает... хочу с ними мерч #ЮТТД

💘14❤‍🔥4🍓2

14 Jun 2026, 21:26 UTC207 views19 reactionsread 9 August 2026
Photo

чето типа картинки #отельхазбин

💘12🍓4❤‍🔥3

25 Apr 2026, 07:11 UTC302 views23 reactionsread 9 August 2026
Photo

the same five songs #отельхазбин

💘14❤‍🔥6🍓3

6 Apr 2026, 21:39 UTC298 views12 reactionsread 9 August 2026
Photo

ребята у меня для вас новость я создала ЩИТПОСТ https://t.me/snezhapizdit всем кто хочет следить за моей жизнью подписываться !!!! я долго думала делать его или нет потому что сомневалась что кому-то это будет интересно но сегодня решила что мне пох ... если что я планирую там периодически жаловаться на всех кто меня выбесит, будьте готовы

❤‍🔥9🍓2💘1

6 Apr 2026, 21:04 UTC212 views16 reactionsread 9 August 2026
Photo

это кокичи ома он всегда срет 😭😭😭 #данганронпа

❤‍🔥11🍓5

31 Mar 2026, 19:52 UTC229 views36 reactionsread 9 August 2026
Photo

не отписывайтесь я скоро закончу свои эксперименты 😭😭 вторая тема хобби !! #отельхазбин #staticmothweek

❤‍🔥23🍓8💘5

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

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

“снежанчик” (@fuenderkk), 111 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/fuenderkk.

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.