Telegram RegisterThe public register of Telegram
Telegram profile photo for MAISON

Channel

MAISON

@MAISON_NFT

On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

172subscribers

-42 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1004103519275
TypeChannel
Username@MAISON_NFT
Created5 June 2026measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live17 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/MAISON_NFT

Growth

1722141938 August 2026 — 214 subscribers8 August 2026 — 214 subscribers16 August 2026 — 206 subscribers24 August 2026 — 193 subscribers31 August 2026 — 186 subscribers9 September 2026 — 179 subscribers17 September 2026 — 172 subscribers8 August 202617 September 2026
7 measurements spanning 41 days, net -42. 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 166–220 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 22:00172-7
9 Sept 2026, 00:36179-7
31 Aug 2026, 13:52186-7
24 Aug 2026, 20:54193-13
16 Aug 2026, 06:11206-8
8 Aug 2026, 10:49214no change
8 Aug 2026, 07:15214first reading

Engagement

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

Reaction mix

235 reactions across 6 posts, in 14 distinct kinds. The most used accounts for 20.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🦄4920.9%
custom 51953571016978103163715.7%
🔥2711.5%
2510.6%
custom 5192815967117263680239.79%
🥰239.79%
custom 5192887465437838577198.09%
🎉83.40%
custom 519519637113669037262.55%
❤‍🔥52.13%
custom 519537745554782500941.70%
🍌41.70%
🍓31.28%
🥱20.851%

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

Measured over the 8 most recent posts we hold, published 5 June 2026 to 19 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.

Recent posts

19 Jul 2026, 20:56 UTC30 viewsread 8 August 2026

10 НОВЫХ МИШЕК 🧸 перешли 3 друзьям и шансы увеличиться на 50%

19 Jul 2026, 20:14 UTC125 views11 reactionsread 8 August 2026
Photo

10 НОВЫХ МИШЕК - БЕСПЛАТНО 🧸 @MAISON_NFT БЕЗ РЕАКЦИЙ НЕ ВЫДАМ 🎁

🦄11

12 Jun 2026, 08:03 UTC266 views4 reactionsread 8 August 2026

Результаты конкурса: Победители: 1. Сифби (@Managkol) 2. ℕ𝕠ℕ𝕒𝕞𝕖 (@Durak666) 3. s.sanich (@realsanich) Проверить результаты

🦄4

7 Jun 2026, 08:07 UTC638 views119 reactionsread 8 August 2026

3 МИШКИ - БЕЗ УСЛОВИЙ 🥰 БЕЗ РЕАКЦИЙ НЕ ВЫДАМ 🎁

custom 519535710169781031635🦄32custom 519281596711726368023custom 519288746543783857719custom 51951963711366903726custom 51953774555478250094

6 Jun 2026, 10:39 UTC999 views42 reactionsread 8 August 2026

Каждый кто перекинет конкурс в свой канал или в 25 чатов дам 100 ⭐️ Скрины кидать - @adelina_nft

🔥12🥰117❤‍🔥5🍌4🍓3

6 Jun 2026, 10:38 UTC≈2,430 views57 reactionsread 8 August 2026

Розыгрыш на Telegram Premium | NFT🎁 1 место - Telegram Premium на 1 год.🤩 2 место - Telegram Premium на 1 год.🤩 3 место - Telegram Premium на 1 год.🤩 4 место - Telegram Premium на 1 год.🤩 5 место - Telegram Premium на 3 месяца.🤩 6 место - Telegram Premium на 3 месяца.🤩 7 место - Telegram Premium на 3 месяца.🤩 8 место - Telegram Premium на 1 месяца.🤩 9 место - Telegram Premium на 1 месяца.🤩 10 место - NFT👁

18🔥15🥰12🎉8🥱2custom 51953571016978103162

Showing the 8 most recent of 8 posts we hold for @MAISON_NFT. 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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“MAISON” (@MAISON_NFT), 172 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/MAISON_NFT.

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.