Telegram RegisterThe public register of Telegram
Telegram profile photo for - #𝗠𝗘¡𝗙𝗘𝗗𝗥𝗢𝗡! ○°

Channel

- #𝗠𝗘¡𝗙𝗘𝗗𝗥𝗢𝗡! ○°

@mirtyg

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

185subscribers

+28 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-1001518150490
TypeChannel
Username@mirtyg
Created9 August 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded8 August 2026
Last confirmed live7 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/mirtyg

Growth

1551851707 August 2026 — 157 subscribers8 August 2026 — 155 subscribers8 August 2026 — 155 subscribers14 August 2026 — 162 subscribers23 August 2026 — 173 subscribers29 August 2026 — 178 subscribers7 September 2026 — 185 subscribers7 August 20267 September 2026
7 measurements spanning 31 days, net +28. 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 151–190 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Sept 2026, 14:37185+7
29 Aug 2026, 15:27178+5
23 Aug 2026, 06:04173+11
14 Aug 2026, 21:35162+7
8 Aug 2026, 18:46155no change
8 Aug 2026, 09:04155-2
7 Aug 2026, 19:55157first reading

Engagement

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

Reaction mix

42 reactions across 8 posts, in 9 distinct kinds. The most used accounts for 26.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53596730585650622181126.2%
custom 5359778993933412705716.7%
custom 5251286045567252018614.3%
custom 5258472951782607267614.3%
custom 5357263955574160907511.9%
37.14%
❤‍🔥24.76%
custom 525121129595643417712.38%
💔12.38%

Custom emoji. 6 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 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 8 of the 20 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 42 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 31 July 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, 21:25 UTC24 viewsread 8 August 2026
Photo

Photo, posted without a caption

Signed ` ° 17 ¡!

7 Aug 2026, 21:25 UTC24 viewsread 8 August 2026

хз но главное премку и звезды не покупать

Signed ` ° 17 ¡!

7 Aug 2026, 21:25 UTC24 viewsread 8 August 2026

сейчас буду делать бизнес. !!!куплю вам премку и звёзды с белорусской карты!!!

Signed ` ° 17 ¡!

6 Aug 2026, 21:19 UTC33 viewsread 8 August 2026

мне надо как-то почистить телефон от ненужной фигни, мне кажется, легче умереть

Signed ` ° 17 ¡!

3 Aug 2026, 20:47 UTC68 views7 reactionsread 8 August 2026

🙏 Love - это когда белоруска приезжает в РФ, и её подруга из этой страны пытается помочь найти нормальный VPN/мод, чтобы работал TT (с учётом того, что у одной Android, а у другой iPhone) Оказывается надо было оставлять свои любимые Нидерланды #лераятебялюблю

2custom 53596730585650622182custom 52584729517826072671custom 53572639555741609071custom 53597789939334127051

Signed ` ° 17 ¡!

3 Aug 2026, 18:05 UTC58 viewsread 8 August 2026
Photo

ало, я в Нидерландах, какого хуя

Signed ` ° 17 ¡!

3 Aug 2026, 18:05 UTC60 viewsread 8 August 2026

Это буквально название улицы в бобре

Signed ` ° 17 ¡!

3 Aug 2026, 18:05 UTC62 viewsread 8 August 2026

Телефон барахлит, намекни своим хахалям

Signed ` ° 17 ¡!

3 Aug 2026, 11:26 UTC58 views2 reactionsread 8 August 2026

Вот бы еще написал

custom 52584729517826072672

Signed ` ° 17 ¡!

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“- #𝗠𝗘¡𝗙𝗘𝗗𝗥𝗢𝗡! ○°” (@mirtyg), 185 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/mirtyg.

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.