Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝙍𝙚𝙎𝙩𝙪𝙙𝙞𝙤𝙨

Channel

𝙍𝙚𝙎𝙩𝙪𝙙𝙞𝙤𝙨

@ReStudios

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

123subscribers

-1 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1001666185027
TypeChannel
Username@ReStudios
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live13 October 2026
Measurements held5
Confirmed unchanged1 time, most recently 13 October 2026
On Telegramt.me/ReStudios

Topic

Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 26 September 2026 and assigned it the closest of 31 fixed categories, at 87% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

12212412312 August 2026 — 124 subscribers12 August 2026 — 124 subscribers10 September 2026 — 123 subscribers19 September 2026 — 122 subscribers13 October 2026 — 123 subscribers12 August 202613 October 2026
5 measurements spanning 62 days, net -1. 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 122–124 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Oct 2026, 11:18123+1
19 Sept 2026, 08:38122-1
10 Sept 2026, 14:57123-1
12 Aug 2026, 06:45124no change
12 Aug 2026, 06:31124first reading

Engagement

17 posts held, back to 3 February 2024 — 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 17 posts for this entry, the most recent from 9 August 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

42 reactions across 7 posts, in 6 distinct kinds. The most used accounts for 40.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54156558140797238711740.5%
custom 51951006062508896091331.0%
💯716.7%
custom 533708005311933630937.14%
custom 620183482010488243512.38%
custom 621988269788443651412.38%

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

Measured over the 17 most recent posts we hold, published 3 February 2024 to 9 August 2025, 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 2025, 21:01 UTCviews —

𝙍𝙚𝙎𝙩𝙪𝙙𝙞𝙤𝙨 pinned «🪐 | ReStudios — [REDEFFE?] Buonasera a tutti! Come state belli? Tutto a posto? Dopo tanto tempo torno a scrivere su questo canale, che purtroppo avevo un po’ trascurato. In questo periodo sono cambiate molte cose: c’è chi mi conosce dai tempi di Minecraft…»

9 Aug 2025, 21:00 UTC119 views2 reactionsread 12 August 2026

🪐 | ReStudios — [REDEFFE?] Buonasera a tutti! Come state belli? Tutto a posto? Dopo tanto tempo torno a scrivere su questo canale, che purtroppo avevo un po’ trascurato. In questo periodo sono cambiate molte cose: c’è chi mi conosce dai tempi di Minecraft e chi mi ha conosciuto in altri contesti. Voglio dirvi che sono cresciuto e sono andato avanti. Parlando del settore grafico, che è sempre stato il cuore di quest…

custom 51951006062508896091custom 54156558140797238711

9 Aug 2025, 20:55 UTC88 viewsread 12 August 2026

⚙️| Stato Bot • ReStudios Il bot Restudios attualmente è in manutenzione, per ogni servizio > @StudiosHelp » @StudiosTalk » @ReStudios

30 Mar 2024, 10:19 UTC377 views11 reactionsread 12 August 2026
Photo

🐋 | ReStudios Tipo🔻Logo Server Minecraft + Copertina Da🔻 @ReStudios Per🔻 Anonimo Prezzo🔺 / / 🌚 » Vuoi richiedere un servizio? @ReStudiosBot

custom 51951006062508896094custom 54156558140797238714💯3

17 Mar 2024, 20:34 UTC385 views9 reactionsread 12 August 2026
Photo

🐋 | ReStudios Tipo🔻Logo 3D + Alternative Da🔻 @ReStudios Per🔻 @fratelliquintale Prezzo🔺 2.5€ 🌚 » Vuoi richiedere un servizio? @ReStudiosBot

custom 51951006062508896094💯3custom 54156558140797238712

10 Mar 2024, 21:10 UTC323 views4 reactionsread 12 August 2026
Photo

🐋 | ReStudios Tipo🔻Logo 3D Da🔻 @ReStudios Per🔻 @popolodellagaina Prezzo🔺 0.60€ 🌚 » Vuoi richiedere un servizio? @ReStudiosBot

custom 51951006062508896093custom 54156558140797238711

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

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

“𝙍𝙚𝙎𝙩𝙪𝙙𝙞𝙤𝙨” (@ReStudios), 123 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/ReStudios.

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.