Sticker, posted without a caption
Channel
BUKTI PROBLEM
@BUKTI3
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
4subscribers
+1 since we began measuring on 28 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1004458177730 |
|---|---|
| Type | Channel |
| Username | @BUKTI3 |
| Created | Between 1 June 2026 and 28 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 6 times, most recently 11 November 2026 |
| On Telegram | t.me/BUKTI3 |
Topic
Other / unclassifiable — 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 7 October 2026 and assigned it the closest of 31 fixed categories, at 65% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Oct 2026, 05:38 | 4 | +1 |
| 29 Aug 2026, 03:53 | 3 | no change |
| 28 Aug 2026, 18:00 | 3 | first reading |
Engagement
12 posts held, back to 28 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 12 posts for this entry, the most recent from 28 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Saat sidang, Arthur sudah diberikan waktu untuk memberikan sanggahan ataupun pembelaan diri terkait masalah ini. Namun, Arthur tidak menunjukkan tanda" keaktifan nya selama sidang, yang membuat terpaksa untuk di lanjutkan ke tahap selanjutnya. Dan untuk Eloise, Ia tidak aktif selama 1 Jam sebelum sidang dan tidak merespon surat yang diberikan kami untuk masuk ke Ruang Sidang. Serta acc nya tidak bisa di invite langs…
Penjelasan secara ringkasnya, inti dari permasalahan.
Sticker, posted without a caption
1. kecurigaan awal dirasakan cfo cvh karna eloise tiba² komen eval arthur, dia begitu katanya panik karna ada masalah diinstansi lain. apa hubungannya? 2. dia joinin akun lain yang awal dia bilang akun clone terus karna ketauan dia ngelak kalo itu temannya
Sticker, posted without a caption
dia reply bbc teguran jam 14.22 wib lalu klasifikasi ke rc arthur jam 15.42 sedangkan menurut perhitungan. 🕑 WIB: 14.22 🕒 WITA: 15.22 (tambah 1 jam) 🕓 WIT: 16.22 (tambah 2 jam) keliatan dibuat² biar punya bukti saja dan jika memang kejadian jam 14.22 WIB, kenapa klasifikasinya delay dan arthur juga read?
Sticker, posted without a caption
Dari bukti ini terlihat, bahwa memang Eloise mengaku bahwa acc tersebut milik temannya, yang di join kan pada Room untuk mengetes ke aktifan dari bot
╭─〔 PIHAK YANG BERSANGKUTAN 〕─╮ 01. Arthur Jadewolf «Username Telegram : @arttchrs « ID Telegram : 6350580028 02. Eloise Franc'esca «Username Telegram : @iffarygirl «ID Telegram : 5535887321 03. Pearly «Username Telegram : @ilywie «ID Telegram : 7251585569
Sticker, posted without a caption
Sticker, posted without a caption
Showing the 12 most recent of 12 posts we hold for @BUKTI3. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 7 October 2026 — this entry's latest reading, not the date you are reading this.
“BUKTI PROBLEM” (@BUKTI3), 4 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/BUKTI3.
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.