Telegram RegisterThe public register of Telegram
Telegram profile photo for Minorik 🌿

Channel

Minorik 🌿

@MinorikVi

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

71subscribers

+1 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-1001672963888
TypeChannel
Username@MinorikVi
Created14 March 2023 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded10 August 2026
Last confirmed live18 September 2026
Measurements held3
Confirmed unchanged4 times, most recently 18 September 2026
On Telegramt.me/MinorikVi

Growth

707170.57 August 2026 — 70 subscribers10 August 2026 — 70 subscribers24 August 2026 — 71 subscribers7 August 202624 August 2026
3 measurements spanning 17 days, net +1. 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 70–71 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 20:0871+1
10 Aug 2026, 00:0170no change
7 Aug 2026, 19:5570first reading

Engagement

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

What this channel posts

Video runtime
26s
Average length
9s

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

57 reactions across 4 posts, in 9 distinct kinds. The most used accounts for 21.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52875926754306552611221.1%
custom 54631547550543498371119.3%
custom 5764753560512240296915.8%
custom 5235593214320197295712.3%
custom 5764676169496534088610.5%
custom 546082966591872750758.77%
custom 545442067276997774235.26%
custom 546776547975603398235.26%
custom 547192792583611444711.75%

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

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

8 Aug 2026, 15:40 UTC32 views15 reactionsread 10 August 2026
Photo

Сегодня ходила на хатха-йогу в потрясающий центр Yoga space по рекомендации волшебницы по волосам и главной йогини чата Alexmooonsun 🧘‍♂️ Занятие прошло очень здорово и понятно, даже несмотря на то, что я была впервые. Тренер Светлана Гордиенко ✨ очень доходчиво все объясняет и показывает, совсем не страшно ошибиться. Атмосфера 🌟🎁 студии располагает приходить туда еще и еще) все чисто, аккуратно, много всякого кла…

custom 57646761694965340886custom 54608296659187275074custom 52875926754306552613custom 54677654797560339822

1 Aug 2026, 16:24 UTC56 views11 reactionsread 10 August 2026
Photo

Summertime sadness Лето решило побаловать нас теплой погодой 🍀 И мы с Полиной отправились поплавать в бассейне в Сокольниках ❤️ Хорошее расположение, практически посреди леса. Тишина, приятный воздух, солнышко. Можно искупаться в двух бассейнах, посидеть в джакузи и заказать различных вкусняшек в кафе. Отлично и атмосферно провели время ❤️

custom 52875926754306552615custom 57647535605122402963custom 54544206727699777422custom 54631547550543498371

26 Jul 2026, 20:32 UTC79 views14 reactionsread 10 August 2026
Photo

Еще красоты 🤩🤩🥢☂️

custom 54631547550543498375custom 57647535605122402965custom 52355932143201972953custom 54608296659187275071

26 Jul 2026, 19:55 UTC72 views17 reactionsread 10 August 2026
Photo

Сегодня был чудесный, хоть и немного дождливый день ❤️ Встретились с любимой Полиной🐰 и отправились гулять. 🎎 Сначала была набережная от Воробьевых гор до парка Горького. 🎎 Потом розарий в Нескучном саду с потрясающими розами, аромат которых хотелось забрать с собой. 🎎 Остановились перекусить в Surf coffee. Полина наслаждалась кофе🤩а я перешла на матчу ☕ 🎎 Хотели прокатиться на кораблике, но передумали, т.к. пла…

custom 54631547550543498375custom 52355932143201972954custom 52875926754306552614custom 54544206727699777421custom 54677654797560339821custom 54719279258361144471custom 57647535605122402961

Showing the 4 most recent of 4 posts we hold for @MinorikVi. 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

Names

Channels on the register whose handles appear in this channel's posts.

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

“Minorik 🌿” (@MinorikVi), 71 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/MinorikVi.

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.