Telegram RegisterThe public register of Telegram
Telegram profile photo for муᴩᴛуз

Channel

муᴩᴛуз

@myrtyztigr

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

86subscribers

-576 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-1003840981166
TypeChannel
Username@myrtyztigr
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live14 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 14 September 2026
On Telegramt.me/myrtyztigr

Growth

861,0065467 August 2026 — 662 subscribers8 August 2026 — 662 subscribers16 August 2026 — 691 subscribers23 August 2026 — 804 subscribers31 August 2026 — 1,003 subscribers4 September 2026 — 1,006 subscribers10 September 2026 — 1,005 subscribers14 September 2026 — 86 subscribers7 August 202614 September 2026
8 measurements spanning 38 days, net -576. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Sept 2026, 08:0186-919
10 Sept 2026, 06:171,005-1
4 Sept 2026, 13:191,006+3
31 Aug 2026, 20:361,003+199
23 Aug 2026, 22:26804+113
16 Aug 2026, 07:08691+29
8 Aug 2026, 02:35662no change
7 Aug 2026, 19:28662first reading

Engagement

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

What this channel posts

Video runtime
4s
Average length
4s

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

157 reactions across 19 posts, in 7 distinct kinds. The most used accounts for 74.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤11774.5%
🕊117.01%
🔥95.73%
👍85.10%
💯53.18%
⚡42.55%
🍓31.91%

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 19 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 157 reactions 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 3 August 2026 to 7 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

7 Aug 2026, 08:41 UTC167 views5 reactionsread 8 August 2026
Forwarded from @tusyabonapartt

я туся передаю т3 чоко @usewordll фк

❤5

Signed муᴩᴛуз

7 Aug 2026, 08:41 UTC183 views4 reactionsread 8 August 2026
Forwarded from @tusyabonapartt

я туся передаю т2 елоу @noumode вин фк

❤4

Signed муᴩᴛуз

7 Aug 2026, 08:41 UTC186 views4 reactionsread 8 August 2026
Forwarded from @tusyabonapartt

я туся передаю т1 омск @wzwxv фк марар

❤4

Signed муᴩᴛуз

6 Aug 2026, 13:00 UTC324 views26 reactionsread 8 August 2026

Регаем жирный фк на т1 и тд? Реакций

❤24👍1🔥1

Signed муᴩᴛуз

6 Aug 2026, 13:00 UTC300 views4 reactionsread 8 August 2026

Я Муртуз передаю Т8 Gold дуэль игроку @Iztck

❤4

Signed муᴩᴛуз

6 Aug 2026, 12:12 UTC279 views14 reactionsread 8 August 2026

10 рк резко пока я фк регаю делаем!

❤11🔥2👍1

Signed муᴩᴛуз

6 Aug 2026, 12:11 UTC277 views4 reactionsread 8 August 2026

передаю т8 ростова @duxovi

❤4

Signed муᴩᴛуз

6 Aug 2026, 11:50 UTC269 views5 reactionsread 8 August 2026
Photo

Результаты конкурса: 🥳 Победитель: 1. M. (@PACCBET_MOCKBbl1) Проверить результаты

❤5

Signed Best Random Bot 🎁 [Конкурсный бот для розыгрышей | Рандомайзер]

5 Aug 2026, 21:52 UTC286 views4 reactionsread 8 August 2026
Video

силач

🕊2⚡1❤1

Signed муᴩᴛуз

5 Aug 2026, 13:24 UTC314 views23 reactionsread 8 August 2026

15 рк ещё фк го

❤15💯5🕊3

Signed муᴩᴛуз мᴀжоᴩный

5 Aug 2026, 13:23 UTC419 views3 reactionsread 8 August 2026

Я Муртуз передаю Т4 Ekb дуэль игроку @Axeors

❤3

Signed муᴩᴛуз мᴀжоᴩный

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

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

“муᴩᴛуз” (@myrtyztigr), 86 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/myrtyztigr.

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.