18 Jul 2024, 13:27 UTC≈7,110 viewsread 12 August 2026
скоро, друзья. скоро.
Channel
borgáta
@B0RGATA
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
889subscribers
+0 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 | -1001604990082 |
|---|---|
| Type | Channel |
| Username | @B0RGATA |
| Description | ᴛы уйдᴇɯь, нᴏ я нᴇ ɜᴀᴋᴩᴏю дʙᴇᴩь. важное — @ardzninfo связь со мной — t.me/anonaskbot?start=1590460501 |
| Created | Between 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/B0RGATA |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 06:00 | 889 | no change |
| 12 Aug 2026, 05:46 | 889 | first reading |
Engagement
20 posts held, back to 14 October 2023 — 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 20 posts for this entry, the most recent from 18 July 2024. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 2
- Links
- 4
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
18 Jul 2024, 13:27 UTC≈7,130 viewsread 12 August 2026
У тебя новое анонимное сообщение! пж верни боргату я на неё дрочу ↩️ Свайпни для ответа.
4 May 2024, 16:58 UTC≈8,840 viewsread 12 August 2026
Sticker
Sticker, posted without a caption
4 May 2024, 16:58 UTC≈13,000 viewsread 12 August 2026
мне потребовалось потерять его, чтобы наконец найти себя.
15 Apr 2024, 08:40 UTC≈31,800 viewsread 12 August 2026
я знал, что тебе не нужен, но когда я услышал это из твоих уст, в мое сердце вонзилось сотни кинжалов, будто я имел надежду на большее.
27 Mar 2024, 16:02 UTC≈45,400 viewsread 12 August 2026
оставайся там, где улыбается твое сердце.
15 Mar 2024, 17:07 UTC≈42,900 viewsread 12 August 2026
ты так красиво смотришься со мной.
28 Feb 2024, 16:01 UTC≈46,600 viewsread 12 August 2026
позвони мне как-нибудь ночью. скажи, что скучаешь.
13 Feb 2024, 05:53 UTC≈43,700 viewsread 12 August 2026
позови и согрей меня. мне очень холодно. дай только пару часов моему телу, оно не справляется.
1 Feb 2024, 14:18 UTC≈41,800 viewsread 12 August 2026
красивые глаза могут быть у кого угодно, но один единственный человек может напеть алфавит так, что он навеки станет твоей любимой мелодией.
15 Jan 2024, 12:58 UTC≈38,600 viewsread 12 August 2026
я так скучал, но понимаю, что нам нельзя начинать сначала.
13 Jan 2024, 12:57 UTC≈38,600 viewsread 12 August 2026
не прикасайся к моим чувствам.
Showing the 12 most recent of 20 posts we hold for @B0RGATA. 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 — 972,508 of 1,169,250entries 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 2 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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“borgáta” (@B0RGATA), 889 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/B0RGATA.
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.