Telegram RegisterThe public register of Telegram

Channel

•°{РЕСТ}°•🌌~𝙱𝚢𝚗𝚔𝚎𝚛 𝙼𝚊𝚒𝚝~🌌

@Maitiiik

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

55subscribers

+0 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-1002671191543
TypeChannel
Username@Maitiiik
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live10 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/Maitiiik

Growth

5510 Aug 2026, 13:34 — 55 subscribers10 Aug 2026, 22:43 — 55 subscribers10 Aug 2026, 13:3410 Aug 2026, 22:43
2 measurements taken within a single day. 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 54–56 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 22:4355no change
10 Aug 2026, 13:3455first reading

Engagement

15 posts held, back to 28 May 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
97.3%
avg views ÷ 55 subscribers
Avg views / post
53.5
4 posts measured
Reaction rate
7.01%
reactions ÷ views · ER floor
Posts in window
5
of 15 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 20 July 2026
Posts held15 (28 May 202620 July 2026)
Views total214
Reactions total15
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 13:34 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
5m 27s
Average length
2m 44s

Measured directly from 2 videos 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.

Reaction mix

42 reactions across 12 posts, in 8 distinct kinds. The most used accounts for 31.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1331.0%
🕊1023.8%
💊716.7%
🥰511.9%
🔥37.14%
🍌24.76%
🍓12.38%
😨12.38%

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 12 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 42reactions 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 28 May 2026 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.

Recent posts

20 Jul 2026, 15:22 UTCviews —

Channel name was changed to «•°{РЕСТ}°•🌌~𝙱𝚢𝚗𝚔𝚎𝚛 𝙼𝚊𝚒𝚝~🌌»

20 Jul 2026, 14:55 UTC61 views7 reactionsread 10 August 2026
Photo

Пожалуй я уйду в рест примерно на месяц, т.к прямо сейчас сижу в поезде, еду в любимый Братск💞

5🔥2

Signed 𝙱𝚊𝚛𝚋 || 𝚃𝚅 || !!

20 Jul 2026, 14:52 UTC54 views2 reactionsread 10 August 2026
Video message

Video message, posted without a caption

🥰2

Signed 𝙱𝚊𝚛𝚋 || 𝚃𝚅 || !!

20 Jul 2026, 14:46 UTC52 views4 reactionsread 10 August 2026
Video

классное и кайфовое выступление.🤩

4

Signed ​𝑲𝒊𝒍𝒍#𝒘𝒊𝒑𝒊𝒅𝒐𝒓.

18 Jul 2026, 08:33 UTC47 views2 reactionsread 10 August 2026

Ну что ж... Уже завтра состоится отчетный концерт от нш. Завтра буду выступать, снова чуть-чуть волнуюсь, но надеюсь что выступлю хорошо. Пока не знаю в каком блоке я буду выступать, предположительно во втором. Либо завтра вечером либо утром в понедельник выложу видео своего выступления. Готовилась долго, за время подготовки сменился преподаватель по причине своего увольнения🥲 Сегодня ген.репетиция, надеюсь все прой

1🔥1

Signed 𝙱𝚊𝚛𝚋 || 𝚃𝚅 || !!

2 Jul 2026, 06:06 UTC77 viewsread 10 August 2026
Forwarded from @fan_buggyPhoto

🤩🤩💋💋 🤩🤩💋💋🤩🤩🤩🤩 🤩🤩💋🤩🤩🤩🤩🤩 💋💋𝘔𝘺 𝘴𝘶𝘪𝘵 𝘸𝘢𝘴 𝘯𝘦𝘷𝘦𝘳 𝘢 𝘧𝘢𝘤𝘢𝘥𝘦 💋𝘰𝘳 𝘢 𝘩𝘰𝘣𝘣𝘺; 𝘱𝘦𝘳𝘩𝘢𝘱𝘴 𝘪𝘵 𝘸𝘢𝘴 𝘢 𝘤𝘰𝘤𝘰𝘰𝘯, 𝘰𝘳 𝘮𝘢𝘺𝘣𝘦 𝘢 𝘯𝘦𝘸 𝘣𝘦𝘨𝘪𝘯𝘯𝘪𝘯𝘨, 𝘢𝘯𝘥 𝘧𝘳𝘰𝘮 𝘯𝘰𝘸 𝘰𝘯, 𝘐 𝘢𝘮 𝘢 𝘥𝘪𝘧𝘧𝘦𝘳𝘦𝘯𝘵 𝘱𝘦𝘳𝘴𝘰𝘯. 𝘠𝘰𝘶 𝘤𝘢𝘯 𝘵𝘢𝘬𝘦 𝘢𝘸𝘢𝘺 𝘮𝘺 🎰🎰 𝘩𝘰𝘮𝘦, 𝘢𝘭𝘭 𝘮𝘺 𝘨𝘢𝘥𝘨𝘦𝘵𝘴 𝘢𝘯𝘥 𝘵𝘰𝘺𝘴, 𝘣𝘶𝘵 𝘵𝘩𝘦𝘳𝘦 𝘪𝘴 𝘰𝘯𝘦 𝘵𝘩𝘪𝘯𝘨 𝘺𝘰𝘶 𝘤𝘢𝘯𝘯𝘰𝘵 𝘵𝘢𝘬𝘦 𝘢𝘸𝘢𝘺: 🌸🌸 🌸 🌸 🌸🕷️ 🤩🤩🤩🤩𝘐 𝘢𝘮 𝘐𝘳𝘰𝘯 𝘔𝘢𝘯. 🤩 🤩 🤩 🤩💋💋💋

Signed 𝙱𝚊𝚛𝚋 || 𝚃𝚅 || !!

25 Jun 2026, 14:37 UTC99 views2 reactionsread 10 August 2026
Photo

Возможно я занимаюсь какой-то хернёй... Но это не точно...

💊2

Signed 𝙱𝚊𝚛𝚋 || 𝚃𝚅 || !!

24 Jun 2026, 16:19 UTC100 views3 reactionsread 10 August 2026

У меня появилось совершенно спонтанное желание закосплеить Кауфмо из уцц....

3

Signed 𝙱𝚊𝚛𝚋 || 𝚃𝚅 || !!

20 Jun 2026, 04:48 UTC106 viewsread 10 August 2026
Forwarded from @Dom_irishkPhoto

😒🤩🤩🤩🤩🤩🤩🤩 💋💋💋💋💋 💋💋💋💋💋 !FAKE KNIFE! 🤩🤩🤩 -something is.. 🤩🤩🤩 wrong with me 🤩🤩🤩 🤩🤩🤩 -a car.. hit a stay 🤩🤩🤩 animal in the 🤩🤩middle of street and the blood.. got on me🤩 🤩🤩🤩🤩🤩🤩🤩🤩🤩 🤩🤩🤩рт/реакции?💕 🤩🤩🤩cosplayer: mochi

Signed 𝙱𝚊𝚛𝚋 || 𝚃𝚅 || !!

10 Jun 2026, 18:38 UTC113 views3 reactionsread 10 August 2026
Forwarded from @Dom_irishkVideo

🕊️💞🕊️🕊️ 🕊️🕊️🕊️🕊️🕊️🕊️ —это второе дефиле, после батла (первое вроде никто не снимал). на самом деле было прикольно поучаствовать в лайфе вдвоем, мы с Мейт почти не готовились, но думаю все равно получилось неплохо 🌟🌟, правда с музыкой опять не повезло 🌟 большое спасибо человечку из подслушки, который снимал большинство дефиле😘

🥰3

Signed 𝙱𝚊𝚛𝚋 || 𝚃𝚅 || !!

7 Jun 2026, 04:02 UTC210 views3 reactionsread 10 August 2026
Photo

‧͙⁺˚*・༓☾ 𝐴𝑁𝑂𝑁𝑆 ☽༓・*˚⁺‧͙ Уже сегодня я с прекрасной Моти будем на игровом кефире в косплеях на... °•°•°•°•🖤𝐵𝑜𝑟𝑡 𝑎𝑛𝑑 𝐷𝑖𝑎𝑚𝑜𝑛𝑑🤍•°•°•°•° До встречи!! 💞

🍌2🍓1

Signed 𝙱𝚊𝚛𝚋 || 𝚃𝚅 || !!

6 Jun 2026, 14:49 UTC122 views3 reactionsread 10 August 2026

К сожалению завтра у меня не получится прити на кефир в косплее на Пейнвил, так как появилась небольшая проблема на счет платья, так что завтра буду в другом косплее Анонс вероятнее всего будет утром

🕊3

Signed 𝙱𝚊𝚛𝚋 || 𝚃𝚅 || !!

Showing the 12 most recent of 15 posts we hold for @Maitiiik. 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.

Citation-graph rank

Citation-graph rank — 1,238,415 of 1,340,412entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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.

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

“•°{РЕСТ}°•🌌~𝙱𝚢𝚗𝚔𝚎𝚛 𝙼𝚊𝚒𝚝~🌌” (@Maitiiik), 55 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/Maitiiik.

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.