Telegram RegisterThe public register of Telegram

Channel

گـوزەشـت💔!

@Guz4sht

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

43subscribers

+0 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-1001744053686
TypeChannel
Username@Guz4sht
CreatedBetween 1 December 2021 and 29 September 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/Guz4sht

Growth

4311 Aug 2026, 01:46 — 43 subscribers11 Aug 2026, 16:56 — 43 subscribers11 Aug 2026, 01:4611 Aug 2026, 16:56
2 measurements taken within a single 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 42–44 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 16:5643no change
11 Aug 2026, 01:4643first reading

Engagement

20 posts held, back to 29 September 2022the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 5 December 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
17s
Average length
17s

Measured directly from 1 video 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

437 reactions across 11 posts, in 15 distinct kinds. The most used accounts for 16.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🥰7116.2%
6514.9%
🔥6414.6%
👏5612.8%
👍5412.4%
😁439.84%
🎉429.61%
92.06%
🏆92.06%
🐳81.83%
👌71.60%
🤩51.14%
😐20.458%
❤‍🔥10.229%
🌚10.229%

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 11 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 437reactions 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 29 September 2022 to 5 December 2025, 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 Dec 2025, 15:21 UTC21 viewsread 11 August 2026

کەمنتـ نەما دەزانی کەس بۆت ناسوتی وەک موم لەباوەشی هەر کەس بیت شەویک دلتەنگ دەبی بۆم💔☺️!

9 Jun 2025, 18:26 UTC73 views2 reactionsread 11 August 2026

بمکوژن بە گـــولــەیــەکــــــ بــەڵـــام دایکم بریندار مەکەن بە وشەیەکــــ...! 🥹❤️‍🩹

❤‍🔥1🌚1

7 May 2025, 20:40 UTC66 viewsread 11 August 2026

تۆ بەس حەبیبی دڵ نیت حەبیبی ڕوحم و وجودمی🫀!

15 Apr 2025, 22:08 UTC83 viewsread 11 August 2026

عەباس کەمەندی دەڵیت... دوو دڵۆپ باران ئەبارێت بۆ لای جلەکانی سەر تەناف ڕا ئەکەیت، ئەی بۆ بۆ فرمێسکەکانی من وانیت؟🥲

3 Apr 2025, 22:22 UTC72 views2 reactionsread 11 August 2026

دووجار هەمان کەست دەست ناکەوێتەوە تەنانەت لە هەمان کەسیشدا

🔥2

29 Mar 2025, 21:11 UTC77 viewsread 11 August 2026

ئەگەر ڕۆژێک قەبرم دەست نەکەوت دێم و لە ناو باوەشت دا دەمرم🫠"

24 Mar 2025, 17:43 UTC88 views1 reactionsread 11 August 2026

بۆم گرینگ نییە چەند کاتی ئەوێ تا ببین بە هی یەک ئەوە گرینگە تەنها یەکمان بوێ

🔥1

19 Mar 2025, 01:54 UTC88 views2 reactionsread 11 August 2026

ئەگەر بتوانم یەک شەو تا بەیانی لە باوەشت بخەوم ئیتر بۆم گرینگ نییە بەیانیەکەی هەڵدەستمەوە یان نا”♥️

2

25 Mar 2024, 23:32 UTC411 viewsread 11 August 2026

ئەزانی تۆ زۆر جوان لەمن هاتووی💍🤎🔥

20 Mar 2024, 21:38 UTC384 viewsread 11 August 2026

هێندە بەمردووی ژیاوم جلەکانم بۆنی کفنیان لێدێ'ھ•!🖤

17 Feb 2024, 00:31 UTC417 views2 reactionsread 11 August 2026

بەتۆ ناڵێم « ژیانم » ژیانی من هیچ کات هیندەی تۆ جوان نەبووە♥️•

2

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

Citation-graph rank

Citation-graph rank — 1,361,363 of 1,478,351entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

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

“گـوزەشـت💔!” (@Guz4sht), 43 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/Guz4sht.

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.