Telegram RegisterThe public register of Telegram

Channel

FORMAT BOOKING CSO

@BOOKINGCSO

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

12subscribers

+0 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1001137209314
TypeChannel
Username@BOOKINGCSO
Created26 June 2021measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
On Telegramt.me/BOOKINGCSO

Growth

128 August 2026 — 12 subscribers12 August 2026 — 12 subscribers8 August 202612 August 2026
2 measurements spanning 4 days. 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 11–13 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 06:0112no change
8 Aug 2026, 15:3112first reading

Engagement

17 posts held, back to 26 June 2021the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 27 March 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
1

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

28 Sept 2021, 18:04 UTC≈3,030 viewsread 12 August 2026

೫ ⃟ ཹ։༉‧₊ 𝓕𝙊𝙍𝙈𝘼𝙏 𝓒𝙃𝘼𝙉𝙉𝙀𝙇 𝓟𝘼𝙍𝙏𝙔۝೫ ﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋ O1. 𝐍ama 𝐏arty ༉‧₊⇝ O2. 𝐔sername channel yg party ༉‧₊⇝ O3. 𝐔sername PJ ..⃗. 「 @.usn PJ min 3 」 ༉‧₊⇝ O4. 𝐌enggunakan medpart atau tidak ༉‧₊⇝ O5. 𝐓ema party ..⃗. 「 Jelaskan secara rinci 」 ༉‧₊⇝ O6. 𝐏lace, 𝐃ate, 𝐓ime ༉‧₊⇝ O7. 𝐌enggunakan game? Untuk game dari pihak kami atau kalian? (n)..⃗. 「 Jika dari kalian, silahkan jelaskan + sebutkan game nya secara rin

8 Jul 2021, 14:09 UTC≈4,260 viewsread 12 August 2026

೫ ⃟ ཹ։༉‧₊ 𝓕𝙊𝙍𝙈𝘼𝙏 𝓐𝙉𝙉𝙄𝙑 / 𝓜𝙀𝙉𝙎𝙄𝙑𝙀 𝓒𝙊𝙐𝙋𝙇𝙀 𝓟𝘼𝙍𝙏𝙔۝೫ ﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋ O1. 𝐍ama lengkap kedua pasangan ༉‧₊⇝ Pria / Dom : nn + chr + @.usn ༉‧₊⇝ Wanita / Sub : nn + chr + @.usn O2. Place, Date, Time ༉‧₊⇝ O3. 𝐃ress 𝐂ode ༉‧₊⇝ O4. 𝐆uest 𝐒tar ..⃗. 「 song max 2 」 ༉‧₊⇝ O5. 𝐒ouvenir ༉‧₊⇝ O6. 𝐌enggunakan Game? ༉‧₊⇝ ╾╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╸ ੈ✎° NOTED : Dimohon untuk cek kembali format nya apakah sudah benar atau be

5 Jul 2021, 20:55 UTC≈4,870 viewsread 12 August 2026

೫ ⃟ ཹ։༉‧₊ 𝓕𝙊𝙍𝙈𝘼𝙏 𝓖𝙐𝙀𝙎𝙏 𝓢𝙏𝘼𝙍۝೫ ﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋ O1. 𝐍ama acara ༉‧₊⇝ wedding / birthday / mensive party O2. 𝐔sername PJ Acara ༉‧₊⇝ @. O3. 𝐏lace, 𝐃ate, 𝐓ime ༉‧₊⇝ O4. 𝐆uest 𝐒tar ..⃗. 「 song max 2 」 ༉‧₊⇝ ༉‧₊⇝ ╾╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╸ ੈ✎° NOTED : Dimohon untuk cek kembali format nya apakah sudah benar atau belum. ੈ✎° 𝐉ika sudah kirim ke bot ; ..⃗. ‧₊ @CSOFCBOT ‧₊ ੈ✎° Auto copy ⓒ COME & SHINE ORGANIZER

26 Jun 2021, 15:13 UTC≈5,760 viewsread 12 August 2026

TANGGAL BOOKING BULAN MEI 01. 🅾 02. 🅾 03. 🅾 04. 🅾 05. 🅾 06. 🅾 07. 🅾 08. 🅾 09. 🅾 10. 11. 12. 13. 14. 15. 16. 🅾 17. 18. 19. 20. 21. 22. 23. 🅾 24. 25. 26. 🅾 27. 28. 29. 30. 🅾 31. note. 🅾 : libur 👫 : Wedding party 👑 : Birthday party 🎀 : Couple party 🪅 : Channel party 🌟 : Guest Star - : Custom party - : Staff rent ✅ : Telah diselenggarakan ❌ : Dibatalkan ⓒ COME & SHINE ORGANIZER

26 Jun 2021, 15:12 UTC≈5,840 viewsread 12 August 2026

೫ ⃟ ཹ։༉‧₊ 𝓕𝙊𝙍𝙈𝘼𝙏 𝓑𝙄𝙍𝙏𝙃𝘿𝘼𝙔 𝓟𝘼𝙍𝙏𝙔۝೫ ﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋﹋ O1. 𝐍ama lengkap yang berulang tahun ༉‧₊⇝ nn + chr + usn O2. Place, Date, Time ༉‧₊⇝ O3. 𝐃ress 𝐂ode ༉‧₊⇝ O4. 𝐆uest 𝐒tar ..⃗. 「 song max 2 」 ༉‧₊⇝ O5. 𝐒ouvenir ༉‧₊⇝ O6. 𝐌enggunakan Game? ༉‧₊⇝ ╾╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╸ ੈ✎° NOTED : Dimohon untuk cek kembali format nya apakah sudah benar atau belum. ੈ✎° 𝐉ika sudah kirim ke bot ; ..⃗. ‧₊ @CSOFCBOT ‧₊ ੈ✎° Au

Showing the 12 most recent of 17 posts we hold for @BOOKINGCSO. 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.

Citation-graph rank

Citation-graph rank — 754,166 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 5 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.

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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“FORMAT BOOKING CSO” (@BOOKINGCSO), 12 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/BOOKINGCSO.

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.