Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 96% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
Growth
28 measurements spanning 97 days, net +875. 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,222–6,359 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 28
Measured (UTC)
Subscribers
Change
11 Nov 2026, 07:38
6,228
+25
7 Nov 2026, 13:20
6,203
+44
4 Nov 2026, 19:39
6,159
-13
1 Nov 2026, 23:26
6,172
+25
30 Oct 2026, 07:17
6,147
-1
27 Oct 2026, 03:10
6,148
-2
24 Oct 2026, 03:36
6,150
+1
21 Oct 2026, 09:29
6,149
+3
17 Oct 2026, 23:38
6,146
+16
15 Oct 2026, 00:09
6,130
+50
11 Oct 2026, 09:20
6,080
+33
5 Oct 2026, 06:59
6,047
+4
27 Sept 2026, 06:37
6,043
+96
17 Sept 2026, 20:37
5,947
+58
13 Sept 2026, 10:15
5,889
+12
9 Sept 2026, 20:59
5,877
+131
4 Sept 2026, 10:57
5,746
+31
31 Aug 2026, 14:17
5,715
+64
28 Aug 2026, 07:55
5,651
+52
25 Aug 2026, 13:56
5,599
first reading
Engagement
111 posts held, back to 4 August 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 14 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
18.5%
avg views ÷ 6,228 subscribers
Avg views / post
1,150
35 posts measured
Reaction rate
2.82%
reactions ÷ views · ER floor
Posts in window
35
of 111 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
Window
Rolling 30 days · latest post in window 6 November 2026
Posts held
111 (4 August 2026 – 6 November 2026)
Views total
40,411
Reactions total
1,139
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
6 Nov 2026, 16:49 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
6s
Average length
6s
Measured directly from 1 video 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,501 reactions across 95 posts, in 35 distinct kinds. The most used accounts for 19.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
694
19.8%
😁
576
16.5%
💯
492
14.1%
custom 5431823741724149238
192
5.48%
❤🔥
187
5.34%
custom 5431566988579197247
185
5.28%
custom 5330136800398688773
165
4.71%
🔥
140
4.00%
🦄
122
3.48%
🥰
113
3.23%
custom 5224306233539831385
109
3.11%
👍
83
2.37%
custom 5213227721882082247
77
2.20%
custom 5339228365696017200
75
2.14%
🤔
54
1.54%
👏
38
1.09%
🫡
30
0.857%
🎉
24
0.686%
👀
22
0.628%
👌
20
0.571%
15 further kinds
103
2.94%
Custom emoji. 6 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 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 111 of the 111 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,967 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 111 most recent posts we hold, published 4 August 2026 to 6 November 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
46
across the posts below
Posts paid on
7
of 111 we hold a reading for · 6%
Most on one post
40
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @vremeninet8. 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 111 most recent posts we hold for this entry, published 4 August 2026 to 6 November 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
Telegram’s own ‘edited’ marker: 0 of 35 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🫖 Любители чая! У вас ведь есть чайная посуда, которой пользуетесь очень редко, мб вообще перестали? Какая-то надоела, с другой внимание переключилось на новую, и она стоит и пылится.
Как вам идея дарить неиспользуемую посуду тем, кому она нужна? От старой избавляешься, новую приобретаешь 👍 Мы в чате @tea_family уже начали друг другу дарить и посуду, и чай!
Смотри, какой классный походный набор Малфи подарила Денис…
📣 Разместите рекламу в этом канале — её увидят
Аудитория Telegram остаётся активной, что бы ни говорили. Индекс читаемости это подтверждает: охваты каналов по тематикам держатся, люди продолжают читать.
Реклама в Telegram — это законно: ФАС в 2026 году официально подтвердил, что она разрешена.
👉 Заказать размещение в этом канале можно через Telega.in — с маркировкой и закрывающими документами, за пару минут.
Форм…
Готовы услышать ПРАВДУ про себя? За 15 минут
Про то, почему так тяжело достаются деньги, сыпется здоровье и удаётся помочь всем, кроме самой себя?!
Не ту правду, которой прикрывается ваш мозг, мол это кризис и у всех сложности. А ту, что живёт в теле и ДНК 🧬 Которую вы годами затыкали чаем с вкусняшками, сессиями у других специалистов и новыми обучениями
Для этого не нужны маятники, карты или ваша дата рождения
…
Showing the 12 most recent of 111 posts we hold for @vremeninet8. 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.
Posts recorded as deleted after publishing
We recorded 2 posts on @vremeninet8 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
First seen missing
4 November 2026
Most recent seen missing
4 November 2026
Median time before seen missing
18 hours
Seen missing in the last 30 days
2
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.
Mentions
Named by 6 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
Виктор Пелевин @viktorpelevin · 32,608 Telegram ranks this channel #9 of 83 here — alongside 82 others — read 5 September 2026
Сергей Кулдин @kuldinchannel · 18,819 Telegram ranks this channel #69 of 82 here — alongside 81 others — read 5 October 2026
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 11 November 2026 — this
entry's latest reading, not the date you are reading this.
“времени нет ∞” (@vremeninet8), 6,228 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/vremeninet8.
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.
