Telegram RegisterThe public register of Telegram
Telegram profile photo for III. ➀ 莱拉尼亚。 | KEDAI BUJANG

Channel

III. ➀ 莱拉尼亚。 | KEDAI BUJANG

@kedaibujang

On this record: Growth · Engagement · Posts · Citations · Cite this entry

493subscribers

-35 since we began measuring on 13 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002304715566
TypeChannel
Username@kedaibujang
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live5 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/kedaibujang

Growth

493528510.513 August 2026 — 528 subscribers14 August 2026 — 527 subscribers20 August 2026 — 514 subscribers27 August 2026 — 512 subscribers5 September 2026 — 493 subscribers13 August 20265 September 2026
5 measurements spanning 23 days, net -35. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 488–533 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 05:37493-19
27 Aug 2026, 19:37512-2
20 Aug 2026, 21:34514-13
14 Aug 2026, 16:04527-1
13 Aug 2026, 16:17528first reading

Engagement

17 posts held, back to 15 June 2025the 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 17 posts for this entry, the most recent from 1 March 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

1 Mar 2026, 16:14 UTC64 viewsread 13 August 2026
Photo

Jajan teleprem fast, order di bot atau ke @kdekan

Signed Vantae

8 Feb 2026, 06:05 UTC96 viewsread 13 August 2026

Ufs @dolminan, @xbujang, @wpelir, @boajak @oMandor

Signed Vantae

17 Jan 2026, 02:22 UTC115 viewsread 13 August 2026
Photo

Sabtu Minggu libur, yang mau premin akun tele boleh banget harganya masih sama di 58.000 sebulan. Premin akun tele paling lama 5 menit ya guys bisa ke bot @kedaibujang/ @kdekan

Signed Vantae

3 Nov 2025, 08:14 UTC156 viewsread 13 August 2026
Photo

Saldo stars gue segini, kalau ada yang minat bisa ke @Kdekan atau @kedaibujangbot

Signed Vantae

3 Nov 2025, 08:13 UTC121 viewsread 13 August 2026

Yang mau jasa upg gift bisa ya, stars dari gue

Signed Vantae

1 Aug 2025, 07:26 UTC224 viewsread 13 August 2026

Gue jualan kalau ada yang beli, kalau nggak ada yang beli nggak jualan ges

20 Jun 2025, 07:21 UTC486 viewsread 13 August 2026
Photo

Buat semuanya, gue mau informasi sedikit ini penting banget buat kalian yang punya gift upgrade. So please kalian boleh fw bbc dari store ini kemana aja. Jadi nanti kalau ada akun @zMbSzcQFUsrR sebar sesuatu yang mengarah ke bot spinner @SpinGiftsReBot. Usahakan kalian jangan coba-coba, nanti bakalan di arahkan ke tele bisnis untuk pasang chat bot otomatis nah kalau kalian pasang bot itu dan ngasih akses buat terima

Showing the 12 most recent of 17 posts we hold for @kedaibujang. 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 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 5 September 2026 — this entry's latest reading, not the date you are reading this.

“III. ➀ 莱拉尼亚。 | KEDAI BUJANG” (@kedaibujang), 493 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/kedaibujang.

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.