Channel
@mt_trademark
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
7subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003043952457 |
|---|---|
| Type | Channel |
| Username | @mt_trademark |
| Description | https://www.instagram.com/mt__________tm |
| Created | 14 September 2025 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/mt_trademark |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 16:46 | 7 | no change |
| 7 Aug 2026, 03:48 | 7 | first reading |
12 posts held, back to 14 September 2025 — 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 12 posts for this entry, the most recent from 20 July 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 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.
25 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 56.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5337261528372512340 | 14 | 56.0% | |
| custom 5190682871609712455 | 9 | 36.0% | |
| ❤ | 2 | 8.00% |
Custom emoji. 2 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 9 of the 12 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 25 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 14 September 2025 to 20 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.
бардак. 23.07 Бутербродная daily slime artemy samoletov dima shapkin isportish dj mt lexxxus Каменноостровский пр-ск 10Б 25.07 Чёртики GUTTA dj set mi6 artemy samoletov isportish ximia aroroirora grachik dj mt lexxxus eqlipse kiddy kohan qqquincy audiomess grachik дмитрий бетонин билеты на входе Невский пр-кт 35д
custom 51906828716097124551custom 53372615283725123401
Saint Petersbuurghhh🤝
custom 51906828716097124551custom 53372615283725123401
💀
File, posted without a caption
custom 51906828716097124555custom 53372615283725123403
🤔
custom 51906828716097124552custom 53372615283725123402
🎈
13 Февраля | ОР Live: jdflag jessie luck fbs n01r w/ artemy samoletov sabina DJ: soal ergsors apocyram isportish b2b dj mt b2b lexxxus raremotherfucker dubstepbass0k Москва, Самокатная 4с1 Шизич 21:00 — 04:00 FC/DC 18+ Poster: noumbrellarainwalking & isportish Билеты ⠀
custom 53372615283725123401
Сегодня играю 👐🎶 @trvtrvtrvtrvtrvtrv
custom 53372615283725123402
Video message, posted without a caption
custom 53372615283725123402❤1
Сегодня @opemopem
custom 53372615283725123402❤1
20 СЕНТЯБРЯ | ОР ❗ VALENTIN FUFAEV KALIONE ARSCHY RISU JANNISE + FBS JESSIE LUCK + CLAYT CARTER live KAYMEERA ISPORTISH + LEXXXUS DJ MT 21:00 — 3:30 Fabula Radio (Новая уличная площадка) Москва, Самокатная 4Бс2 FC/DC 18+ Билеты по ссылке ниже или на входе Цена — 800 ₽ (на входе подорожание) БИЛЕТЫ Афиша — isportish & i________l_____
Channel created
Showing the 12 most recent of 12 posts we hold for @mt_trademark. 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.
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.
Named by 2 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
@mt_trademark named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“MT™” (@mt_trademark), 7 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/mt_trademark.
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.