Telegram RegisterThe public register of Telegram
Telegram profile photo for bzrc

Channel

bzrc

@bizarrica

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

97subscribers

+1 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-1001929713243
TypeChannel
Username@bizarrica
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live15 September 2026
Measurements held4
Confirmed unchanged2 times, most recently 15 September 2026
On Telegramt.me/bizarrica

Growth

9698978 August 2026 — 96 subscribers9 August 2026 — 96 subscribers30 August 2026 — 98 subscribers8 September 2026 — 97 subscribers8 August 20268 September 2026
4 measurements spanning 31 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 96–98 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 14:3897-1
30 Aug 2026, 21:4498+2
9 Aug 2026, 12:0396no change
8 Aug 2026, 06:0196first reading

Engagement

13 posts held, back to 17 May 2026 — 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 13 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
7s
Average length
7s

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

8 Aug 2026, 18:30 UTC35 viewsread 9 August 2026

золото атомных кружев под крылом если я вижу прекрасное, значит стыд не забил меня до смерти

14 Jul 2026, 20:31 UTC137 viewsread 9 August 2026

либештод (нем. liebestod) — добровольный уход из жизни обоих возлюбленных во имя любви

13 Jul 2026, 06:49 UTC130 viewsread 9 August 2026
Photo

from the series 'Five People Thinking The Same Thing' | Frances Kearney

9 Jul 2026, 07:37 UTC132 viewsread 9 August 2026
Photo

0807 :: какую форму принимает дистанция?

26 May 2026, 15:04 UTC248 viewsread 9 August 2026
Forwarded from @suspiriabarPhoto

Фотоклуб «Отпечаток» и бар «Суспирия» представляют фестиваль фотографии и музыки «Аналог» 📸 Для тех, кто уже увлекается фотографией или только хочет начать, — мастер-классы, лекции и выставка. Для любителей аналоговой музыки — кассетные и лайв-сеты в обоих залах бара. Программа фотоклуба: 🔹 18:00 — 02:00 Выставка фотоклуба «Отпечаток» 🔹 18:00 — 20:00 Мастер-класс «Изготовление и съëмка на пинхол-камеры» 🔹 20:00 — 2…

25 May 2026, 22:35 UTC194 viewsread 9 August 2026
Photo

26: следы дождя на всём, что меня касается — следы дождя на всём, к чему я прикасаюсь

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

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.

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

“bzrc” (@bizarrica), 97 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/bizarrica.

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.