Telegram RegisterThe public register of Telegram
Telegram profile photo for Legend script

Channel

Legend script

@legendscriptrb

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

222,138subscribers

+4,315 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002233246797
TypeChannel
Username@legendscriptrb
DescriptionLegend script - сообщество где ты можешь найти скрипты без бана для - Roblox По рекламе : @lyaguhascripter Тех поддержка - @legendscript_bot Состою только в @legendscrips_robot - остальные - фейк Чат - @scriptlegendchat
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live4 September 2026
Measurements held26
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/legendscriptrb

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 8 August 2026 and assigned it the closest of 31 fixed categories, at 96% 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 1 other registered channel. 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
@legendscriptrb/3190 · this entry5 Aug 2026, 11:08 UTC@legendscriptrb2/46755 Aug 2026, 11:09 UTC1.00under a minute
@legendscriptrb/3191 · this entry5 Aug 2026, 14:00 UTC@legendscriptrb2/46785 Aug 2026, 15:08 UTC1.0068 minutes
@legendscriptrb/3196 · this entry6 Aug 2026, 12:57 UTC@legendscriptrb2/46836 Aug 2026, 12:58 UTC1.00under a minute
@legendscriptrb/3197 · this entry6 Aug 2026, 16:31 UTC@legendscriptrb2/46856 Aug 2026, 16:32 UTC1.00under a minute
@legendscriptrb/3198 · this entry6 Aug 2026, 20:13 UTC@legendscriptrb2/46876 Aug 2026, 20:13 UTC1.00under a minute
@legendscriptrb/3199 · this entry6 Aug 2026, 20:53 UTC@legendscriptrb2/46886 Aug 2026, 20:54 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@legendscriptrb210 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (100)

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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 21 comparable posts for this entry, running 3 August 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 key clone_source, last confirmed 8 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

217,823222,712220,267.57 August 2026 — 217,823 subscribers8 August 2026 — 217,886 subscribers9 August 2026 — 218,051 subscribers10 August 2026 — 218,343 subscribers11 August 2026 — 218,457 subscribers12 August 2026 — 218,509 subscribers14 August 2026 — 218,755 subscribers15 August 2026 — 218,780 subscribers16 August 2026 — 219,118 subscribers17 August 2026 — 219,449 subscribers18 August 2026 — 219,720 subscribers19 August 2026 — 220,097 subscribers20 August 2026 — 220,527 subscribers21 August 2026 — 220,574 subscribers23 August 2026 — 220,520 subscribers24 August 2026 — 220,436 subscribers25 August 2026 — 220,188 subscribers26 August 2026 — 220,532 subscribers27 August 2026 — 221,142 subscribers28 August 2026 — 221,380 subscribers29 August 2026 — 221,847 subscribers30 August 2026 — 222,360 subscribers31 August 2026 — 222,633 subscribers1 September 2026 — 222,712 subscribers3 September 2026 — 222,415 subscribers4 September 2026 — 222,138 subscribers222,1387 August 20264 September 2026
26 measurements spanning 28 days, net +4,315. 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 217,090–223,445 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)SubscribersChange
4 Sept 2026, 21:17222,138-277
3 Sept 2026, 05:58222,415-297
1 Sept 2026, 21:13222,712+79
31 Aug 2026, 20:53222,633+273
30 Aug 2026, 17:39222,360+513
29 Aug 2026, 14:17221,847+467
28 Aug 2026, 15:08221,380+238
27 Aug 2026, 14:04221,142+610
26 Aug 2026, 15:23220,532+344
25 Aug 2026, 16:42220,188-248
24 Aug 2026, 16:05220,436-84
23 Aug 2026, 02:13220,520-54
21 Aug 2026, 17:56220,574+47
20 Aug 2026, 17:52220,527+430
19 Aug 2026, 21:02220,097+377
18 Aug 2026, 17:44219,720+271
17 Aug 2026, 20:25219,449+331
16 Aug 2026, 18:28219,118+338
15 Aug 2026, 07:37218,780+25
14 Aug 2026, 01:47218,755first reading

Engagement

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

ERR · 30 days
2.41%
avg views ÷ 222,138 subscribers
Avg views / post
5,340
149 posts measured
Reaction rate
0.146%
reactions ÷ views · ER floor
Posts in window
149
of 171 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 147 of 149 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 6 September 2026
Posts held171 (3 August 20266 September 2026)
Views total796,279
Reactions total1,150
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Sept 2026, 19:03 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,220
Videos
369
Links
865

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. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
10m 36s
Average length
19s

Measured directly from 34 videos 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

1,323 reactions across 167 posts, in 28 distinct kinds. The most used accounts for 50.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
67350.9%
🔥18113.7%
👍1057.94%
❤‍🔥846.35%
🥴564.23%
👏382.87%
🍌241.81%
🤪231.74%
💘181.36%
😁181.36%
🐳141.06%
😱130.983%
🤔130.983%
🥰130.983%
🕊110.831%
90.68%
🍓60.454%
🌭40.302%
30.227%
💋30.227%
8 further kinds141.06%

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 169 of the 171 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 1,323 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 171 most recent posts we hold, published 3 August 2026 to 6 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.

Telegram Stars

Stars received
25
across the posts below
Posts paid on
17
of 171 we hold a reading for · 10%
Most on one post
5
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @legendscriptrb. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 171 most recent posts we hold for this entry, published 3 August 2026 to 6 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

6 Sept 2026, 17:30 UTC659 views2 reactionsread 6 September 2026
Photo

👀 Дюп вещей и бессмертие 99 nights in the forest script Авто фарм алмазов 💎, дюп и притягивание вещей , авто фарм дней, авто дети и god mod Обход всех ключей - тык Нейросеть по скриптам - тык

11

6 Sept 2026, 14:30 UTC≈1,610 views5 reactionsread 6 September 2026
Photo

🫥 авто фрукты и в4 🧑 блокс фрутс Авто в4 , фрукты , уровни , сундуки , ягоды , баунти , рыба, морские ивенты , кдк и многое другое Обход всех ключей - тык Нейросеть по скриптам - тык

4🍾1

6 Sept 2026, 11:00 UTC≈2,290 views5 reactionsread 6 September 2026

ПАК СКРИПТОВ 👀 99 nights in the forest script ПОЛУЧИТЬ СКРИПТ Blox fruits script ПОЛУЧИТЬ СКРИПТ Steal an egg script ПОЛУЧИТЬ СКРИПТ Clean the leaves script ПОЛУЧИТЬ СКРИПТ +1 speed keyboard escape script ПОЛУЧИТЬ СКРИПТ Lost front script ПОЛУЧИТЬ СКРИПТ Обход всех ключей - @Legendbypass_robot Нейросеть по скриптам - @LegendscripBot

🔥32

5 Sept 2026, 19:15 UTC≈4,150 views15 reactionsread 6 September 2026
Photo

👀 Универсальный скрипт на все режимы Скрипт просто включит другой скрипт который вам нужен на почти любой режим , полная имба, сможете не юзать куча разных скриптов Обход всех ключей - тык Нейросеть по скриптам - тык

👍75🤪3

5 Sept 2026, 17:40 UTC≈3,960 views8 reactionsread 6 September 2026
Photo

👀 Невидимость и бессмертие укради брэйнрот скрипт С помощью данного скрипта вы сможете становится полностью невидимым и с легкостью красит брэйнротов , помимо этого есть куча других функций для кражи и игры Обход всех ключей - тык Нейросеть по скриптам - так

🍓51👍1🔥1

5 Sept 2026, 14:30 UTC≈3,910 views0 reactionsread 6 September 2026
Photo

✨ Авто кража и авто фарм Steal an egg script авто кража яичек с выбором из какой зоны и какими мутациями, настройка приоритетов, сервер хоп, авто надевание лучших петов, авто фьюз петов, авто продажа петов, авто продажа яиц, авто покупка апгрейдов и тд Обход всех ключей - тык Нейросеть по скриптам - тык

5 Sept 2026, 11:30 UTC≈4,370 views8 reactionsread 6 September 2026

ПАК СКРИПТОВ 👀 Steal an egg script ПОЛУЧИТЬ СКРИПТ San Diego script ПОЛУЧИТЬ СКРИПТ Blade ball script ПОЛУЧИТЬ СКРИПТ Doors script ПОЛУЧИТЬ СКРИПТ +1 speed monkey escape script ПОЛУЧИТЬ СКРИПТ Grow a garden 2 script ПОЛУЧИТЬ СКРИПТ Обход всех ключей - @Legendbypass_robot Нейросеть по скриптам - @LegendscripBot

6❤‍🔥1🔥1

4 Sept 2026, 20:57 UTC≈5,220 views17 reactionsread 6 September 2026
Video

👀 Скам дуэли укради брэйнрот обнова С помощью этого скрипта вы без никакого труда получите чужого брэйнрота пока он этого даже не поймёт Обход всех ключей - тык Нейросеть по скриптам - тык

7❤‍🔥5🔥5

4 Sept 2026, 19:15 UTC≈4,630 views6 reactionsread 6 September 2026
Photo

👀 Випка на любой режим бесплатно Скрипт создаёт сервер куда не сможет попасть никто кроме вас и ваших друзей которым вы дадите адрес сервера Обход всех ключей - тык Нейросеть по скриптам - тык

4🎃1👏1

4 Sept 2026, 17:30 UTC≈4,470 views5 reactionsread 6 September 2026
Photo

👀 Кил аура и бессмертие Murder Mystery 2 script Спидхак, ноуклип, флай, иксрей, множество визуалов (ESP игроков, чамсы, трейсера), авто подбирание гана, аимлок, силент аим для ножа, авто фарм монет, настройки Обход всех ключей - тык Нейросеть по скриптам - тык

5

4 Sept 2026, 15:31 UTC≈4,530 views22 reactionsread 6 September 2026
File

File, posted without a caption

👏14👍4🔥3🌭1

4 Sept 2026, 14:30 UTC≈5,110 views7 reactionsread 6 September 2026
Photo

🫥 авто фрукты и в4 🧑 блокс фрутс Авто в4 , фрукты , уровни , сундуки , ягоды , баунти , рыба, морские ивенты , кдк и многое другое Обход всех ключей - тык Нейросеть по скриптам - тык

5👍1🔥1

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

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.

“Legend script” (@legendscriptrb), 222,138 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/legendscriptrb.

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.