Channel
@TheStuxy
On this record: Growth · Engagement · Posts · Citations · Cite this entry
411subscribers
-6 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003380078003 |
|---|---|
| Type | Channel |
| Username | @TheStuxy |
| Created | Between 1 November 2025 and 23 January 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 19 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 19 August 2026 |
| On Telegram | t.me/TheStuxy |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Aug 2026, 18:42 | 411 | -5 |
| 13 Aug 2026, 09:24 | 416 | -1 |
| 6 Aug 2026, 19:32 | 417 | no change |
| 6 Aug 2026, 09:40 | 417 | first reading |
18 posts held, back to 23 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 pageof 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 18 posts for this entry, the most recent from 10 June 2026. An engagement rate over an empty window would be a number about nothing.
Halo, gua naima. Disini gua mau minta maaf ke pihak" yang bersangkutan dan merasa dirugikan atas apa yang udah terjadi. Gua bakal jadiin kejadian ini sebagai pelajaran buat lebih hati" lagi dalam bermedia sosial kedepannya. Gua sadar ada hal" yang seharusnya bisa gua sikapi dengan lebih baik, dan gua berjanji nggak akan mengulangi kesalahan yang sama lagi. Sekali lagi gua minta maaf dan terima kasih buat semua yang u…
haloo, aku sahara. aku mau minta maaf atas kegaduhan yang sempat terjadi belakangan ini. maaf buat gege karena membangun stuxy yang berisi anak-anak dari ranah gege di kondisi saat itu, aku nggak membenarkan hal tersebut. dan untuk masalah internal antara admin yang td sempat dibahas, aku minta maaf yg sebesar besarnya untuk admin yang bersangkutan karena kurangnya komunikasi sama kalian dan terjadi secara tiba tiba.…
halo semua, aku hallie. aku mau menyampaikan permintaan maaf atas situasi yang telah terjadi. aku akuin bangun cc dengan tim dari ex ranah gege sebelumnya adalah keputusan yang salah. buat admin-admin yang pernah ngerasa dirugikan sama sikap aku, aku juga minta maaf. aku jadiin ini pelajaran supaya hal ini nggak keulang lagi ke depannya. buat gege, aku juga minta maaf karena udah ngambil jalan yang nggak seharusnya a…
haloo ini Laily disini aku mau minta maaf ke gege karena ikut serta dalam pembuatan cc ini yang isinya ex ranah dia. Dan gak lupa aku juga minta maaf ke semua orang yang merasa dirugikan aku janji habis ini gak bakal ngulangin hal yang sama, sekali lagi aku minta maaf buat semua yang ngerasa dirugiin 🤎🤎
halo ini bebev/kanuna disini gua minta maaf ke gege karena ikut adil dalam jalan pembuatan cc ini yng isinya pernah ada di ranah dia. gua minta maaf untuk siapapun itu diluaran sana yang merasa dirugikan atas tindakan gua, gua bener bener minta maaf tulus dari hati gua yang paling dalam dan gua bakalan belajar dari kesalahan yang gua buat dan berjanji ga akan mengulangi hal tersebut, sekali lagi gua minta maaf untuk …
halo, selamat malam semuanya. semoga kita semua selalu dalam keadaan sehat, ya. maaf menyita waktunya sebentar yaa. di sini gua, hagia, mau konfirmasi kalau problem internal dari admin stuxy sudah kami tuntaskan. mohon maaf untuk beberapa pihak yang merasa kurang nyaman atas problem ini, maaf buat gege juga, atas kurang tepatnya keputusan untuk mengambil team dari ranah gege. terima kasih atas pengertiannya, have a …
halo, gua jakav. gua minta maaf atas keputusan yang gua ambil sembarangan untuk ngeluarin beberapa admin stuxy dari gc team dan ch. gua sudah ngobrol dengan yang bersangkutan dan saat ini masalah sudah clear. gua juga minta maaf ke gege karena didalam team isinya dulu dari ranah gege. gua juga belajar atas semua kesalahan gua mau itu disengaja atau engga, gua minta maaf. terimakasih 🙏
Halo gw jaden, disini gw mau minta maaf atas semua yang terjadi malam ini khususnya ke semua orang yang merasa gw rugikan. Dan gw juga mau minta maaf sama gege karena terlibat di cc ini yang dimana isinya merupakan orang orang bagian yang pernah ada di ranah gege, gw akui itu salah. Dan gw minta maaf soal itu yaa. Untuk laily gw juga udah say sorry langsung ke orang nya. Dan untuk cc yang isinya gw, jakav, naima itu …
Posted without readable text
hi everyone, specially our beloved stuxy members. we just want to announce that stuxy is officially closing down starting from todaay. we truly enjoyed every bit of it, and we’re so glad we met all of you. maaf ya kalau ada salah-salah kata selama kita bareng. makasih banyak ya buat kalian yang udah nemenin stuxy dari awal. it’s been a pleasure knowing all of you and sharing so many good vibes here. thank you for th…
Sticker, posted without a caption
STÜXY DOORS: CLOSED (موصود) Major love for the contributions. If you missed out, stay tuned for the next rotation and keep your eyes on the next drop. Hit up @StuxyBot for any inquiries. See you on the streets.
Showing the 12 most recent of 18 posts we hold for @TheStuxy. 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.
Citation-graph rank — 217,909 of 1,563,849entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 5 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 19 August 2026 — this entry's latest reading, not the date you are reading this.
“STUXY: SIGNING OFF.” (@TheStuxy), 411 subscribers as measured 19 August 2026. Telegram Register, tgregister.com/channel/TheStuxy.
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.