20 Aug 2026, 19:05 UTC24 viewsread 21 August 2026
Photo
🎁🎁🎁
Channel
𝐌𝐀𝐈𝐒𝐊𝐘𝐄ᴵᶰᶠᵒ
@MA1SK1E
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
119subscribers
+4 since we began measuring on 21 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003210027717 |
|---|---|
| Type | Channel |
| Username | @MA1SK1E |
| Created | 27 October 2025 — measured — dated from the channel’s first post |
| First recorded | 21 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/MA1SK1E |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 11:40 | 119 | -1 |
| 5 Sept 2026, 07:38 | 120 | +2 |
| 29 Aug 2026, 03:36 | 118 | +1 |
| 22 Aug 2026, 23:39 | 117 | +2 |
| 21 Aug 2026, 19:15 | 115 | first reading |
Engagement
10 posts held, back to 27 October 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 10 posts for this entry, the most recent from 20 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 49s
- Average length
- 49s
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.
Recent posts
20 Aug 2026, 19:05 UTC24 viewsread 21 August 2026
Sticker
Sticker, posted without a caption
20 Aug 2026, 12:47 UTC32 viewsread 21 August 2026
Video
#V1DEO от MAISKIH. Creator :: @KRMM_224 Видео было выложено в наш тт. ✨
29 Dec 2025, 17:28 UTC588 viewsread 21 August 2026
Sticker
Sticker, posted without a caption
29 Dec 2025, 17:26 UTC659 viewsread 21 August 2026
Photo
MAISKIE – . . . Это не просто пространство, а то самое уникальное место, где абсолютно каждый человек сможет найти себя. Каждый может в любой момент присоединиться, чтобы ощутить это необыкновенное, ни с чем не сравнимое чувство искреннего тепла, уюта и абсолютной внутренней свободы. 𝗔𝗗𝗠𝗜𝗡 𝗣𝗔𝗧𝗘𝗡𝗧 𝗥𝗨𝗟𝗘𝗦 𝗧𝗜𝗞 𝗧𝗢𝗞 𝗚𝗔𝗠𝗘 …
8 Nov 2025, 20:13 UTC731 viewsread 21 August 2026
Sticker
Sticker, posted without a caption
8 Nov 2025, 20:13 UTC765 viewsread 21 August 2026
Photo
Что вам нужно, чтобы вашу заявку приняли : ✔️Быть подписаным на Канал. ✔️Прочитать Правила. ✔️Поставить Инициал. ✔️Написать Администрации об вступлении, чтобы он проверил все пункты и дал Вам ссылку на чат. Все условия проверяются перед принятием в чат.
8 Nov 2025, 19:25 UTC502 viewsread 21 August 2026
Sticker
Sticker, posted without a caption
8 Nov 2025, 19:24 UTC497 viewsread 21 August 2026
➿➿➿ 𝙋𝘼𝙏𝙀𝙉𝙏 ➿➿➿ С сегодняшнего дня название < 𝑀𝐴𝐼𝑆𝐾𝑌𝐸 > и все оформление с 8 ноября 2025 года (08.11.2025) принадлежит исключительно нашей конференции. ➖➖➖ При любом увиденном совпадении можем попросить что-либо сменить. С уважением, администрация Майских.
27 Oct 2025, 19:26 UTCviews —
Channel created
Showing the 10 most recent of 10 posts we hold for @MA1SK1E. 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 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.
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.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“𝐌𝐀𝐈𝐒𝐊𝐘𝐄ᴵᶰᶠᵒ” (@MA1SK1E), 119 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/MA1SK1E.
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.