Telegram RegisterThe public register of Telegram
Telegram profile photo for π–₯» π‚π‘π«π’π¬π­π’πšπ§ 𝐒πͺ !BUBAR.

Channel

π–₯» π‚π‘π«π’π¬π­π’πšπ§ 𝐒πͺ !BUBAR.

@christiansq

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

112subscribers

-1 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1001324024133
TypeChannel
Username@christiansq
CreatedBetween 1 March 2018 and 31 August 2021 β€” estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live27 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 27 August 2026
On Telegramt.me/christiansq

Growth

112113112.512 August 2026 β€” 113 subscribers12 August 2026 β€” 113 subscribers27 August 2026 β€” 112 subscribers12 August 202627 August 2026
3 measurements spanning 15 days, net -1. 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 112–113 and does not start at zero.
Measurement log β€” every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Aug 2026, 18:22112-1
12 Aug 2026, 09:45113no change
12 Aug 2026, 09:32113first reading

Engagement

18 posts held, back to 19 January 2022 β€” 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 18 posts for this entry, the most recent from 23 December 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
2m 10s
Average length
2m 10s

Measured directly from 1 video 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

24 Mar 2022, 17:00 UTC718 viewsread 12 August 2026

Jumat, 25 Maret 2022 Shalom, selamat pagi/siang/sore/malam. Saya Meira Nyxley ddΔ“ Orion selaku admin inti dari Christian Sq dengan berat hati menyatakan bahwa @ChristianSq tidak akan beroperasi lagi, dalam artian Christian Sq resmi di BUBARKAN. Keputusan ini diambil setelah dibicarakan dan disepakati admin inti Christian Sq. Username @ChristianSq akan di keep untuk menghindari hal hal yang tidak diinginkan. Saya min…

24 Jan 2022, 16:02 UTC623 viewsread 12 August 2026
Forwarded from @flywithelPhoto

Shalom temen teman, mohon bantuan bagi yang berdomisili di kota Medan, bantu donor darah A+ , pendonor diusahakan laki laki, ada temen sangat butuh Nama : Jonathan Marpaung. Skrng hb Jonathan hanya 18.000, masih jauh untuk bisa 150.000 masih banyak butuh pendonor lagi Mohon bantuan nya, terima kasih πŸ™πŸ»

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

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.

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 27 August 2026 β€” this entry's latest reading, not the date you are reading this.

β€œπ–₯» π‚π‘π«π’π¬π­π’πšπ§ 𝐒πͺ !BUBAR.” (@christiansq), 112 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/christiansq.

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.