Telegram RegisterThe public register of Telegram
Telegram profile photo for /

Channel

/

@KolerotScripts

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry

38subscribers

-15,429 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-1002375945470
TypeChannel
Username@KolerotScripts
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 November 2026
Measurements held38
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/KolerotScripts

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 100% 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 the other topics.

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 in near-verbatim form on 4 other registered channels. This entry also sits inside a group of 32 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts 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
@script_r/17782 Aug 2026, 10:49 UTC@KolerotScripts/8436 · this entry2 Aug 2026, 10:50 UTC1.00under a minute
@script_r/17958 Aug 2026, 11:06 UTC@KolerotScripts/8471 · this entry8 Aug 2026, 11:06 UTC1.00under a minute
@script_r/180511 Aug 2026, 15:49 UTC@KolerotScripts/8490 · this entry11 Aug 2026, 15:50 UTC1.00under a minute
@script_r/180812 Aug 2026, 07:58 UTC@KolerotScripts/8496 · this entry12 Aug 2026, 07:59 UTC1.0072 seconds
@script_r/184623 Aug 2026, 12:54 UTC@KolerotScripts/8557 · this entry23 Aug 2026, 12:54 UTC1.00under a minute
@script_r/185225 Aug 2026, 10:55 UTC@KolerotScripts/8567 · this entry25 Aug 2026, 10:56 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@script_r16 (8/8 hand-verifiable sample passed)1.00under a minute@script_r (9–7)
@DeltaXRobloxScripts12 (8/8 hand-verifiable sample passed)1.002 minutesthis entry (9–3)
@emenstu12 (8/8 hand-verifiable sample passed)1.00under a minute@emenstu (7–5)
@GojoScriptsRBX10 (8/8 hand-verifiable sample passed)1.002 minutesthis entry (9–1)

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. 23 of the 25 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 85 comparable posts for this entry, running 1 August 2026 to 2 September 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).

Of the group of 32 channels, the one whose matching posts we hold earliest is @ponScriptRoblox. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_mutual · clone_source, last confirmed 11 November 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.

Channels linked by matching posts

This channel is in a group of 32 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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.

Legend script
@legendscriptrb · Channel
215,733 subscribers
Four Script | Роблокс Скрипты | Roblox Script
@FourScript_Roblox · Channel
47,818 subscribers
𝗠𝗮𝘅𝗶𝗺𝗸𝗮 | 𝗥𝗼𝗯𝗹𝗼𝘅 | 𝗦𝗰𝗿𝗶𝗽𝘁𝘀
@R0blox_scr1pts · Channel
45,418 subscribers
Dahakka Script
@dahakka_script · Channel
42,668 subscribers
Delta-X Script Roblox
@DeltaXRobloxScripts · Channel
40,436 subscribers
ᴅᴇʟᴛᴀ x ᴀᴢᴜʀᴇ
@deltascriptt · Channel
40,164 subscribers
𝘿𝙧𝙖𝙜𝙤𝙣 𝙎𝙘𝙧𝙞𝙥𝙩
@dragonscriptt · Channel
37,438 subscribers
KREVETKASCRIPTS
@KREVETKASCRIPTS · Channel
36,928 subscribers
pon.СКРИПТЫ ММ2
@ponScriptRoblox · Channel
36,747 subscribers
wezscript | Roblox Scripts
@Wezscript · Channel
36,347 subscribers
Delta x script
@deltaxxscript · Channel
30,591 subscribers
SCRIPTS Х Roblox | СКРИПТЫ на роблокс
@ScriptsDeltaX · Channel
25,999 subscribers
Scripts roblox | Delta
@seizyscript · Channel
25,870 subscribers
⚜️ HUNTER SCRIPT ⚜️
@HunterScriptsX · Channel
23,559 subscribers
𝗚𝗢𝗝𝗢𝗦𝗖𝗥𝗜𝗣𝗧𝗦𝗥𝗕𝗫
@GojoScriptsRBX · Channel
22,853 subscribers
🏝️ 𝐂𝐚𝐩𝐲𝐛𝐚𝐫𝐚 𝐒𝐜𝐫𝐢𝐩𝐭𝐬 | 𝐑𝐨𝐛𝐥𝐨𝐱 𝐒𝐜𝐫𝐢𝐩𝐭𝐬
@Capybara_Scripts · Channel
21,543 subscribers
Fire Script | Roblox скрипты
@script_r · Channel
19,727 subscribers
Твинк (Scriptov rb Xirrora)
@TwinkXirrorScript · Channel
18,998 subscribers
𝗔𝗹𝘆𝗮 𝗦𝗰𝗿𝗶𝗽𝘁
@AlyaScript · Channel
18,428 subscribers
Xeorx Script | DeltaX Роблокс Скрипты
@Xeorxscript · Channel
16,739 subscribers
ᴘɪᴠᴏᴋ sᴄʀɪᴘᴛs
@pivok_script · Channel
15,389 subscribers
🏖 Kombo Scripts 🏖
@komboscript · Channel
14,677 subscribers
Script Musor
@scriptmusor · Channel
13,520 subscribers
Project Script | Roblox Скрипты🎩
@Project_Script · Channel
12,028 subscribers
BARS | SCRIPTS
@bpscripts · Channel
11,658 subscribers
BYAKUYASCRIPTS
@BYAKUYASCRIPTS · Channel
11,491 subscribers
🦾 Kenny scripts
@kenny_scripts · Channel
10,902 subscribers
‼️ Фемчики ‼️
@emenstu · Channel
201 subscribers
Переходник
@sbabbahvd · Channel
131 subscribers

2 more channels are in this same group but not listed individually here.

Growth

515,4677,7367 August 2026 — 15,467 subscribers7 August 2026 — 15,467 subscribers8 August 2026 — 15,456 subscribers9 August 2026 — 15,420 subscribers10 August 2026 — 15,391 subscribers11 August 2026 — 15,346 subscribers12 August 2026 — 15,318 subscribers13 August 2026 — 15,296 subscribers14 August 2026 — 15,234 subscribers16 August 2026 — 15,182 subscribers17 August 2026 — 15,135 subscribers18 August 2026 — 15,107 subscribers19 August 2026 — 15,058 subscribers20 August 2026 — 14,980 subscribers22 August 2026 — 14,942 subscribers23 August 2026 — 14,857 subscribers25 August 2026 — 14,835 subscribers26 August 2026 — 14,786 subscribers27 August 2026 — 14,744 subscribers28 August 2026 — 14,712 subscribers29 August 2026 — 14,683 subscribers30 August 2026 — 14,659 subscribers31 August 2026 — 14,611 subscribers1 September 2026 — 14,592 subscribers2 September 2026 — 14,564 subscribers3 September 2026 — 14,506 subscribers5 September 2026 — 14,468 subscribers8 September 2026 — 14,376 subscribers11 September 2026 — 14,324 subscribers13 September 2026 — 14,274 subscribers15 September 2026 — 14,217 subscribers18 September 2026 — 5 subscribers3 October 2026 — 25 subscribers13 October 2026 — 27 subscribers21 October 2026 — 32 subscribers29 October 2026 — 38 subscribers4 November 2026 — 37 subscribers11 November 2026 — 38 subscribers387 August 202611 November 2026
38 measurements spanning 96 days, net -15,429. 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”.
Measurement log — every subscribers count we have recorded, most recent 20 of 38
Measured (UTC)SubscribersChange
11 Nov 2026, 08:5838+1
4 Nov 2026, 06:2537-1
29 Oct 2026, 05:5038+6
21 Oct 2026, 07:5032+5
13 Oct 2026, 11:1927+2
3 Oct 2026, 06:1925+20
18 Sept 2026, 06:175-14,212
15 Sept 2026, 00:5814,217-57
13 Sept 2026, 09:5714,274-50
11 Sept 2026, 10:0114,324-52
8 Sept 2026, 19:1914,376-92
5 Sept 2026, 08:5714,468-38
3 Sept 2026, 13:3714,506-58
2 Sept 2026, 04:2814,564-28
1 Sept 2026, 05:3514,592-19
31 Aug 2026, 08:0314,611-48
30 Aug 2026, 05:1314,659-24
29 Aug 2026, 07:0614,683-29
28 Aug 2026, 07:2714,712-32
27 Aug 2026, 10:1514,744first reading

Engagement

161 posts held, back to 1 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 53 pages 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 161 posts for this entry, the most recent from 2 September 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

10 reactions across 10 posts, in 6 distinct kinds. The most used accounts for 30.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤330.0%
👍220.0%
🗿220.0%
💊110.0%
🙉110.0%
🤨110.0%

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

Measured over the 161 most recent posts we hold, published 1 August 2026 to 2 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

2 Sept 2026, 17:15 UTC16 viewsread 2 September 2026
Photo

👀 Авто дуэли и невидимость Steal a brainrot script ⚙️ Функции: Лучший скрипт для дуэлей , авто кража , аим , авто покупка брэйнротов , высокие прыжки и скорость , невидимость , авто медуза и многое другое Без бана ✔️ и без ключа 🔑

Signed ℳ𝒶𝓉𝓋ℯ𝓎 ℳℯ𝓁ℯ𝓈𝒽𝓀ℴ

2 Sept 2026, 16:00 UTC28 viewsread 2 September 2026
Photo

💨 Отличный скрипт на Blox Fruits ⚙️ Функции: Auto Farm Level, Auto Travel Dressrosa, Auto Zou Quest, Auto Farm Nearest, Auto Factory Raid, Auto Pirate Raid, Auto Materials, Auto Farm Ectoplasm, Auto Done Bartilo Quest, Auto Done Citizen Quest, Auto Training Dummy, Auto Collect Berry, Auto Collect Chest, Auto Fishing, NPC Aimbot, Double Attack, Auto Mastery Fruit, Auto Mastery Gun, Auto Mastery All Sword и многое дру…

Signed ︎ ︎samu

1 Sept 2026, 20:10 UTC69 viewsread 2 September 2026
Photo

👀 Кил аура и бессмертие Murder Mystery 2 script ⚙️ Функции: Спидхак, ноуклип, флай, иксрей, множество визуалов (ESP игроков, чамсы, трейсера), авто подбирание гана, аимлок, силент аим для ножа, авто фарм монет, настройки Без бана ✔️ и без ключа 🔑

Signed ℳ𝒶𝓉𝓋ℯ𝓎 ℳℯ𝓁ℯ𝓈𝒽𝓀ℴ

1 Sept 2026, 17:32 UTC75 viewsread 2 September 2026
Photo

👀 Aim и skin Channger скрипт на Rivals ⚙️ Функции: С помощью этого скрипта вы сможете использовать любые скины , видеть соперников через стены , авто стрелять в голову и многое другое Без бана ✔️ и без ключа 🔑

Signed ℳ𝒶𝓉𝓋ℯ𝓎 ℳℯ𝓁ℯ𝓈𝒽𝓀ℴ

31 Aug 2026, 21:14 UTC98 viewsread 2 September 2026
Photo

👀 Лучший скрипт 99 nights in the forest ⚙️ Функции: Авто фарм алмазов, авто фарм дней, авто-дети, авто эвенты и многое другое Без бана ✔️ и без ключа 🔑

Signed ℳ𝒶𝓉𝓋ℯ𝓎 ℳℯ𝓁ℯ𝓈𝒽𝓀ℴ

31 Aug 2026, 16:13 UTC123 viewsread 2 September 2026
Photo

🤩 Имбовый Blox fruits SCRIPT ⚙️ Функции: Авто фарм в4 , фрукты , уровни , сундуки , ягоды , баунти , рыба, морские ивенты , кдк и многое другое Без бана ✔️ и без ключа 🔑

Signed ℳ𝒶𝓉𝓋ℯ𝓎 ℳℯ𝓁ℯ𝓈𝒽𝓀ℴ

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

@KolerotScripts edited 2 posts 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
13 August 2026
Most recent edit
17 August 2026

Posts recorded as deleted after publishing

We recorded 3 posts on @KolerotScripts as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
7 August 2026
Most recent seen missing
8 August 2026
Median time before seen missing
25 hours
Seen missing in the last 30 days
0

Mentions

Named by 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“/” (@KolerotScripts), 38 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/KolerotScripts.

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.