Telegram RegisterThe public register of Telegram
Telegram profile photo for M1NtY_SS

Channel

M1NtY_SS

@MINTY_SS

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

36subscribers

+2 since we began measuring on 10 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003868360986
TypeChannel
Username@MINTY_SS
CreatedBetween 1 February 2026 and 29 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live1 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 1 September 2026
On Telegramt.me/MINTY_SS

Growth

32363410 August 2026 — 34 subscribers11 August 2026 — 34 subscribers25 August 2026 — 32 subscribers1 September 2026 — 36 subscribers10 August 20261 September 2026
4 measurements spanning 22 days, net +2. 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 31–37 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Sept 2026, 04:4836+4
25 Aug 2026, 13:5932-2
11 Aug 2026, 00:3234no change
10 Aug 2026, 07:0134first reading

Engagement

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

Reaction mix

60 reactions across 11 posts, in 4 distinct kinds. The most used accounts for 56.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53956738137425440693456.7%
custom 52737332325782804882033.3%
58.33%
🍓11.67%

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 11 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 60 reactions 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 29 March 2026 to 4 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

4 Aug 2026, 19:39 UTC20 views1 reactionsread 11 August 2026

Поиграть в майнкрафт или порисовать… #щп

custom 53956738137425440691

4 Aug 2026, 10:46 UTC25 viewsread 11 August 2026

Нормальных артов не будет,я ушла в запой #щп

4 Aug 2026, 10:22 UTC28 views5 reactionsread 11 August 2026
Photo

«Давай нарисуем коллаб» #арт ???

custom 52737332325782804883custom 53956738137425440692

3 Aug 2026, 19:22 UTC26 views1 reactionsread 11 August 2026

Гартик не хотите? #щп

custom 53956738137425440691

1 Aug 2026, 18:56 UTC32 views6 reactionsread 11 August 2026

Заебали,возвращаюсь к вайбу тоскливых русреал артов #щп

custom 52737332325782804883custom 53956738137425440693

22 Jul 2026, 23:23 UTC126 views12 reactionsread 11 August 2026
Photo

Пока эти двое..Потом ещё поскетчу возможно 😻 #sketch

custom 52737332325782804886custom 53956738137425440696

22 Jul 2026, 21:46 UTC59 viewsread 11 August 2026

Я анон добавила кстати.. По поводу коллабов и трейдов туда,соглашаться буду не на все так как времени не особо много есть🌟 #щп

22 Jul 2026, 21:16 UTC57 views6 reactionsread 11 August 2026
Photo

РЕКВЕСТЫ ДРУНЫ🙂 Под этот пост можете закинуть своих осов,буду их скетчить,несколько штучек точно отрисую!!!😄 #щп

custom 53956738137425440694custom 52737332325782804882

22 Jul 2026, 21:01 UTC66 views6 reactionsread 11 August 2026
Photo

Ты и есть монстр.💧 #art #oc

custom 53956738137425440696

20 Jul 2026, 21:31 UTC51 views5 reactionsread 11 August 2026
Photo

Я не знаю кто это 0-0 Но рисовала другу 💧 #art

custom 53956738137425440693custom 52737332325782804882

14 Jul 2026, 20:05 UTC81 viewsread 11 August 2026

https://t.me/+l6m4q4BSfcs4YTc6 У меня новый щп…🙂

Showing the 12 most recent of 15 posts we hold for @MINTY_SS. 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 1 registered channel — 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.

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

“M1NtY_SS” (@MINTY_SS), 36 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/MINTY_SS.

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.