Supplier bukan cuma visend awr tapi ada gp gig dll, ya pokonya roblox needs.
Signed Jae close order, cuma open tutor.

Channel
@neixus
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
1,084subscribers
-84 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002300774317 |
|---|---|
| Type | Channel |
| Username | @neixus |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 27 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 27 September 2026 |
| On Telegram | t.me/neixus |
Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 18 September 2026 and assigned it the closest of 31 fixed categories, at 39% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Sept 2026, 06:37 | 1,084 | -13 |
| 15 Sept 2026, 12:59 | 1,097 | -6 |
| 12 Sept 2026, 00:57 | 1,103 | -7 |
| 7 Sept 2026, 15:55 | 1,110 | -8 |
| 2 Sept 2026, 23:14 | 1,118 | -6 |
| 27 Aug 2026, 14:25 | 1,124 | -3 |
| 24 Aug 2026, 05:16 | 1,127 | -5 |
| 20 Aug 2026, 15:22 | 1,132 | -3 |
| 17 Aug 2026, 11:54 | 1,135 | -2 |
| 13 Aug 2026, 16:05 | 1,137 | -7 |
| 10 Aug 2026, 07:45 | 1,144 | -23 |
| 7 Aug 2026, 12:46 | 1,167 | -1 |
| 6 Aug 2026, 20:05 | 1,168 | first reading |
20 posts held, back to 5 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 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 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Supplier bukan cuma visend awr tapi ada gp gig dll, ya pokonya roblox needs.
Signed Jae close order, cuma open tutor.
Open pt pt all package lagi
Signed Jae close order, cuma open tutor.
All mem dapet 10 supplier+tutor, supplier bukan cuma kontak tapi juga website yg murah.
Signed Jae close order, cuma open tutor.
Close udh pay dan udh dikasih semua
Signed Jae close order, cuma open tutor.
-1
Signed Jae close order, cuma open tutor.
Dapet 10 kontak + tutor
Signed Jae close order, cuma open tutor.
All package bisa pt pt max 4 org
Signed Jae close order, cuma open tutor.
Kontak supp visend sold.
Signed Jae close order, cuma open tutor.
Gua rec dari awal login sampe terkirim, proof limit cuma 500r juga ada disana, semua terekam jelas. Jd buat yg di doktrin method ke fix all itu coba lu liat aja sendiri, yg ke fix pack gede doang.
Signed Jae close order, cuma open tutor.
Udh gua coba dan method masih work buat maximal 5000 robux seperti yg gua bilang diatas, ini gua send 2000 robux dari akun limit 500r berhasil dan masuk semua. Member tutor buru cek ya info baru di ch
Signed Jae close order, cuma open tutor.
Tar gua infoin lagi kalo ada yg baru, mau coba kirim 2000r dulu
Signed Jae close order, cuma open tutor.
Info method ke fix tapi untuk yg main dibawah 5k masih aman, maximal kirim visend/viplus 5000 robux di akun yg limitnya 500r. Bedanya apan bang? Bedanya kalo kmren akun limit 500r bisa kirim viplus unlimited, skrg batas max 5000 robux.
Signed Jae close order, cuma open tutor.
Showing the 12 most recent of 20 posts we hold for @neixus. 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.
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.
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.
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 27 September 2026 — this entry's latest reading, not the date you are reading this.
“💭 ׅ Nexus ׄopen tutor robux & sell contact supplier ֵׅ ֵׅ ֵׅ” (@neixus), 1,084 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/neixus.
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.