Telegram RegisterThe public register of Telegram
Telegram profile photo for REST — REWRITE

Channel

REST — REWRITE

@Rewrite_VN

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

43subscribers

+10 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003958161276
TypeChannel
Username@Rewrite_VN
CreatedBetween 1 April 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live2 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/Rewrite_VN

Growth

3343387 August 2026 — 33 subscribers11 August 2026 — 33 subscribers14 August 2026 — 34 subscribers20 August 2026 — 38 subscribers27 August 2026 — 40 subscribers2 September 2026 — 43 subscribers7 August 20262 September 2026
6 measurements spanning 27 days, net +10. 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 32–45 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Sept 2026, 20:3843+3
27 Aug 2026, 07:0540+2
20 Aug 2026, 08:5338+4
14 Aug 2026, 01:4734+1
11 Aug 2026, 01:1633no change
7 Aug 2026, 07:1833first reading

Engagement

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

Reaction mix

10 reactions across 3 posts, in 6 distinct kinds. The most used accounts for 30.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5449906937019789552330.0%
custom 5283274326332695593220.0%
custom 5447199531370312521220.0%
custom 5447320911441065449110.0%
110.0%
🕊110.0%

Custom emoji. 4 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 3 of the 20 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 10 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 31 July 2026 to 9 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

9 Aug 2026, 06:35 UTC13 viewsread 11 August 2026

🔣🤩🌟🌟🤩🔣 🌟ROLEPLAY ➿➿➿➿➿➿➿➿➿➿➿ Отметив для себя беспокойство Дискорда, Реврайт сперва не стал вмешиваться. Аудитор ответил быстрее него, да и сказал всё по факту. Понемногу ёж стал отвлекаться, то и дело посматривая в разные стороны. Больше всего его внимание перетянули чайки на берегу. Они что-то кричали и вскоре улетели. Тут то до ушей Реврайта донёсся вопрос об отношении драконикуса к нему. Ещё и заданный так, слов

8 Aug 2026, 15:11 UTC14 viewsread 11 August 2026

🔣🤩🌟🌟🤩🔣 🌟ROLEPLAY ➿➿➿➿➿➿➿➿➿➿➿ К появлению Дискорда Реврайт отнёсся лучше. С драконикусом у него не было конфликтов, хоть тот и показывал неприязнь к ёжику. Так что на приветствие он дружелюбно помахал На вопрос он пока что не стал отвечать. А вот напиток из интереса попробовал, но после первого же глотка отставил в сторону. Тем временем обстановка между Биллом и Аудитором накалилась настолько, что первый исчез. — Мо

7 Aug 2026, 18:41 UTC16 viewsread 11 August 2026

🔣🤩🌟🌟🤩🔣 🌟ROLEPLAY ➿➿➿➿➿➿➿➿➿➿➿ Хоть он и ожидал подвоха, но такая подлянка стала сюрпризом. Рожок точечно прилетел в лоб ежу и затем свалился на песок. — Серьёзно? Жаль ты не материален, так бы вернул твой подарочек. Проворчал он, убирая остатки мороженого со своего сосуда. Однако теперь его рука была испачкана в нём. Но это не беда, он просто отсоединил конечность и отправил её отмыться в воде у берега. Реврайт отр

7 Aug 2026, 17:15 UTC13 viewsread 11 August 2026

🔣🤩🌟🌟🤩🔣 🌟ROLEPLAY ➿➿➿➿➿➿➿➿➿➿➿ Ёжик сам не особо был рад Аудитору, точно так же косясь на него, когда тот подошёл к ним. Но он тактично проигнорировал "тучку", лишь махнул ушком, словно отгоняя муху. Подперев мордашку рукой, Реврайт наблюдал за тем как недавно пришедший пробует мороженое. Однако внезапное предложение этого самого мороженного удивило божество. Аудитор, да мирно предлагающий отдать не понравившийся десе

7 Aug 2026, 15:11 UTC15 viewsread 11 August 2026

🔣🤩🌟🌟🤩🔣 🌟ROLEPLAY ➿➿➿➿➿➿➿➿➿➿➿ Отдых проходил замечательно. Реврайт гулял по курорту, изучая, что тут есть. Весь первый день он потратил на то, чтобы обойти большую часть этого места. Были найдены ларьки, кафе, отель и достаточно прочего В конце концов он таки нашёл Билла. Треугольник под большим таким же треугольным зонтиком. Не долго думая, ёжик к нему подлетел — Приветики! А вот и я Чуть ли не пропел он, усаживая

6 Aug 2026, 10:07 UTC15 views4 reactionsread 11 August 2026

Замечательное однако здесь место! Жара, конечно, непривычная, но в целом терпимо. Уже успел тут немного погулять. Напитки классные, надеюсь никто не против был, что я стащил их, не заплатив. В любом случае, платить мне нечем Пойду-ка поищу Билла. Будет замечательно, если по пути не наткнусь на всяких ворчунов

custom 52832743263326955932custom 54471995313703125211custom 54499069370197895521

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

Republishes

Channels on the register whose posts this channel has forwarded.

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 27 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. The 21 listed below are the most frequent namers; the rest are counted above but not each listed.

Named by

Channels on the register whose posts name this channel's handle.

[Rest] BIGBADAUD999
@KillThatDamnHankGuys_VN · 49
2 posts
THE ᘜOᗪ of falls
@BILLCIPHER_VN · 41
1 post
⌗ !! ꒰ F_0r K.. P3-N0N4L' ꒱
@BlaVirus_VN · 31
1 post
[REST] Columbina.
@columbinavn · 30
1 post
Рестᅠᅠ𝑫𝒓. 𝑴𝒂𝒔𝒂𝒄𝒓𝒊𝒌 - \\#🫁
@DrMasacrikVN · 38
1 post
[rest]『𝑭𝒍𝒖𝒕𝒕𝒆𝒓𝒔𝒉𝒚🐰』
@FluttershyHC · 32
1 post
GLaDOS's public relations service
@GLaDOS_public_service_1_VN · 60
1 post
Rest — RADIANT THEIA
@heeHeephis_VN · 34
1 post
𝑻𝒉𝒆 𝑴𝒂𝒏 𝒊𝒏 𝒕𝒉𝒆 𝑯𝒊𝒈𝒉 𝑪𝒂𝒔𝒕𝒍𝒆
@MstHouse_VLNET · 48
1 post
| 𝗜𝗟𝗟𝗨𝗦𝗜𝗢𝗡𝗜𝗦𝗧 𝗡𝗨𝗠𝗕𝗘𝗥 𝗢𝗡𝗘
@mysterio_vn · 35
1 post
[рест]👁️ᖘ𐌴𐍄𐌴𐍂 𐌱𐌳𐍂𐌽🏚️
@Peter_The_PumpkinVN · 36
1 post
рест 𝓢𝓪𝓲𝓸𝓷𝓳𝓲'𝓼 𝓫𝓵𝓸𝓰, 𝓸𝓴𝓪𝔂?
@SaionjiHC · 19
1 post
𝘚𝘦𝘢 𝘰𝘧 𝘋𝘦𝘢𝘵𝘩 𝘼𝙢𝙗𝙖𝙨𝙨𝙖𝙙𝙤𝙧。(𝗦𝖺𝗅)
@SAL_VN · 37
1 post
А КАК КАНАЛ МНЕ УДАЛИТЬ???(рест) ⤿⌢𝐌ᴀʀɪᴏɴᴇᴛᴛᴇ. 『🔩』
@Sandrone_VN · 33
1 post
Half-rest||Solid Horn.
@SolidHornVn · 34
1 post
[wheres he] the ceo . ꔛ
@stevecobs_vnet · 12
1 post
Рестᅠᅠ𝑳0𝒓𝒅 o̶̶F̶̶ 𝗖𝗛𝗔𝗢𝗦. | 𝘋𝘪𝘴𝘤𝘰𝘳𝘥 ` #
@TheBestDiscord_VN · 37
1 post
VILLAIN.NET
@VILLAINNET · 362
1 post
Архив WHEATLEY!!!
@Wheatley_VN · 48
1 post
▷ᕕᗰᗴᖇᖴIᗴᕗ
@YourBestFriend_VN · 40
1 post
аааррххиииивввв///)#единицаабьюзерша|YULIA CHANNEL
@YuliaBoltik_HC · 19
1 post

Names

Channels on the register whose handles appear in this channel's posts.

THE ᘜOᗪ of falls
@BILLCIPHER_VN · 41
2 posts
Рестᅠᅠ@𝐵𝑙𝑖𝑡𝑧∅ | 𝑁𝑜 "𝑂" - #🔥
@BlitzoVN · 37
2 posts
[Rest] BIGBADAUD999
@KillThatDamnHankGuys_VN · 49
2 posts
(Рест)Accelerator (TDS)
@accelerator_top_HC · 42
1 post
⌗ !! ꒰ F_0r K.. P3-N0N4L' ꒱
@BlaVirus_VN · 31
1 post
Рестᅠᅠ𝑫𝒓. 𝑴𝒂𝒔𝒂𝒄𝒓𝒊𝒌 - \\#🫁
@DrMasacrikVN · 38
1 post
𝖯𝗂𝗇𝗄 𝖳𝗁𝗋𝖾𝖺𝗍 🎀
@EMYrose_HC · 25
1 post
GLaDOS's public relations service
@GLaDOS_public_service_1_VN · 60
1 post
i still love you.
@GOD_GRACE_HC · 29
1 post
Rest — RADIANT THEIA
@heeHeephis_VN · 34
1 post
⚡LIZZIE >33
@LIZZIESCHANNELFOR_FUN_HC · 37
1 post
𝑻𝒉𝒆 𝑴𝒂𝒏 𝒊𝒏 𝒕𝒉𝒆 𝑯𝒊𝒈𝒉 𝑪𝒂𝒔𝒕𝒍𝒆
@MstHouse_VLNET · 48
1 post
| 𝗜𝗟𝗟𝗨𝗦𝗜𝗢𝗡𝗜𝗦𝗧 𝗡𝗨𝗠𝗕𝗘𝗥 𝗢𝗡𝗘
@mysterio_vn · 35
1 post
[рест]👁️ᖘ𐌴𐍄𐌴𐍂 𐌱𐌳𐍂𐌽🏚️
@Peter_The_PumpkinVN · 36
1 post
Архив| мя разобрали💀ℝ𝔼ℕℤ𝕆 𝕋ℍ𝔼 𝔻𝔼𝕊𝕋ℝ𝕆𝕐𝔼ℝ
@RENZOTHEDESTROYER_VN · 19
1 post
Sinner №4.
@ryoshu_vn · 35
1 post
𝘚𝘦𝘢 𝘰𝘧 𝘋𝘦𝘢𝘵𝘩 𝘼𝙢𝙗𝙖𝙨𝙨𝙖𝙙𝙤𝙧。(𝗦𝖺𝗅)
@SAL_VN · 37
1 post
Half-rest||Solid Horn.
@SolidHornVn · 34
1 post
REST | Tᴀᴍsʏ Cᴀɪɴᴇs | A̷̛͎̱̣ ̼n̵̨̡͖̠̤͕̘͇͖͈̪̭̬̲͙̩̾͋͒̅̂̾̏̔́̎̔̀͜g̷͠ ̧̛̟̺̗̝͈̭̹̜̺͓͊̐̌̒e̷͔̣̚l̵̯̻͓̩̖̣̭̥̩̭̙̺͉̀̇ͅ
@TamsyCaines_VN · 34
1 post
Рестᅠᅠ𝑳0𝒓𝒅 o̶̶F̶̶ 𝗖𝗛𝗔𝗢𝗦. | 𝘋𝘪𝘴𝘤𝘰𝘳𝘥 ` #
@TheBestDiscord_VN · 37
1 post
VILLAIN.NET
@VILLAINNET · 362
1 post
Архив WHEATLEY!!!
@Wheatley_VN · 48
1 post
▷ᕕᗰᗴᖇᖴIᗴᕗ
@YourBestFriend_VN · 40
1 post
аааррххиииивввв///)#единицаабьюзерша|YULIA CHANNEL
@YuliaBoltik_HC · 19
1 post

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

“REST — REWRITE” (@Rewrite_VN), 43 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/Rewrite_VN.

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.