9 Jul 2026, 12:49 UTC101 views8 reactionsread 8 August 2026
Photo
%%% 🩶 Первый стамбульский дроп сейчас со скидками 🩶 несколько изделий ещё доступны к покупке на bipolarsiren.ru
custom 59538241970451288125custom 54201871162461526063
Channel
BIPOLAR SIREN
@bipolar_siren
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
193subscribers
+0 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 | -1002277671580 |
|---|---|
| Type | Channel |
| Username | @bipolar_siren |
| Description | [байпо́лар са́йрен] украшения в стиле русалочий панк жемчуг + пирсинг + устрицы заказать: t.me//what_katty_did сайт: https://bipolarsiren.ru иг: https://www.instagram.com/bipolar_siren?igsh=ZmZ6azRhb2VhYzEw |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/bipolar_siren |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 11:49 | 193 | no change |
| 7 Aug 2026, 16:58 | 193 | first reading |
Engagement
6 posts held, back to 29 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 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 6 posts for this entry, the most recent from 9 July 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 252
- Videos
- 5
- Links
- 10
Lifetime counters from Telegram’s own channel header, read 8 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.
Reaction mix
35 reactions across 6 posts, in 7 distinct kinds. The most used accounts for 28.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5427305775431169247 | 10 | 28.6% | |
| custom 5420187116246152606 | 6 | 17.1% | |
| custom 5447629732474558772 | 5 | 14.3% | |
| custom 5953824197045128812 | 5 | 14.3% | |
| custom 5325875252243229264 | 4 | 11.4% | |
| custom 5449908143905608474 | 3 | 8.57% | |
| custom 5323430694297303845 | 2 | 5.71% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.
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 35reactions 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 29 May 2026 to 9 July 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
9 Jul 2026, 10:52 UTC104 views12 reactionsread 8 August 2026
Photo
Русалочки, Отпуск продлевается до 14.07, но я прилечу со стамбульскими ракушками и будет Istanbul drop#2
custom 54273057754311692477custom 54476297324745587725
18 Jun 2026, 10:55 UTC205 views3 reactionsread 8 August 2026
Photo
Подборка пар серёжек с разными жемчужинами Цены в комментариях ✨
custom 54499081439056084743
17 Jun 2026, 20:02 UTC213 views6 reactionsread 8 August 2026
Photo
🤍 жемчуг, сталь, родированная латунь UPD: все проданы заказ @what_katty_did
custom 53258752522432292644custom 53234306942973038452
1 Jun 2026, 15:14 UTC250 views3 reactionsread 8 August 2026
Photo
MARIE ANTOINETTE натуральный жемчуг, гематит Чокер 35-40 см 7900.- Ожерелье 40-45 см 8200.-
custom 54273057754311692473
29 May 2026, 14:37 UTC228 views3 reactionsread 8 August 2026
Photo
ожерелье 𝖆𝖋𝖎𝖓𝖆 🌟 натуральный жемчуг, гематит, сталь длина 43-53 см, регулируется 8900.- в единственном экземпляре заказ @what_katty_did
custom 54201871162461526063
Showing the 6 most recent of 6 posts we hold for @bipolar_siren. 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 — 1,027,814 of 1,481,243entries 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 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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“BIPOLAR SIREN” (@bipolar_siren), 193 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/bipolar_siren.
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.