Channel
@Nekei_4
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Declared links · Cite this entry
43subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002384600652 |
|---|---|
| Type | Channel |
| Username | @Nekei_4 |
| Description | Привет! Я - Nekei (Некей). Здесь вы найдете расписание стримов, важные новости о канале и т.д. Twitch - https://www.twitch.tv/nekei_4 Ютуб - https://www.youtube.com/@Nekei_4 ВК - https://vk.com/club236815934 |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Nekei_4 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 16:16 | 43 | no change |
| 8 Aug 2026, 10:02 | 43 | first reading |
20 posts held, back to 10 February 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 20 posts for this entry, the most recent from 15 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 10 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.
138 reactions across 20 posts, in 10 distinct kinds. The most used accounts for 30.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5460798261117869737 | 42 | 30.4% | |
| custom 5460805145950445943 | 40 | 29.0% | |
| custom 5460925039962514602 | 11 | 7.97% | |
| custom 5460717975294206787 | 10 | 7.25% | |
| custom 5461052390037806374 | 10 | 7.25% | |
| ❤ | 8 | 5.80% | |
| custom 5413794461152978282 | 7 | 5.07% | |
| 👀 | 6 | 4.35% | |
| custom 5460735885307831170 | 2 | 1.45% | |
| 👍 | 2 | 1.45% |
Custom emoji. 7 of the rows above are 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 20 of the 20 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 138reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 10 February 2026 to 15 June 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.
Сегодня в 19:00! Будут новые кубы, а еще я скачал блюстакс......😨 так что может постреляем чут чут 👺 📱Ютуб: https://www.youtube.com/@Nekei_4 📱Твич: https://www.twitch.tv/nekei_4
custom 54607982611178697374custom 54607179752942067871custom 54608051459504459431custom 54609250399625146021
Товарищи, стрим будет завтра в 19:00! 👺 Только не бейте.. Поиграем, расскажу куда пропадал, в конце можем залететь в гартик, если будет народ 😄 Если есть чо предложить, велком в комы 😼
custom 54608051459504459433custom 54609250399625146022custom 54607982611178697371
Товаристчи! Стример жив и здоров, просто сессия на носу 😴 Попробую сделать подруб в субботу или воскресенье на этой неделе 😼
custom 54607982611178697374custom 54608051459504459432custom 54609250399625146021
Стример почти воскресе, на днях подруб 😼
custom 54608051459504459435custom 54607982611178697373
Стример немного замболейло, постараюсь подрубить во вторник 😴😴
custom 54610523900378063747custom 54608051459504459432
Сегодня стрим в 18:00! Побегаем на сервере WebCraft и посмотрим ченть. 📱Ютуб: https://www.youtube.com/@Nekei_4 📱Твич: https://www.twitch.tv/nekei_4
custom 54607982611178697375👍2custom 54608051459504459431
🎉 Результаты розыгрыша: 🏆 Победители: 1. Direrage (@HTMLerCSSion) 2. 𝓐𝓻𝓲𝓷𝓪 Просьба победителям написать в сообщения канала для получения награды! ✔️Проверить результаты
👀5❤2custom 54608051459504459432custom 54607982611178697371
Стрим будет 26, как раз после подведения итогов розыгрыша. Можете пока накидать вариков, чо будем смотреть 🧐
custom 54607982611178697376custom 54608051459504459433
🕔🕕🕖🕗🕘🕙 Товарищи, настало время раздачи на спавне! Мы совместно с командой сервера в minecraft WebCraft подготовили для вас розыгрыш! Счастливчики получат 1000р на свой кошелёк в Steam, чтобы смачно закупиться на распродаже, а также проходку на сервер WebCraft на два месяца и подписку Web+ на месяц! Победителей будет двое, так что шансы есть у всех! Условия чисты, как слеза гаста: вам всего лишь нужно быть подписа…
custom 54608051459504459434custom 54607982611178697372custom 54610523900378063742❤1custom 54607358853078311701
Ну что, дропнем сегодня розыгрыш? 😄
custom 54607179752942067874custom 54137944611529782823
Сегодня в 18:30! Побегаем в хардкор майне и посмотрим майнкрафт лайв! 📱Ютуб: https://www.youtube.com/@Nekei_4 📱Твич: https://www.twitch.tv/nekei_4
custom 54607982611178697374custom 54608051459504459432
Чо будем сегодня майнкрафт лайф на стриме смотреть? 👀
custom 54137944611529782824custom 54608051459504459433
Showing the 12 most recent of 20 posts we hold for @Nekei_4. 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 — 645,321 of 1,480,688entries 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.
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.
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.
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.
3 URLs this entry has put in its own public description, shown exactly as written there. A declaration, not a verified association— we measured that the description contained this text, and nothing more. It is not a claim that this entry owns, runs or is connected to whatever the link resolves to; a description is text anyone controls, and anyone can put anyone else’s URL into it. How this is measured.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Nekei Stream” (@Nekei_4), 43 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/Nekei_4.
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.