Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝗥𝗔𝗜𝗡𝗕𝗢𝗪 𝗦𝗖𝗥𝗜𝗣𝗧

Channel

𝗥𝗔𝗜𝗡𝗕𝗢𝗪 𝗦𝗖𝗥𝗜𝗣𝗧

@RainScripts

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

37,572subscribers

-2,549 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-1002663565217
TypeChannel
Username@RainScripts
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live4 September 2026
Measurements held27
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/RainScripts

Topic

Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 92% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 6 other registered channels. They sit inside a group of 14 channels that share the same post bodies with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@ponScriptRoblox/724022 Jul 2026, 12:49 UTC@RainScripts/2478 · this entry29 Jul 2026, 13:20 UTC1.007 days
@ponScriptRoblox/724223 Jul 2026, 14:44 UTC@RainScripts/2480 · this entry30 Jul 2026, 14:06 UTC1.007 days
@ponScriptRoblox/724725 Jul 2026, 13:46 UTC@RainScripts/2484 · this entry31 Jul 2026, 13:28 UTC1.006 days
@RainScripts/2488 · this entry1 Aug 2026, 14:16 UTC@ponScriptRoblox/72541 Aug 2026, 14:18 UTC1.002 minutes
@RainScripts/2490 · this entry2 Aug 2026, 14:00 UTC@ponScriptRoblox/72552 Aug 2026, 14:05 UTC1.005 minutes
@ponScriptRoblox/72585 Aug 2026, 13:21 UTC@RainScripts/2500 · this entry5 Aug 2026, 13:21 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@ponScriptRoblox7 (7/7 hand-verifiable sample passed)1.003 days@ponScriptRoblox (52)
@AlyaScript6 (6/6 hand-verifiable sample passed)1.0072 secondsthis entry (42)
@Wezscript6 (6/6 hand-verifiable sample passed)1.002 minutesthis entry (42)
@DeltaXRobloxScripts5 (5/5 hand-verifiable sample passed)1.002 minutesthis entry (32)
@KolerotScripts5 (5/5 hand-verifiable sample passed)1.003 minutesthis entry (41)
@JordonScript8 (8/8 hand-verifiable sample passed)1.00under a minute@JordonScript (53)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 1 of the 13 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 19 comparable posts for this entry, running 29 July 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 14, the earliest publisher we hold is @ponScriptRoblox. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 13 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

37,57240,29438,9337 August 2026 — 40,121 subscribers7 August 2026 — 40,121 subscribers8 August 2026 — 40,106 subscribers9 August 2026 — 40,173 subscribers10 August 2026 — 40,268 subscribers11 August 2026 — 40,293 subscribers12 August 2026 — 40,294 subscribers13 August 2026 — 40,189 subscribers15 August 2026 — 39,945 subscribers16 August 2026 — 39,723 subscribers17 August 2026 — 39,620 subscribers18 August 2026 — 39,524 subscribers19 August 2026 — 39,431 subscribers20 August 2026 — 39,301 subscribers21 August 2026 — 39,037 subscribers23 August 2026 — 38,889 subscribers24 August 2026 — 38,629 subscribers25 August 2026 — 38,502 subscribers26 August 2026 — 38,416 subscribers27 August 2026 — 38,253 subscribers28 August 2026 — 38,200 subscribers29 August 2026 — 38,054 subscribers30 August 2026 — 38,004 subscribers1 September 2026 — 37,861 subscribers2 September 2026 — 37,763 subscribers3 September 2026 — 37,669 subscribers4 September 2026 — 37,572 subscribers7 August 20264 September 2026
27 measurements spanning 28 days, net -2,549. 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,164–40,702 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
4 Sept 2026, 15:2037,572-97
3 Sept 2026, 01:4737,669-94
2 Sept 2026, 00:5537,763-98
1 Sept 2026, 01:0437,861-143
30 Aug 2026, 22:5338,004-50
29 Aug 2026, 20:2638,054-146
28 Aug 2026, 18:3838,200-53
27 Aug 2026, 19:5738,253-163
26 Aug 2026, 19:1738,416-86
25 Aug 2026, 18:3838,502-127
24 Aug 2026, 19:0538,629-260
23 Aug 2026, 05:4938,889-148
21 Aug 2026, 20:4939,037-264
20 Aug 2026, 15:2239,301-130
19 Aug 2026, 15:3239,431-93
18 Aug 2026, 17:4339,524-96
17 Aug 2026, 20:3339,620-103
16 Aug 2026, 16:5539,723-222
15 Aug 2026, 01:1739,945-244
13 Aug 2026, 18:2740,189first reading

Engagement

50 posts held, back to 23 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 62 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.13%
avg views ÷ 37,572 subscribers
Avg views / post
800
22 posts measured
Reaction rate
0.101%
reactions ÷ views · ER floor
Posts in window
22
of 50 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 22 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 24 August 2026
Posts held50 (23 July 202624 August 2026)
Views total17,599
Reactions total6
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Sept 2026, 12: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
118
Videos
5
Links
27

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

Video runtime
30s
Average length
30s

Measured directly from 1 video 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

24 reactions across 14 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1250.0%
1041.7%
🔥28.33%

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

Measured over the 50 most recent posts we hold, published 23 July 2026 to 24 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

24 Aug 2026, 11:54 UTC512 views1 reactionsread 6 September 2026
Forwarded from @RoqsScriptPhoto

Скрипт на Blox Fruts ❌Без ключа ⚙️ФУНКЦИИ 🔘Много авто функциий 🔘ESP на мобов/игроков 🔘Фарм для фрукта 🔘И тд ❓Туториал как получить скрипт(https://t.me/tut0r10ls) ⬇️Получи скрипт по кнопке ниже

🔥1

24 Aug 2026, 07:16 UTC507 views1 reactionsread 6 September 2026
Forwarded from @NextScriptRbPhoto

👀 Animal Hospital script ❌Без ключа ⚙️ФУНКЦИИ 🔘Все на скрине ❓Туториал как получить скрипт(https://t.me/tut0r10ls) ⬇️Получи скрипт по кнопке ниже

1

23 Aug 2026, 11:03 UTC526 views0 reactionsread 6 September 2026
Forwarded from @NextScriptRbPhoto

Скрипт на steal an egg ❌Без ключа ⚙️ФУНКЦИИ Все самые нужные ❓Туториал как получить скрипт(https://t.me/tut0r10ls) ⬇️Получи скрипт по кнопке ниже

22 Aug 2026, 10:14 UTC624 viewsread 6 September 2026
Forwarded from @NextScriptRbPhoto

❤️ Отличный скрипт на Murder Mystery 2 ❌Без ключа ⚙️ФУНКЦИИ AutoLoot Gun, TriggerBot, Auto Shot Murder, WallShot Murder, Kill All, Kill Sheriff Only, Auto Farm Coins, AutoFlin Murder, Auto Reset, ESP, Inf Jump, Fly, Fly Aura, Noclip, SpinBot, BunnyHop, Jerk Off Tool, Anti-Fling, Touch Fling, Fling ❓Туториал как получить скрипт(https://t.me/tut0r10ls) ⬇️Получи скрипт по кнопке ниже

22 Aug 2026, 10:14 UTC541 viewsread 6 September 2026
Forwarded from @AbsolutXScriptPhoto

Скрипт на 99 Night in The Forest ❌Без ключа ⚙️ФУНКЦИИ 🔘килл аура 🔘есп 🔘притянуть предметы 🔘все нужные функции ❓Туториал как получить скрипт(https://t.me/tut0r10ls) ⬇️Получи скрипт по кнопке ниже

15 Aug 2026, 13:08 UTC870 viewsread 6 September 2026
Forwarded from @NextScriptRbPhoto

Скрипт на the strongest battlegrounds ❌Без ключа ⚙️ФУНКЦИИ 🔘Авто килл 🔘анти воид 🔘тп 🔘аим 🔘т.д ❓Туториал как получить скрипт(https://t.me/tut0r10ls) ⬇️Получи скрипт по кнопке ниже

15 Aug 2026, 13:07 UTC732 views0 reactionsread 6 September 2026
Forwarded from @RoqsScriptPhoto

СКРИПТ на Muscle Legends ❌Без ключа ⚙️ФУНКЦИИ: 🔘Все для фарм 🔘авто перерождение 🔘авто убийство ❓Туториал как получить скрипт(НАЖМИ) ⬇️Получи скрипт по кнопке ниже

15 Aug 2026, 08:04 UTC737 viewsread 6 September 2026
Forwarded from @NextScriptRbPhoto

Скрипт на Fisch ❌Без ключа ⚙️ФУНКЦИИ 🔘Teleport 🔘Авто ловля рыбы 🔘Авто фарм 🔘Авто апгрейд 🔘есп ❓Туториал как получить скрипт(https://t.me/tut0r10ls) ⬇️Получи скрипт по кнопке ниже

15 Aug 2026, 08:04 UTC661 views1 reactionsread 6 September 2026
Forwarded from @RoqsScriptPhoto

👹 СКРИПТ НА MM2 ❌Без ключа ⚙️ФУНКЦИИ 🔘авто шот мардер 🔘рол есп 🔘пик ап ган 🔘кил всех и тому подобное ❓Туториал как получить скрипт(https://t.me/tut0r10ls) ⬇️Получи скрипт по кнопке ниже

1

13 Aug 2026, 12:50 UTC732 viewsread 6 September 2026
Forwarded from @NextScriptRbPhoto

Скрипт на Grow A Garden 2 ❌Без ключа ✅Проверенно ⚙️ФУНКЦИИ -Auto Plant (авто-посадка семян с настройкой позиции), Auto Harvest (авто-сбор урожая), создание правил сбора по фильтрам, Shovel & ирен Gear (удаление и перемещение растений), Auto Water (авто-полив лейками). ❓Туториал как получить скрипт(https://t.me/tut0r10ls) ⬇️Получи скрипт по кнопке ниже

13 Aug 2026, 10:21 UTC720 viewsread 6 September 2026
Forwarded from @RoqsScriptPhoto

Скрипт на Forsaken ❌Без ключа ✅Проверенно ⚙️ФУНКЦИИ 🔘Esp 🔘InfinityStamina 🔘Antifling 🔘Speedhack 🔘jumphack ❓Туториал как получить скрипт(https://t.me/tut0r10ls) ⬇️Получи скрипт по кнопке ниже

12 Aug 2026, 15:21 UTC869 viewsread 6 September 2026
Forwarded from @RoqsScriptPhoto

📌Скрипт на +1 SPEED KEYBOARD ESCAPE | CANDY & CHOCOLATE ❌Без ключа ✅Проверенно ⚙️ФУНКЦИИ 💖 Любой геймпасс в игре бесплатно! 💖 Лучший Авто-Фарм побед! 💖 Рабочий Анти-Хит для 2-го мира! 💖 Поставить себе любую скорость 💖 Авто-Скуп для магазина предметов ❓Туториал как получить скрипт(https://t.me/tut0r10ls) ⬇️Получи скрипт по кнопке ниже

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

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

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

“𝗥𝗔𝗜𝗡𝗕𝗢𝗪 𝗦𝗖𝗥𝗜𝗣𝗧” (@RainScripts), 37,572 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/RainScripts.

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.