19 Jul 2022, 21:32 UTCviews —
𝐌𝐀𝐒𝐓𝐄𝐑𝐈𝐘 pinned a photo
Channel
𝐌𝐀𝐒𝐓𝐄𝐑𝐈𝐘
@masteriyshd
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
2subscribers
+0 since we began measuring on 27 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001784364929 |
|---|---|
| Type | Channel |
| Username | @masteriyshd |
| Description | •по всем вопросам писать владельцу - @shadow_sf |•админы по союзам{рп}– ?? |•админы по нью— ?? |•админ чата– @ovverluv |
| Created | 19 May 2022 — measured — dated from the channel’s first post |
| First recorded | 27 August 2026 |
| Last confirmed live | 18 October 2026 |
| Measurements held | 2 |
| On Telegram | t.me/masteriyshd |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 15:30 | 2 | no change |
| 27 Aug 2026, 15:16 | 2 | first reading |
Engagement
9 posts held, back to 19 May 2022 — 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 9 posts for this entry, the most recent from 19 July 2022. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 3
- Links
- 1
Lifetime counters from Telegram’s own channel header, read 27 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.
Recent posts
19 Jul 2022, 21:32 UTC133 views0 reactionsread 27 August 2026
Photo
•|||Navigation 𝙼𝙰𝚂𝚃𝙴𝚁𝙸𝚈 •|Chat Rules|채팅 규칙 • {правила чата} •|Questionnaire template|설문지 템플릿 • {шаблон анкеты} •|Union Rules|연합 규칙 • {правила союза} •|Checklist of unions|노동 조합의 체크리스트 • { лист¹ , лист²} •|Initial|초기 • {наш инициал} •|Participants|참가자 • { } ____ •|||Hashtags|해시태그 •#ᶰᵉʷᵐᵉᵐᵇᵉʳˢᵈʰ - нью •#ᵛᶦᵈᵉᵒˢᵈʰ - видео •#ʳᵉᵖᵒˢᵗˢᵈʰ - репост •#ᵏᶠˢᵈʰ - инфо для участников
Signed ::teon
19 Jul 2022, 21:26 UTCviews —
Channel name was changed to «𝐌𝐀𝐒𝐓𝐄𝐑𝐈𝐘»
19 Jul 2022, 21:09 UTC97 viewsread 27 August 2026
Photo
•|||UNION @masteriyshd ____ ° ° ° ° ° ° ° ° ° ° ° ° ° ° ° ° ° ° ° ° ° ° ° ° ° ° ° ° [0] ___ |•союз 0+
Signed sᴏꜰᴀ ʜᴀɴˢᵈʰ°ʳᶫᵛ
19 Jul 2022, 21:08 UTC67 viewsread 27 August 2026
Photo
•|||Union Rules|연합 규칙 ___ •|Рп постов с хэштегом #ʳᵉᵖᵒˢᵗˢᵈʰ / #ᵛᶦᵈᵉᵒˢᵈʰ •|Рп пост держится на канале два дня •|Удаляем рп без предупреждения •|Админ должен взаимно подписаться •|Не выкладываем рп в субботу и воскресенье •|Пожалуйста , предупредите о ресте или о смене юза •|Союз от 0+ •|Не выкладываем не нужную информацию •|Пост о заключении союза держим час •|Админы по союзам • ___ {|так же ищу админов по с…
Signed sᴏꜰᴀ ʜᴀɴˢᵈʰ°ʳᶫᵛ
19 Jul 2022, 20:55 UTC58 viewsread 27 August 2026
새로운 회원 new member!ˢᵈʰ ╰⸺➤ |your name•ваше имя| 환영 彡 |ваш статус| 彡 |возраст| 彡 |персонаж| 彡 |орентация| 彡 |позиция| #ᶰᵉʷᵐᵉᵐᵇᵉʳˢᵈʰ #ᵐᵃˢᵗᵉʳᶦʸ 𓆏 #ˢᵈʰ |ваш юзернейм| •так же прислать 2 фотографии 1:1• •админ по нью - ?? так же присылать мне @shadow_sf
Signed sᴏꜰᴀ ʜᴀɴˢᵈʰ°ʳᶫᵛ
19 Jul 2022, 20:54 UTC54 viewsread 27 August 2026
•|Чистка проводится раз в месяц по первым числам| Норма соо: День - 25 Неделя - 175 Месяц - 750 Неактив 3 дня - бан ____ | У рестников нормы нет |
Signed sᴏꜰᴀ ʜᴀɴˢᵈʰ°ʳᶫᵛ
19 Jul 2022, 20:53 UTC57 viewsread 27 August 2026
•||| rules for masteriy ___ |«просим уважать всех админов, владельца, участников, тк это правда очень важно» |«при смене: юза, персонажа, любой информации о себе в анкете, или об уходе из кф/в рест – предупреждать» | «ссоры, конфликты – разрешены, только до того момента, пока владелец/админ не скажет прекратить» | «не использовать призыв, а именно ”калл„ просто так» |«быть активным на протяжении всей недели, но …
Signed sᴏꜰᴀ ʜᴀɴˢᵈʰ°ʳᶫᵛ
19 May 2022, 10:36 UTCviews —
Channel created
Showing the 9 most recent of 9 posts we hold for @masteriyshd. 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.
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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“𝐌𝐀𝐒𝐓𝐄𝐑𝐈𝐘” (@masteriyshd), 2 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/masteriyshd.
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.