Telegram RegisterThe public register of Telegram
Telegram profile photo for Лохматый Шуш

Channel

Лохматый Шуш

@TWFkk

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

50subscribers

-3 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-1002170693806
TypeChannel
Username@TWFkk
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live18 September 2026
Measurements held4
Confirmed unchanged3 times, most recently 18 September 2026
On Telegramt.me/TWFkk

Growth

505351.511 August 2026 — 53 subscribers11 August 2026 — 52 subscribers25 August 2026 — 51 subscribers1 September 2026 — 50 subscribers11 August 20261 September 2026
4 measurements spanning 22 days, net -3. 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 50–53 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Sept 2026, 16:3450-1
25 Aug 2026, 15:1951-1
11 Aug 2026, 23:2552-1
11 Aug 2026, 04:1653first reading

Engagement

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

What this channel posts

Video runtime
3m 09s
Average length
1m 35s

Measured directly from 2 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

58 reactions across 11 posts, in 8 distinct kinds. The most used accounts for 55.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3255.2%
custom 5427292534047018832813.8%
custom 5366389751760851269712.1%
🔥35.17%
🥰35.17%
🍾23.45%
🕊23.45%
🤯11.72%

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

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

26 Jul 2026, 08:10 UTC37 views4 reactionsread 11 August 2026

Я ушла на новый канал Тут активности больше не будет💔 Если кто-то хочет перейти в новый канал пишите мне, дам ссылку🍦

🕊21🥰1

24 Jul 2026, 06:50 UTC43 views8 reactionsread 11 August 2026
Photo

обновленный реф Гварда✋

5🥰2🤯1

23 Jul 2026, 08:41 UTC46 views6 reactionsread 11 August 2026
Video

Спидпейнт к этой работе я опять забыла включить сразу запись так что начало на этапе лайна 🙂

5custom 54272925340470188321

21 Jul 2026, 13:49 UTC49 views2 reactionsread 11 August 2026

я хочу продать этого персонажа, я не хочу его развивать 🪑

2

20 Jul 2026, 13:08 UTC50 views5 reactionsread 11 August 2026
Photo

Трейд с любимой Саней 1 фото - моя часть 2 фото - ее часть

2custom 54272925340470188322custom 53663897517608512691

19 Jul 2026, 07:04 UTC46 views7 reactionsread 11 August 2026
Video

У меня есть не полный спидпейнт работы В приложении нет автоматической записи процесса как в Ибисе, я сама включила когда вспомнила🙂 Вобщем вот процесс покраса В следующих работах я уже записываю таймлапс (правда иногда забываю)

4🔥2custom 54272925340470188321

18 Jul 2026, 08:30 UTC122 views13 reactionsread 11 August 2026
Photo

Мне сегодня исполняется 17 лет😊

8🍾2custom 54272925340470188322🔥1

18 Jul 2026, 08:30 UTC42 viewsread 11 August 2026

За этот год очень много произошло. Я благодарна моим подписчикам за теплые слова поддержки под моими артами🩷 Вы - самая главная мотивация дальше творить Спасибо что вы со мной🙏

17 Jul 2026, 18:44 UTC47 views6 reactionsread 11 August 2026
Photo

Новый Референс Ганса😋

custom 536638975176085126941custom 54272925340470188321

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

“Лохматый Шуш” (@TWFkk), 50 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/TWFkk.

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.