Telegram RegisterThe public register of Telegram
Telegram profile photo for TgSk45 18+🐉🥦| WLW 🫶🐉🥦

Channel

TgSk45 18+🐉🥦| WLW 🫶🐉🥦

@tgsk45_22

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

302subscribers

+0 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-1002377842687
TypeChannel
Username@tgsk45_22
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 13 September 2026
On Telegramt.me/tgsk45_22

Growth

2903022966 August 2026 — 302 subscribers6 August 2026 — 302 subscribers7 August 2026 — 300 subscribers14 August 2026 — 298 subscribers21 August 2026 — 290 subscribers7 September 2026 — 299 subscribers13 September 2026 — 302 subscribers6 August 202613 September 2026
7 measurements spanning 38 days. 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 288–304 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Sept 2026, 18:37302+3
7 Sept 2026, 01:17299+9
21 Aug 2026, 07:45290-8
14 Aug 2026, 01:47298-2
7 Aug 2026, 00:37300-2
6 Aug 2026, 22:32302no change
6 Aug 2026, 17:33302first reading

Engagement

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

Reaction mix

566 reactions across 14 posts, in 11 distinct kinds. The most used accounts for 50.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
28650.5%
custom 51954012539616356528014.1%
custom 5195022905997564482468.13%
❤‍🔥335.83%
🔥325.65%
custom 5303279875975586261264.59%
custom 5368529040611240606223.89%
🦄173.00%
custom 5334943422853699123111.94%
🎉111.94%
💘20.353%

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

Measured over the 14 most recent posts we hold, published 25 July 2026 to 5 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

5 Aug 2026, 22:53 UTC88 views51 reactionsread 6 August 2026
Photo

Новый референс к Шарпу!

28❤‍🔥11custom 519540125396163565210custom 51950229059975644821custom 53685290406112406061

2 Aug 2026, 19:37 UTC198 views46 reactionsread 6 August 2026
Photo

Решил сделать новый референс для Шарпа, такой же как я сейчас делаю своим заказчикам Ну и для сравнения, старый реф и лайн к новому Пх, почти ничего не поменялось

30custom 530327987597558626110❤‍🔥3custom 53349434228536991232custom 51950229059975644821

2 Aug 2026, 17:43 UTC186 views30 reactionsread 6 August 2026
Photo

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

🦄168💘2custom 51954012539616356522❤‍🔥1custom 53685290406112406061

1 Aug 2026, 19:27 UTC186 views46 reactionsread 6 August 2026
Photo

Что-то я решил нарисовать какого-нибудь большого бота на продажу, мне нравится его расцветка Мне интересно рисовать трёхрежимников

37custom 53032798759755862614custom 51950229059975644823❤‍🔥1custom 53349434228536991231

31 Jul 2026, 22:53 UTC165 views44 reactionsread 6 August 2026
Photo

С Первым днём последнего месяца лета! Я вам принес небольшой скетчик А ещё начинаю отчёт до 22 августа, ух, день рождения уже не за горами

26🎉11custom 51950229059975644826custom 53349434228536991231

30 Jul 2026, 19:46 UTC176 views26 reactionsread 6 August 2026

Ребятки, напоминаю, у меня можно заказать коммишку! А ещё я всегда готов идти на встречу и сделать небольшую скидочку

21custom 53349434228536991232custom 51950229059975644821custom 53032798759755862611custom 53685290406112406061

30 Jul 2026, 15:24 UTC226 views42 reactionsread 6 August 2026
Photo

Готовый референс для @VihattuInkvisiittori

custom 51954012539616356522710custom 53685290406112406062❤‍🔥1🔥1custom 51950229059975644821

30 Jul 2026, 12:05 UTC186 views21 reactionsread 6 August 2026

Ребята, тут всего два комментария, напишите, пожалуйста, ещё что-нибудь⁉

custom 5195401253961635652165

29 Jul 2026, 17:40 UTC204 views53 reactionsread 6 August 2026
Photo

Кстати, забыл выложить, моя часть с Шарпом отдельно Драма с Дриллом продолжается

custom 51950229059975644822513custom 53032798759755862617custom 51954012539616356524custom 53349434228536991232❤‍🔥1custom 53685290406112406061

29 Jul 2026, 07:55 UTC572 views55 reactionsread 6 August 2026
Photo

Огромное спасибо всем за участие в коллабе!! С вами было очень приятно работать! 1 @brocco45 (ТГК: @tgsk45_22 ) ‌2 @Winterhummel (ТГК: @winterschmetterlinge ) ‌3 @RustedAshes (ТГК: @Rusted_Ashes ) ‌4 @u_hayang (ТГК: @hayanglovely ) ‌5 @Mamkin_lizer (ТГК: @the_yelloweyed ) ‌6 @Bruhabiliti (ТГК: @AsIWasAlwaysThere ) ‌7 @BratanCyda (ТГК: @makistr_vudu ) ‌8 @Buttercup_2007 (ТГК: @strawberry_049 ) ‌9 @SuNderaArt1

🔥2711custom 51954012539616356527custom 51950229059975644826custom 53349434228536991233❤‍🔥1

28 Jul 2026, 22:29 UTC188 views44 reactionsread 6 August 2026
Photo

Я немного сегодня скетчами побаловался Мне сон приснился вчера в сеттинге викингов, вот решил порисовать

25custom 519540125396163565211custom 53032798759755862613custom 53685290406112406063❤‍🔥1custom 51950229059975644821

28 Jul 2026, 17:24 UTC221 views20 reactionsread 6 August 2026
Photo

Давайте небольшой интерактивчик) Судя по моим последним работам можно сказать, что автор очень продажен😂 Мне разрешили стырить пикчу)

16🔥4

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

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

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

“TgSk45 18+🐉🥦| WLW 🫶🐉🥦” (@tgsk45_22), 302 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/tgsk45_22.

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.