Telegram RegisterThe public register of Telegram

Channel

m1she44ka

@m1she44ka

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

308subscribers

+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-1002820718251
TypeChannel
Username@m1she44ka
Descriptionстримы, кружки и всякое гавно twitch.tv/m1she44ka https://t.me/okuratnenkiysell моя группа^
CreatedBetween 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/m1she44ka

Growth

3087 Aug 2026, 19:29 — 308 subscribers8 Aug 2026, 07:48 — 308 subscribers7 Aug 2026, 19:298 Aug 2026, 07:48
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 307–309 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 07:48308no change
7 Aug 2026, 19:29308first reading

Engagement

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

What this channel posts

Photos
82
Videos
1
Links
87

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

Reaction mix

114 reactions across 12 posts, in 7 distinct kinds. The most used accounts for 32.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54408956403662279533732.5%
custom 54384703754133913683429.8%
custom 54382988601893919591412.3%
1311.4%
custom 543823119297964475487.02%
👍43.51%
🤨43.51%

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

Measured over the 15 most recent posts we hold, published 30 May 2026 to 25 June 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.

Telegram Stars

Stars received
5
across the posts below
Posts paid on
1
of 14 we hold a reading for · 7%
Most on one post
5
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @m1she44ka. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 15 most recent posts we hold for this entry, published 30 May 2026 to 25 June 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

25 Jun 2026, 15:03 UTC202 views21 reactions5 Starsread 8 August 2026
Photo

Всем ку! Давно не запускал стримы, накопилось много дел вне компьютера, поэтому немного выпал из активности. Но сегодня хочу представить вам проект — @okuratnenkiysell Мы долго работали над тем, чтобы всё грамотно организовать и оформить, и вот что получилось. Я также буду принимать участие в развитии сообщества и выступать гарантом сделок. Все сделки будут проходить под моим контролем, поэтому всё будет максималь

13👍4🤨4

11 Jun 2026, 08:59 UTC276 views2 reactionsread 8 August 2026

начинаем смотреть первые матчи stage 3 twitch.tv/m1she44ka

custom 54384703754133913682

10 Jun 2026, 22:12 UTC294 views8 reactionsread 8 August 2026
Photo

сегодня в 12:00 продолжаем смотреть STAGE 3 💵💸💶🪙 всех жду!!

custom 54382311929796447548

9 Jun 2026, 11:47 UTC254 views2 reactionsread 8 August 2026
Photo

через 15 минут, смотрим монте пейн продолжаем лудить, поднимать деньги twitch.tv/m1she44ka

custom 54408956403662279532

7 Jun 2026, 18:36 UTC276 views2 reactionsread 8 August 2026

смотрим ласт матч FUT vs G2 twitch.tv/m1she44ka

custom 54382988601893919592

6 Jun 2026, 11:30 UTC313 views3 reactionsread 8 August 2026

тестово подрублю мажор, будем болеть за леху666, и аккуратно попробуем поднять денег⌨️ twitch.tv/m1she44ka

custom 54382988601893919593

1 Jun 2026, 18:01 UTC465 views19 reactionsread 8 August 2026
Photo

Київ❤️

custom 543847037541339136819

1 Jun 2026, 13:41 UTC363 views27 reactionsread 8 August 2026
Photo

Вот и закончился наш уикенд в Одессе. Провели время на 10/10, все было просто на высшем уровне. Жаль что не сыграли на сцене, но ничего в следующий раз обязательно будем. Отдельный респект всему стафу OneTab просто лучшие люди, и городу Одессе за такой приятный вайб.

custom 544089564036622795319custom 54382988601893919594custom 54384703754133913684

31 May 2026, 14:45 UTC174 views10 reactionsread 8 August 2026
Forwarded from @sijeyy_ofPhoto

🌟гивчик на 5 футболок okura🌟 🌟Условия: Быть подписанным на канал m1she44ka Быть подписанным на канал vanyak3k Быть подписанным на канал Sijeyy Тыкни кнопку «участвую!» Делаем чилловый на недельку, где-то в 21:00 разыграем, с победителем свяжусь👍

custom 544089564036622795310

31 May 2026, 12:14 UTC295 views5 reactionsread 8 August 2026
Photo

мы все тут на месте

custom 54408956403662279535

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

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

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

“m1she44ka” (@m1she44ka), 308 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/m1she44ka.

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.