13 May 2026, 21:06 UTC≈5,170 viewsread 6 August 2026
https://youtu.be/HvE48ZlPhO4 полный разбор ответки Нагибайки, доступ по ссылке
Channel
скриншоты
@informationnagibayka
On this record: Growth · Engagement · Posts · Citations · Cite this entry
690subscribers
-5 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003414216086 |
|---|---|
| Type | Channel |
| Username | @informationnagibayka |
| Created | Between 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/informationnagibayka |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 01:15 | 690 | -5 |
| 6 Aug 2026, 21:14 | 695 | no change |
| 6 Aug 2026, 17:47 | 695 | first reading |
Engagement
13 posts held, back to 11 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 13 posts for this entry, the most recent from 13 May 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
13 May 2026, 20:23 UTC≈5,250 viewsread 6 August 2026
https://nagibayka.notion.site/35e9c507eec3800caf6be5ad34b87047 оправдательный пост Нагибайки
12 May 2026, 15:58 UTC≈8,500 viewsread 6 August 2026
https://youtu.be/rStSqrNuUQ0 не хочу делать по этому нарезку полноценно байтерское название писать там вообще не про это история, просто залил в доступе по ссылке, всем, до кого надо, эта инфа и так дойдет
12 May 2026, 13:08 UTC≈8,460 viewsread 6 August 2026
Photo
Нагибайка написал гипотетической жертве незадолго до возможного придания огласке событий с целью убедить ее, что ей же лучше, если о ситуации никто не будет знать, и что нужно, чтобы она высказалась от своего лица со словами о том, что "не нужно лезть не в свое дело"
11 May 2026, 20:45 UTC≈7,910 viewsread 6 August 2026
Photo
показания Нагибайки и гипотетической жертвы расходятся, она утверждает, что не давала никакого согласия
11 May 2026, 20:38 UTC≈7,450 viewsread 6 August 2026
Photo
Photo, posted without a caption
11 May 2026, 20:38 UTC≈7,230 viewsread 6 August 2026
Photo
Photo, posted without a caption
11 May 2026, 20:38 UTC≈6,930 viewsread 6 August 2026
Photo
Photo, posted without a caption
11 May 2026, 19:48 UTC≈6,920 viewsread 6 August 2026
Photo
первые комментарии Нагибайки касательно слухов о случившемся
11 May 2026, 19:35 UTC≈6,840 viewsread 6 August 2026
Photo
небольшое количество скриншотов обусловлено тем, что переписку с гипотетической жертвой Нагибайка удалил
11 May 2026, 19:33 UTC≈7,020 viewsread 6 August 2026
Photo
Photo, posted without a caption
11 May 2026, 19:30 UTC≈6,920 viewsread 6 August 2026
File
запись разговора в дискорде с подтверждением факта случившейся ситуации самой гипотетической жертвой и частичным описанием произошедшего, голос изменен
Showing the 12 most recent of 13 posts we hold for @informationnagibayka. 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 — 604,629 of 1,480,975entries 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 4 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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“скриншоты” (@informationnagibayka), 690 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/informationnagibayka.
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.