Telegram RegisterThe public register of Telegram

Channel

Никита и компания

@nikit_nest

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

5,508subscribers

+9 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1002216738686
TypeChannel
Username@nikit_nest
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live14 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/nikit_nest

Growth

5,4995,5085,503.514 Aug 2026, 04:18 — 5,499 subscribers14 Aug 2026, 21:09 — 5,508 subscribers14 Aug 2026, 04:1814 Aug 2026, 21:09
2 measurements taken within a single day, net +9. 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 5,498–5,509 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 21:095,508+9
14 Aug 2026, 04:185,499first reading

Engagement

18 posts held, back to 30 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
33.6%
avg views ÷ 5,508 subscribers
Avg views / post
1,850
18 posts measured
Reaction rate
9.94%
reactions ÷ views · ER floor
Posts in window
18
of 18 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 13 August 2026
Posts held18 (30 July 202613 August 2026)
Views total33,265
Reactions total3,305
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Aug 2026, 04:18 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
17m 21s
Average length
1m 09s

Measured directly from 15 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

3,305 reactions across 18 posts, in 16 distinct kinds. The most used accounts for 27.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤣89927.2%
😁81024.5%
🔥50215.2%
❤‍🔥3299.95%
custom 57850046577303915892286.90%
🥰1765.33%
😢1163.51%
👏762.30%
😭501.51%
🗿310.938%
🤪310.938%
🤯260.787%
🐳110.333%
80.242%
🤔70.212%
🥱50.151%

Custom emoji. One 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 count beside it isTelegram’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 18 of the 18 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 3,305reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 30 July 2026 to 13 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.

Telegram Stars

Stars received
11
across the posts below
Posts paid on
5
of 18 we hold a reading for · 28%
Most on one post
3
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @nikit_nest. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 18 most recent posts we hold for this entry, published 30 July 2026 to 13 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

13 Aug 2026, 19:43 UTC≈1,770 views126 reactions1 Starread 14 August 2026
Video

Секретный рецепт передающийся из поколения в поколение

🤣89🔥18custom 578500465773039158911❤‍🔥6👏1😁1

13 Aug 2026, 08:58 UTC915 views152 reactionsread 14 August 2026
Photo

Ни дня без подарков от подписчиков 🥰

🔥95🥰33custom 578500465773039158918❤‍🔥4👏2

12 Aug 2026, 20:28 UTC≈1,100 views140 reactionsread 14 August 2026
Video

А у вас есть такой? 😅

🔥60😁38🤪16🤣11❤‍🔥7🤔4custom 57850046577303915892🐳1

11 Aug 2026, 19:41 UTC≈1,280 views176 reactionsread 14 August 2026
Video

Не кофейня, а проходной двор 😭

🤣131custom 578500465773039158917😁16😢6🗿2❤‍🔥1🔥1🤯1

10 Aug 2026, 19:34 UTC≈1,450 views117 reactionsread 14 August 2026
Video

Новая «Варочная» в Екатеринбурге, по адресу Московская 251. 15 августа официальное открытие и акция «Плати за кофе сколько хочешь»

🥰66🔥35custom 578500465773039158910❤‍🔥5😁1

9 Aug 2026, 11:01 UTC≈1,780 views259 reactionsread 14 August 2026
Photo

Всё гениальное - просто! 😎

😁178👏32custom 578500465773039158919🤣14🔥53❤‍🔥3🗿2

8 Aug 2026, 20:27 UTC≈1,700 views144 reactionsread 14 August 2026
Video

Вишенка на торте в конце смены 😭

😁61😭30custom 578500465773039158929🔥10🤪5🐳3🗿2🥱2

8 Aug 2026, 16:10 UTC≈1,560 views138 reactions2 Starsread 14 August 2026
Video

Минутка философии 😅

🔥66😁40❤‍🔥14🤣7👏5custom 57850046577303915893🥰2🥱1

7 Aug 2026, 20:20 UTC≈1,670 views161 reactionsread 14 August 2026
Video

Тысяча и одна причина уйти раньше.. 😭

🤣104😁29❤‍🔥10😭6🔥5custom 578500465773039158932🐳1

6 Aug 2026, 20:58 UTC≈1,710 views200 reactions3 Starsread 14 August 2026
Video

Зато всегда есть, что рассказать 😂

😁115🤣56custom 578500465773039158916❤‍🔥7🔥5🗿1

6 Aug 2026, 09:50 UTC≈2,050 views279 reactions2 Starsread 14 August 2026
Photo

Это очень смешно 🤣

🤣216custom 578500465773039158930🗿15🤪6🐳4🤯3❤‍🔥2🔥2

5 Aug 2026, 20:56 UTC≈1,880 views140 reactionsread 14 August 2026
Video

Честный обзор на новый напиток Varka Fest

🔥91❤‍🔥21🤣16custom 57850046577303915897😁3🐳1🗿1

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 563,724 of 1,345,403entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“Никита и компания” (@nikit_nest), 5,508 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/nikit_nest.

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.