Telegram RegisterThe public register of Telegram

Channel

𝐳𝐚𝐠𝐢𝐠𝐮𝐞𝐞𝐧/перешла

@zagigueen

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

22subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002597854858
TypeChannel
Username@zagigueen
Descriptionnew canals: @lce_s
CreatedBetween 1 March 2025 and 29 April 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/zagigueen

Growth

227 August 2026 — 22 subscribers11 August 2026 — 22 subscribers7 August 202611 August 2026
2 measurements spanning 4 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 21–23 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 12:3422no change
7 Aug 2026, 15:5822first reading

Engagement

19 posts held, back to 29 April 2025the 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 19 posts for this entry, the most recent from 15 August 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
15
Videos
2
Links
7

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

Video runtime
40s
Average length
20s

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

118 reactions across 10 posts, in 13 distinct kinds. The most used accounts for 24.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🍓2924.6%
1512.7%
💅1210.2%
custom 5195075884419139605119.32%
👻119.32%
custom 532578319820916577275.93%
🕊75.93%
💋65.08%
💔65.08%
🆒54.24%
🍾43.39%
👾32.54%
💘21.69%

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

Measured over the 19 most recent posts we hold, published 29 April 2025 to 15 August 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

30 Jul 2025, 21:11 UTC43 viewsread 11 August 2026
Forwarded from @vnliaxPhoto

—no time to die #billieeilish #processing 🌃 @vnliax/ . . . vanilla

21 Jun 2025, 15:39 UTCviews —

𝐳𝐚𝐠𝐢𝐠𝐮𝐞𝐞𝐧/перешла pinned «ХХААХХАХ, НОВЫЦ ТГК @vnliax»

5 May 2025, 18:06 UTC197 viewsread 11 August 2026

всем привет!я к вам с новостью,но возможно для некоторых она окажется плохой. приятного чтения! итак..я все таки решила так скажем закрыть канал,и перейти на другой,так как на этом канале я чувствую себя некомфортно,и будто этот канал не мой,и не я его создала. хочу рассказать о том как я его вообще создавала. в 2025 году 13 апреля я все таки решилась на свой собственный канал,смотря за другими-я мечтала о нем. с

4 May 2025, 08:52 UTC206 views5 reactionsread 11 August 2026

111-красивое число⭐️ спасибо!

🍓3🍾1💅1

3 May 2025, 15:40 UTC193 views6 reactionsread 11 August 2026

не написала о том что уйду в рест,ну так вот:я ухожу в рест на 5-6 дней,а может и меньше,так как у меня нехваток времени и завалы по учёбе-времени на канал почти нет,но посты будут-только колоры,или же какие либо обработки,так что в рест я ухожу 50/50.когда вернусь с реста,будут и колоры,и эдиты,и даже новая аватарка. надеюсь массовых отписок не будет🐈

💔6

3 May 2025, 14:42 UTCviews —

Channel name was changed to «𝐳𝐚𝐠𝐢𝐠𝐮𝐞𝐞𝐧./рест»

2 May 2025, 18:16 UTC188 views9 reactionsread 11 August 2026
Photo

🙂🙂🙂🙂🙂🙂🙂🙂🙂🙂 для красивейшего канала камилиевка! с чем у меня ассоциируется этот канал: 🔪фигуристка: Анна Щербакова 🤍фрукт/ягода: малина 🤍природ.явление: снегопад 🤍спорт: конный спорт спасибо за участие! остальные ассоциации завтра

💅3🆒3🍓2custom 53257831982091657721

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

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

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.

“𝐳𝐚𝐠𝐢𝐠𝐮𝐞𝐞𝐧/перешла” (@zagigueen), 22 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/zagigueen.

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.