Telegram RegisterThe public register of Telegram
Telegram profile photo for ♡⃘ ‌ׄ m a r g o c h k a 。

Channel

♡⃘ ‌ׄ m a r g o c h k a 。

@margochk_a

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

85subscribers

+0 since we began measuring on 28 August 2026

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

Register entry

Telegram ID-1001223156637
TypeChannel
Username@margochk_a
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded28 August 2026
Last confirmed live12 September 2026
Measurements held2
Confirmed unchanged3 times, most recently 12 September 2026
On Telegramt.me/margochk_a

Growth

8528 Aug 2026, 16:47 — 85 subscribers28 Aug 2026, 21:05 — 85 subscribers28 Aug 2026, 16:4728 Aug 2026, 21:05
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 84–86 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Aug 2026, 21:0585no change
28 Aug 2026, 16:4785first reading

Engagement

13 posts held, back to 5 June 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 10 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

212 reactions across 12 posts, in 6 distinct kinds. The most used accounts for 25.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52043336864256555275525.9%
custom 54629890251512983065023.6%
custom 52314225562626401924822.6%
custom 53935398635365014702913.7%
custom 5952017450332590604178.02%
custom 5334968548412367183136.13%

Custom emoji. Every row above is a 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 212 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 5 June 2026 to 10 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

10 Jul 2026, 08:14 UTC326 views33 reactionsread 28 August 2026
Photo

🖕

custom 523142255626264019217custom 53935398635365014709custom 52043336864256555277

9 Jul 2026, 15:13 UTC79 views4 reactionsread 28 August 2026

Я подушки не нарисовала, но он лежит вххыхыхы

custom 53935398635365014704

9 Jul 2026, 15:12 UTC80 views5 reactionsread 28 August 2026

Позже полноценку замучу 🫡

custom 54629890251512983065

9 Jul 2026, 15:11 UTC67 views33 reactionsread 28 August 2026
Photo

С днем рождения, Кавех, емае🤪🤪🤪

custom 523142255626264019222custom 52043336864256555277custom 54629890251512983064

27 Jun 2026, 13:11 UTC98 views14 reactionsread 28 August 2026
Photo

Пока что разрисовываемся 🫡

custom 539353986353650147014

27 Jun 2026, 13:10 UTC91 views17 reactionsread 28 August 2026
Photo

Любимка🖕

custom 533496854841236718313custom 52043336864256555274

25 Jun 2026, 04:39 UTC135 views21 reactionsread 28 August 2026
Photo

Гспд, я защитилась… вымученная 4😫 Хочу еще доработать фасады, но главное что сдала. Держите пару более менее норм виз проекта.. наконец-то я смогу опять начать рисовать, а то три недели к планшету не прикасалась

custom 546298902515129830619custom 53935398635365014702

11 Jun 2026, 13:19 UTC132 views9 reactionsread 28 August 2026

У нас сейчас с ребятами голодные игры)) до защиты осталось 10 дней😇

custom 54629890251512983069

11 Jun 2026, 13:18 UTC128 views13 reactionsread 28 August 2026
Photo

У меня уже в глазах рябит от этих осей…. Когда-нибудь я сдам диплом…. и смогу спокойно жить…😫😫

custom 59520174503325906048custom 52043336864256555273custom 54629890251512983062

6 Jun 2026, 03:58 UTC149 views38 reactionsread 28 August 2026
Photo

Какие-то супер быстрые фаедеи😎

custom 520433368642565552719custom 52314225562626401929custom 59520174503325906046custom 54629890251512983064

5 Jun 2026, 16:18 UTC134 views9 reactionsread 28 August 2026

У меня возвращается гиперфикс на хёнлуков….. аватарка канала поддерживает эту авантюру

custom 52043336864256555276custom 54629890251512983063

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

“♡⃘ ‌ׄ m a r g o c h k a 。” (@margochk_a), 85 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/margochk_a.

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.