Channel
@CratoxZSrc
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
26subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003610417303 |
|---|---|
| Type | Channel |
| Username | @CratoxZSrc |
| Created | 4 January 2026 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 1 September 2026 |
| On Telegram | t.me/CratoxZSrc |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 06:34 | 26 | -1 |
| 11 Aug 2026, 07:01 | 27 | no change |
| 7 Aug 2026, 18:11 | 27 | first reading |
10 posts held, back to 4 January 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 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 10 posts for this entry, the most recent from 21 April 2026. An engagement rate over an empty window would be a number about nothing.
Hello everyone, Our website is now live on the new domain: https://goofystresse.st Please make sure to update the API key in your funnel to reflect the new domain. As compensation for the downtime, all active plans have been extended by 1 day. Thank you for your understanding and support!
High-Performance IPHM-Enabled Infrastructure We deliver IPHM-enabled and Scan dedicated virtual servers engineered for performance, stability, and operational flexibility. Our systems are optimized to handle resource-intensive workloads with consistent throughput and low latency. --- Standard Compute Plans • 8GB DDR4 RAM | 4 vCPU — $35 / month • 16GB DDR4 RAM | 6 vCPU — $50 / month • 24GB DDR4 RAM | 8 vCPU — $…
BulletProof Servers on sell aswell!
🏆 CratoxZScripts – Costume Advanced L7 Bypass Script ✍️ Features: • Cloudflare Captcha , uam bypass • Free Lifetime Updates 💰 Price: $60 ✉️ Contact: @CratoXz
⚡️ | Goofystress.st - #1| ⚡️ ❓ | Why Is Goofystress the Preferred Choice for Customers? 🚀 Goofystress Delivers Unmatched Layer 4 / Layer 7. ➡️ Layer 7 : Goofystress offers bypasses for alot protections, we have the latest bypasses for CAPTCHA, CACHE, UAM, and many more. ➡️ Layer 4 : One of the best L4 on the market with the cheapest price per con, we offer 1.5 - 2 milion pps of TCP flood, and around 700 - 800k pp…
END 🔚
🚀 10% Off on both l4 & l7 Scripts 😴 Contact - @CratoXz
🏷 CratoxZScripts – Advanced L4 Script Available ✍️ Features: • UDP , TCP , ACK , SYN , STUN , GAMES , DNS , OVH • Free Lifetime Updates • More powerful methods available 🪙 Price: $35 [ package ] 💬 Contact: @CratoXz
🏆 CratoxZScripts – Costume Advanced L7 Bypass Script ✍️ Features: • Cloudflare Bypass , Captcha • Free Lifetime Updates • More powerful methods available 💰 Price: $45 ✉️ Contact: @CratoXz
Channel created
Showing the 10 most recent of 10 posts we hold for @CratoxZSrc. 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.
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.
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.
@CratoxZSrc named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“CratoxZ Scripts | Best Bypass Scripts & L4 Scripts Seller” (@CratoxZSrc), 26 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/CratoxZSrc.
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.