Telegram RegisterThe public register of Telegram
Telegram profile photo for [Rest] 𝕀 𝔸𝕄 𝕋ℍ𝔼 ℝ𝔼𝔸𝕃 𝕊𝕆ℕ𝕀ℂ

Channel

[Rest] 𝕀 𝔸𝕄 𝕋ℍ𝔼 ℝ𝔼𝔸𝕃 𝕊𝕆ℕ𝕀ℂ

@METAL_SONIC_VN

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

34subscribers

+21 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-1004391963889
TypeChannel
Username@METAL_SONIC_VN
CreatedBetween 1 June 2026 and 6 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live16 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/METAL_SONIC_VN

Growth

133423.57 August 2026 — 13 subscribers7 August 2026 — 14 subscribers12 August 2026 — 14 subscribers14 August 2026 — 18 subscribers22 August 2026 — 21 subscribers30 August 2026 — 24 subscribers7 September 2026 — 29 subscribers16 September 2026 — 34 subscribers7 August 202616 September 2026
8 measurements spanning 40 days, net +21. 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 10–37 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 11:4034+5
7 Sept 2026, 17:3629+5
30 Aug 2026, 01:0424+3
22 Aug 2026, 18:3421+3
14 Aug 2026, 23:2518+4
12 Aug 2026, 00:3114no change
7 Aug 2026, 20:5514+1
7 Aug 2026, 07:1813first reading

Engagement

20 posts held, back to 6 August 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 11 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

7 reactions across 7 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53435852878952904817100.0%

Custom emoji. One row above is a 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 count beside it is 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 7 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 7 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 6 August 2026 to 11 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

11 Aug 2026, 01:21 UTC8 views1 reactionsread 12 August 2026

▰▰▰▰▰▰▰▰▰▰▰▰▰▰▰▰ [For navigation] ✨ >> #POST >> #EVENT >> #ROLEPLAY •———————MESSAGE————————• Метал лишь молча выслушал претензии Эми Роуз, которая все также возмущалась насчет личности Соника. Он смотрел на нее внимательно, замечая каждое ее движение, каждую деталь в ее внешнем виде. Что-то цепляло в этой ежихе самого Метала, но что именно - он и сам не знал. Однако, когда та заговорила про воду, робот повернул го

custom 53435852878952904811

11 Aug 2026, 01:21 UTC8 viewsread 12 August 2026

Live, camera, action. Protocol <kill the faker> active. ... ... Sonic, dead or alive I-I-IS MINE. 🤩

7 Aug 2026, 16:08 UTC17 views1 reactionsread 12 August 2026

▰▰▰▰▰▰▰▰▰▰▰▰▰▰▰▰ [For navigation] ✨ >> #POST >> #EVENT >> #ROLEPLAY •———————MESSAGE————————• Когда Метала назвали дураком, тот лишь что-то пробурчал в ответ на своем ломанном, отведя взгляд в сторону. Однако, когда та попросила отдохнуть по нормальному, то Метал.. Не знал, что ответить? Он и так не мог, само собой, но его пустая реакция, когда глаза лишь забегали по округе, будто пытается найти то, как он мог отдо

custom 53435852878952904811

7 Aug 2026, 16:08 UTC13 viewsread 12 August 2026

Live, camera, action. Protocol <kill the faker> active. ... ... Sonic, dead or alive I-I-IS MINE. 🤩

7 Aug 2026, 11:17 UTC14 views1 reactionsread 12 August 2026

▰▰▰▰▰▰▰▰▰▰▰▰▰▰▰▰ [For navigation] ✨ >> #POST >> #EVENT >> #ROLEPLAY •———————MESSAGE————————• Когда Эми отошла от Метала на шаг, его голова моментально повернулась в сторону противника за спиной. Его когтистые руки мгновенно образовали что-то подобие клетки. Однако, убедившись в "покорности" Печи после хорошей взбучки", через пару секунд, настоящий Соник вернул свою более спокойную позу, а взгляд вновь был направлен

custom 53435852878952904811

7 Aug 2026, 11:17 UTC8 viewsread 12 August 2026

Live, camera, action. Protocol <kill the faker> active. ... ... Sonic, dead or alive I-I-IS MINE. 🤩

6 Aug 2026, 20:47 UTC13 views1 reactionsread 12 August 2026

▰▰▰▰▰▰▰▰▰▰▰▰▰▰▰▰ [For navigation] ✨ >> #POST >> #EVENT >> #ROLEPLAY •———————MESSAGE————————• Когда Эми в действительности поблагодарила, Метал лишь отвел взгляд в сторону. Он в действительности не ожидал таких... Приятных слов. В какой-то мере, его это смутило, ибо чтобы ему был благодарен кто-то из команды Соника? Однако, не долго он думал. Когда та заговорила про отдых, взгляд Метала выражал конфуз, непонимание.

custom 53435852878952904811

6 Aug 2026, 20:47 UTC12 viewsread 12 August 2026

Live, camera, action. Protocol <kill the faker> active. ... ... Sonic, dead or alive I-I-IS MINE. 🤩

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

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 20 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 — RADIANT THEIA
@heeHeephis_VN · 36
2 posts
THE ᘜOᗪ of falls
@BILLCIPHER_VN · 46
1 post
⌗ !! ꒰ F_0r K.. P3-N0N4L' ꒱
@BlaVirus_VN · 33
1 post
[REST] Columbina.
@columbinavn · 32
1 post
Рестᅠᅠ𝑫𝒓. 𝑴𝒂𝒔𝒂𝒄𝒓𝒊𝒌 - \\#🫁
@DrMasacrikVN · 42
1 post
[rest]『𝑭𝒍𝒖𝒕𝒕𝒆𝒓𝒔𝒉𝒚🐰』
@FluttershyHC · 33
1 post
GLaDOS's public relations service
@GLaDOS_public_service_1_VN · 67
1 post
𝑻𝒉𝒆 𝑴𝒂𝒏 𝒊𝒏 𝒕𝒉𝒆 𝑯𝒊𝒈𝒉 𝑪𝒂𝒔𝒕𝒍𝒆
@MstHouse_VLNET · 53
1 post
| 𝗜𝗟𝗟𝗨𝗦𝗜𝗢𝗡𝗜𝗦𝗧 𝗡𝗨𝗠𝗕𝗘𝗥 𝗢𝗡𝗘
@mysterio_vn · 41
1 post
[полу-рест]👁️ᖘ𐌴𐍄𐌴𐍂 𐌱𐌳𐍂𐌽🏚️
@Peter_The_PumpkinVN · 40
1 post
REST — REWRITE
@Rewrite_VN · 48
1 post
рест 𝓢𝓪𝓲𝓸𝓷𝓳𝓲'𝓼 𝓫𝓵𝓸𝓰, 𝓸𝓴𝓪𝔂?
@SaionjiHC · 23
1 post
𝘚𝘦𝘢 𝘰𝘧 𝘋𝘦𝘢𝘵𝘩 𝘼𝙢𝙗𝙖𝙨𝙨𝙖𝙙𝙤𝙧。(𝗦𝖺𝗅)
@SAL_VN · 41
1 post
А КАК КАНАЛ МНЕ УДАЛИТЬ???(рест) ⤿⌢𝐌ᴀʀɪᴏɴᴇᴛᴛᴇ. 『🔩』
@Sandrone_VN · 33
1 post
Half-rest||Solid Horn.
@SolidHornVn · 39
1 post
[wheres he] the ceo . ꔛ
@stevecobs_vnet · 11
1 post
Рестᅠᅠ𝑳0𝒓𝒅 o̶̶F̶̶ 𝗖𝗛𝗔𝗢𝗦. | 𝘋𝘪𝘴𝘤𝘰𝘳𝘥 ` #
@TheBestDiscord_VN · 46
1 post
VILLAIN.NET
@VILLAINNET · 382
1 post
Архив WHEATLEY!!!
@Wheatley_VN · 47
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 16 September 2026 — this entry's latest reading, not the date you are reading this.

“[Rest] 𝕀 𝔸𝕄 𝕋ℍ𝔼 ℝ𝔼𝔸𝕃 𝕊𝕆ℕ𝕀ℂ” (@METAL_SONIC_VN), 34 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/METAL_SONIC_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.