Channel
@JASEBERA
On this record: Growth · Engagement · Posts · Citations · Cite this entry
2,548subscribers
+293 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003524466849 |
|---|---|
| Type | Channel |
| Username | @JASEBERA |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 11 September 2026 |
| On Telegram | t.me/JASEBERA |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 03:21 | 2,548 | -17 |
| 5 Sept 2026, 18:39 | 2,565 | +173 |
| 1 Sept 2026, 14:47 | 2,392 | +186 |
| 29 Aug 2026, 11:08 | 2,206 | -2 |
| 26 Aug 2026, 15:05 | 2,208 | -10 |
| 23 Aug 2026, 10:18 | 2,218 | -23 |
| 20 Aug 2026, 01:26 | 2,241 | -11 |
| 16 Aug 2026, 17:47 | 2,252 | -3 |
| 12 Aug 2026, 23:00 | 2,255 | no change |
| 12 Aug 2026, 22:58 | 2,255 | first reading |
20 posts held, back to 7 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 12 August 2026. An engagement rate over an empty window would be a number about nothing.
ID 1 - 16k , inc ubot 22k ID 2 - 15k , inc ubot 20k ID 5 - 11k , inc ubot 18k ID 6 - 9k , inc ubot 16k fullgar userbot ( acc ban/limit nogar. ) , plan spesial ctc @MiuNatashza selalu ready acc idc nya
Signed Løvänsā. slow-respon @wajibrnk.
open ya jaseb promo , jaseb di lpm sfs promo & userbot promo send format formless ke @MiuNatashza
Signed Løvänsā. slow-respon @wajibrnk.
ID 1 - 16k , inc ubot 22k ID 2 - 15k , inc ubot 20k ID 5 - 11k , inc ubot 18k ID 6 - 9k , inc ubot 16k fullgar userbot ( acc ban/limit nogar. ) , plan spesial ctc @MiuNatashza selalu ready acc idc nya
Signed Løvänsā. slow-respon @wajibrnk.
yang belum claim garansi ke @miunatashza ya bawa bukti transaksi / claim g.a sebelumnya.
Signed Løvänsā. slow-respon @wajibrnk.
open ya jaseb promo , jaseb di lpm sfs promo & userbot promo send format formless ke @MiuNatashza
Signed Løvänsā. slow-respon @wajibrnk.
userbot @miuqbot avail pay otomatis di bot ya , fast proses juga kalau di bot
Signed Løvänsā. slow-respon @wajibrnk.
open ya jaseb promo , jaseb di lpm sfs promo & userbot promo send format formless ke @MiuNatashza
Signed Løvänsā. slow-respon @wajibrnk.
id 6 r2. inc bot 16k/acc , kosongan 9k/acc hit @MiuNatashza
Signed Løvänsā. slow-respon @wajibrnk.
yang belum claim garansi ke @miunatashza ya bawa bukti transaksi / claim g.a sebelumnya.
Signed Løvänsā. slow-respon @wajibrnk.
open ya jaseb promo , jaseb di lpm sfs promo & userbot promo send format formless ke @MiuNatashza
Signed Løvänsā. slow-respon @wajibrnk.
beli manual pake harga promo aja
Signed Løvänsā. slow-respon @wajibrnk.
🌟 Layanan Akses Reseller ℹ️ Apa itu Reseller? Fitur eksklusif yang memungkinkan Anda mencetak keuntungan dengan menjual kembali akses premium Userbot kepada pelanggan Anda sendiri. 👤 Status Akun: ❌ Nonaktif 💰 Harga Akses: Rp 50,000 perbulan 🧩 Pilih durasi paket reseller Anda di bawah ini.
Signed Løvänsā. slow-respon @wajibrnk.
Showing the 12 most recent of 20 posts we hold for @JASEBERA. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“JASEB ERA • OPEN UBOT 8k/BULAN” (@JASEBERA), 2,548 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/JASEBERA.
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.