Telegram RegisterThe public register of Telegram
Telegram profile photo for زاپاس تی اند رویال

Channel

زاپاس تی اند رویال

@Royal_Tuned

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

69,881subscribers

+28,482 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1002156108097
TypeChannel
Username@Royal_Tuned
Created5 June 2024 — measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live25 September 2026
Measurements held35
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/Royal_Tuned

Topic

Other / unclassifiable — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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

41,39969,88155,6407 August 2026 — 41,399 subscribers7 August 2026 — 41,399 subscribers8 August 2026 — 43,661 subscribers9 August 2026 — 44,719 subscribers10 August 2026 — 45,391 subscribers11 August 2026 — 47,644 subscribers12 August 2026 — 50,061 subscribers13 August 2026 — 51,282 subscribers14 August 2026 — 52,437 subscribers16 August 2026 — 53,655 subscribers17 August 2026 — 54,600 subscribers18 August 2026 — 55,161 subscribers19 August 2026 — 55,392 subscribers20 August 2026 — 55,677 subscribers21 August 2026 — 56,070 subscribers23 August 2026 — 57,446 subscribers24 August 2026 — 58,834 subscribers25 August 2026 — 59,810 subscribers26 August 2026 — 61,847 subscribers27 August 2026 — 62,713 subscribers28 August 2026 — 63,461 subscribers29 August 2026 — 63,751 subscribers30 August 2026 — 64,014 subscribers31 August 2026 — 64,267 subscribers1 September 2026 — 64,586 subscribers2 September 2026 — 64,701 subscribers3 September 2026 — 64,956 subscribers5 September 2026 — 64,838 subscribers9 September 2026 — 64,793 subscribers11 September 2026 — 65,210 subscribers13 September 2026 — 65,532 subscribers15 September 2026 — 65,874 subscribers16 September 2026 — 66,451 subscribers19 September 2026 — 66,985 subscribers25 September 2026 — 69,881 subscribers7 August 202625 September 2026
35 measurements spanning 49 days, net +28,482. 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 37,127–74,153 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)SubscribersChange
25 Sept 2026, 17:5669,881+2,896
19 Sept 2026, 03:3666,985+534
16 Sept 2026, 20:5966,451+577
15 Sept 2026, 02:2065,874+342
13 Sept 2026, 10:3765,532+322
11 Sept 2026, 14:5765,210+417
9 Sept 2026, 01:2164,793-45
5 Sept 2026, 16:1864,838-118
3 Sept 2026, 17:0164,956+255
2 Sept 2026, 12:2464,701+115
1 Sept 2026, 15:0564,586+319
31 Aug 2026, 13:0264,267+253
30 Aug 2026, 14:1664,014+263
29 Aug 2026, 14:3463,751+290
28 Aug 2026, 12:5263,461+748
27 Aug 2026, 15:1762,713+866
26 Aug 2026, 16:4261,847+2,037
25 Aug 2026, 17:3959,810+976
24 Aug 2026, 19:4458,834+1,388
23 Aug 2026, 07:5457,446first reading

Engagement

36 posts held, back to 5 June 2024 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 107 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.41%
avg views ÷ 69,881 subscribers
Avg views / post
986
13 posts measured
Reaction rate
0.412%
reactions ÷ views · ER floor
Posts in window
13
of 36 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. It is computed over the 8 of 13 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 23 September 2026
Posts held36 (5 June 2024 – 23 September 2026)
Views total12,819
Reactions total34
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Sept 2026, 14:39 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

Photos
1
Links
2

Lifetime counters from Telegram’s own channel header, read 27 September 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.

Reaction mix

8,564 reactions across 23 posts, in 25 distinct kinds. The most used accounts for 38.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤3,26238.1%
❤‍🔥1,38816.2%
🔥94411.0%
😁5696.64%
👍4365.09%
🤔3103.62%
🥰2583.01%
🖕2562.99%
🕊1191.39%
😎1191.39%
🍾1181.38%
👎1181.38%
😍1171.37%
💋810.946%
☃730.852%
👾670.782%
💯620.724%
🤯600.701%
😱590.689%
⚡520.607%
5 further kinds961.12%

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 23 of the 36 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 8,564 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 36 most recent posts we hold, published 5 June 2024 to 23 September 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

4 Sept 2026, 20:12 UTC863 views2 reactionsread 5 September 2026

یکی بیاد رل بزنیم❤️‍🔥

💔2

3 Sept 2026, 20:01 UTC790 viewsread 4 September 2026

آخر شبا آنلاینی بیا ربات زیر ناشناس چت کن😍👇

2 Sept 2026, 20:44 UTC739 views8 reactionsread 3 September 2026

یکی بیاد رل بزنیم❤️‍🔥

❤8

1 Sept 2026, 20:45 UTC797 views3 reactionsread 2 September 2026

یکی بیاد رل بزنیم❤️‍🔥

❤3

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

Posts edited after publishing

@Royal_Tuned edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
22 August 2026
Most recent edit
22 August 2026

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 2 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.

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

“زاپاس تی اند رویال” (@Royal_Tuned), 69,881 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/Royal_Tuned.

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.