5 measurements spanning 23 days, net -5. 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 414–421 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
31 Aug 2026, 12:47
415
-2
24 Aug 2026, 06:34
417
-1
17 Aug 2026, 09:38
418
-2
9 Aug 2026, 00:53
420
no change
8 Aug 2026, 09:31
420
first reading
Engagement
15 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 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 12 March 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
7m 30s
Average length
1m 04s
Measured directly from 7 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
1,249 reactions across 13 posts, in 14 distinct kinds. The most used accounts for 24.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5197582693621079540
311
24.9%
custom 5195045982856844571
276
22.1%
custom 5195063811266092126
206
16.5%
custom 5318952018365130187
157
12.6%
custom 5202060553509445012
82
6.57%
custom 5197399577690410230
59
4.72%
custom 5204041736023737408
42
3.36%
custom 5197292169148271388
31
2.48%
custom 5197378253177789757
31
2.48%
custom 5192907071963567497
30
2.40%
custom 5201714297541003593
13
1.04%
custom 5199893716738806705
8
0.641%
custom 5197319751428247417
2
0.16%
custom 5197196588946071450
1
0.08%
Custom emoji. Every 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 counts beside them are Telegram’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 13 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 1,249 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 10 February 2026 to 12 March 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
5
across the posts below
Posts paid on
5
of 13 we hold a reading for · 38%
Most on one post
1
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @neyrotonin. 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 15 most recent posts we hold for this entry, published 10 February 2026 to 12 March 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.
Прошёл уже месяц с выезда и мы собрали плейлист, чтобы вспомнить, как это было
😮Слушайте на площадках:
😢Яндекс Музыка
😢ВКонтакте
😢Spotify
😵💫 Нашли пасхалки плейлиста во ВКонтакте?
#МыКоманда2026 #Нейротонин #Плейлист
⭐️⭐️⭐️⭐️⭐️⭐️⭐️
😄🫤🤜🤣😅😀
😖Это просто награда? Нет. Это история, точнее множество историй, которые вместе приводят к чему-то гораздо большему...
☀️Мы объединили две разных эпохи — прошлое и будущее и решили показать, что значит для нас выезд "Мы - команда".
Все усилия не прошли даром, мы выросли как личности и стали друг для друга настоящей семьёй 😮
🤝🤜🖕🫶👏🫸👏🤝😼🤝
⭐️⭐️⭐️⭐️ ➖
Сияем внутри, озаряя вокруг. И не важно, сколь…
😖😚🤭 😎😀😈😀😖
😮Огонь и вода, логин и пароль, левая и правая палочка Твикс, так же идеально друг другу подходят Нейротонин и Р.И.Т.М., согласны?
#МыКоманда2026 #МыКоманда2025 #Нейротонин #РИТМ
Всё когда-нибудь становится красивым «финалом».
😎Наша команда закрывает главу - без драмы, но с огромной благодарностью.
Это было про идеи, смех в чатах в 3 ночи, горящие дедлайны и людей, которые делали невозможное возможным.
😮Мы не пропадаем - просто расходимся по своим привычным местам. И вот где нас можно найти:
😮Вика - кэп
😮Леша - клипер
😮Варя - копирайтер
😮Настя - та, которая дизайнер
😮Тимур - дизайнер
😮Лера - …
😄😈🤜😊 😇🫶😼😄🤜🫸
😮Вместе с командой Рефлекс хотим поздравить вас с днём всех влюблённых
В честь этого события выкладываем видео со свадьбы, как это было с каждой из сторон!
😮Как прошёл день невесты можете узнать у нас, а чтобы увидеть как это было от лица жениха, переходите в канал Рефлекса и смотрите видео там
#Свадьба
#Нейротонин
#МыКоманда2026
Showing the 12 most recent of 15 posts we hold for @neyrotonin. 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.
Mentions
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.
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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@neyrotonin named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@q8935219 named in 1 post, 9 August 2026 – 9 August 2026
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 31 August 2026 — this
entry's latest reading, not the date you are reading this.
“Нейротонин” (@neyrotonin), 415 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/neyrotonin.
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.