Telegram RegisterThe public register of Telegram
Telegram profile photo for В нижнем белье.

Channel

В нижнем белье.

@vnijne

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

2,330subscribers

+588 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002160193028
TypeChannel
Username@vnijne
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live8 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/vnijne

Growth

1,7422,3302,0367 August 2026 — 1,742 subscribers7 August 2026 — 1,742 subscribers8 August 2026 — 1,753 subscribers10 August 2026 — 1,804 subscribers14 August 2026 — 2,065 subscribers17 August 2026 — 2,030 subscribers20 August 2026 — 2,003 subscribers24 August 2026 — 1,980 subscribers27 August 2026 — 2,020 subscribers31 August 2026 — 2,019 subscribers3 September 2026 — 1,994 subscribers8 September 2026 — 2,330 subscribers7 August 20268 September 2026
12 measurements spanning 32 days, net +588. 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 1,654–2,418 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 11:392,330+336
3 Sept 2026, 01:161,994-25
31 Aug 2026, 00:152,019-1
27 Aug 2026, 20:332,020+40
24 Aug 2026, 10:531,980-23
20 Aug 2026, 08:542,003-27
17 Aug 2026, 10:382,030-35
14 Aug 2026, 04:482,065+261
10 Aug 2026, 17:271,804+51
8 Aug 2026, 01:481,753+11
7 Aug 2026, 15:481,742no change
7 Aug 2026, 14:171,742first reading

Engagement

15 posts held, back to 26 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 15 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
46s
Average length
23s

Measured directly from 2 videos 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.

Reaction mix

4 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 75.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
375.0%
🔥125.0%

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 3 of the 15 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 15 most recent posts we hold, published 26 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.

Advertising

Ad load
6.67%
1 of 15 posts carry an ad marker
Regulatory tokens
0
none — marked by hashtag only
Median views · ads
145
over 1 measured post
Median views · rest
430
over 14 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Measured over the 15 most recent posts we hold, published 26 July 2026 to 7 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

5 Aug 2026, 21:22 UTC145 viewsread 7 August 2026
AdvertisementVideo

Мега порно папка на сотни каналов для взрослых. Подпишись на все каналы по одной ссылке. 🔥 https://t.me/addlist/2zDKYFRR8TkyZDcy 🍓 https://t.me/addlist/2zDKYFRR8TkyZDcy #реклама

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

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.

“В нижнем белье.” (@vnijne), 2,330 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/vnijne.

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.