4 Nov 2021, 14:43 UTC299 viewsread 10 August 2026
Pernah berkata dia takut kehilangan dan terganti dengan yang lain dan sekarang kata itu sedang terjadi , bagaimana dengan masa akan datang dia bukan bersamaku lagi? @bulandanbintang ✨
Channel
『 ɓմʆαη & ɓίηէαηɠ 』
@bulandanbintang
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
62subscribers
-2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001443711146 |
|---|---|
| Type | Channel |
| Username | @bulandanbintang |
| Created | Between 1 April 2019 and 25 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/bulandanbintang |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 15:55 | 62 | -2 |
| 10 Aug 2026, 02:47 | 64 | no change |
| 6 Aug 2026, 17:37 | 64 | first reading |
Engagement
20 posts held, back to 25 July 2021 — 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 4 November 2021. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 1m 02s
- Average length
- 31s
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Recent posts
31 Oct 2021, 16:25 UTC307 viewsread 10 August 2026
Ya tuhan kembalikanlah bulan dan bintang yang pernah menyatu seuatu ketika dulu , hanya harapku di bulan baru ini . @bulandanbintang ✨🌑
31 Oct 2021, 16:22 UTC314 viewsread 10 August 2026
Di bulan baru ini aku masih merindukan bintang yang sama😔 @bulandanbintang ✨
30 Oct 2021, 11:54 UTC307 viewsread 10 August 2026
Video
Masih di sini @bulandanbintang ✨
28 Oct 2021, 10:53 UTC202 viewsread 10 August 2026
tidak tahulah macam mana nak bagi orang tu percaya kita balik penat lah😔😭 @bulandanbintang ✨
27 Oct 2021, 11:13 UTC194 viewsread 10 August 2026
Bukannya berharap namun perasaan nyaman yang membuatkan ingin terus bersama . @bulandanbintang ✨
26 Oct 2021, 15:30 UTC192 viewsread 10 August 2026
terima kasih tuhan telah pertemukan orang yang pernah menyayangiku kembali , andai ini salah satu takdir permudahkanlah , andai ini satu ujian tabahkanlah . @bulandanbintang ✨
26 Oct 2021, 15:27 UTC183 viewsread 10 August 2026
Tidak tahu nak kata apa , tapi masih mencoba mengikhlaskan dia pergi dan menerima orang yang ingin membahagiakan cerita ini. @bulandanbintang ✨
24 Oct 2021, 13:05 UTC169 viewsread 10 August 2026
Teruntuk kamu , Boleh tak sebelum engkau betul" tidak ingin memiliki aku kita bertemu ? Tak minta masa yang lama untuk pertemuannya singkat saja sudah mencukupi , aku ingin memberi sesuatu yang berharga kepada mu . Harap ego mu tidak membatasinya . @bulandanbintang ✨
17 Oct 2021, 16:08 UTC168 viewsread 10 August 2026
Emm selamat malam sajalah😁 @bulandanbintang 🐢
17 Oct 2021, 16:07 UTC164 viewsread 10 August 2026
Sakit siak kena tipu @bulandanbintang 🐢
5 Sept 2021, 15:25 UTC223 viewsread 10 August 2026
Selamat malam mimpi indah 💗 @bulandanbintang ✨
Showing the 12 most recent of 20 posts we hold for @bulandanbintang. 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.
Mentions
Named by 2 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.
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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“『 ɓմʆαη & ɓίηէαηɠ 』” (@bulandanbintang), 62 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/bulandanbintang.
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.