Telegram RegisterThe public register of Telegram
Telegram profile photo for BAZILIKA

Channel

BAZILIKA

@the_bazilika

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

265subscribers

-4 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003375060338
TypeChannel
Username@the_bazilika
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live31 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 31 August 2026
On Telegramt.me/the_bazilika

Growth

2652732697 August 2026 — 269 subscribers8 August 2026 — 269 subscribers15 August 2026 — 273 subscribers24 August 2026 — 268 subscribers31 August 2026 — 265 subscribers7 August 202631 August 2026
5 measurements spanning 24 days, net -4. 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 264–274 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 16:02265-3
24 Aug 2026, 04:23268-5
15 Aug 2026, 20:23273+4
8 Aug 2026, 08:50269no change
7 Aug 2026, 23:51269first reading

Engagement

6 posts held, back to 27 July 2026the 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.

ERR · 30 days
15.8%
avg views ÷ 265 subscribers
Avg views / post
42.0
2 posts measured
Reaction rate
17.9%
reactions ÷ views · ER floor
Posts in window
2
of 6 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held6 (27 July 20267 August 2026)
Views total84
Reactions total15
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 08:50 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

49 reactions across 6 posts, in 5 distinct kinds. The most used accounts for 32.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1632.7%
😍1122.4%
🥰918.4%
🕊714.3%
🔥612.2%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 6 of the 6 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 49 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 6 most recent posts we hold, published 27 July 2026 to 7 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

7 Aug 2026, 16:05 UTC31 views6 reactionsread 8 August 2026
Photo

Выбор: Marieke Vannieuwenhuyse Платье макси с открытой спиной и воротником на пуговицах в молочном цвете. 33 970 рублей.

2😍2🔥1🥰1

Signed BAZILIKA

5 Aug 2026, 16:03 UTC53 views9 reactionsread 8 August 2026
Photo

Топ из вискозного шелка в молочном цвете. Отлично подойдет к вечернему выходу, а также для повседневной носки. 16 990 рублей.

3🕊3🥰3

Signed BAZILIKA

3 Aug 2026, 16:02 UTC69 views8 reactionsread 8 August 2026
Photo

Выбор: Milena Bessonova Кардиган из натурального премиального кашемира в светло-сером оттенке. 49 970 рублей.

3😍3🕊1🥰1

Signed BAZILIKA

31 Jul 2026, 16:04 UTC104 views9 reactionsread 8 August 2026
Photo

Рубашка оверсайз из хлопка в молочном цвете и брюки из струящейся ткани на резинке в черном цвете. Рубашка 19 990 рублей Брюки 16 590 рублей Весь образ доступен на нашем сайте.

3🔥3🕊2😍1

Signed BAZILIKA

29 Jul 2026, 16:04 UTC113 views9 reactionsread 8 August 2026
Photo

Выбор Sofia Ruutu Платье с открытой спиной из струящейся ткани в молочном цвете. 29 950 рублей Отличный выбор для особого вечера, а также для круиза.

3🥰3😍3

Signed BAZILIKA

27 Jul 2026, 16:01 UTC98 views8 reactionsread 8 August 2026
Photo

Двубортный приталенный жакет в черном цвете из костюмной ткани. 26 890 рублей. Жакет доступен в молочном цвете.

2🔥2😍2🕊1🥰1

Signed BAZILIKA

Showing the 6 most recent of 6 posts we hold for @the_bazilika. 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.

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

“BAZILIKA” (@the_bazilika), 265 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/the_bazilika.

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.