Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 71% 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 why it has no browse page of its own yet.
Growth
43 measurements spanning 75 days, net -719. 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 65,134–66,069 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 43
Measured (UTC)
Subscribers
Change
20 Oct 2026, 12:10
65,242
-13
19 Oct 2026, 13:16
65,255
-8
18 Oct 2026, 11:37
65,263
-18
17 Oct 2026, 08:28
65,281
-17
16 Oct 2026, 05:29
65,298
-16
15 Oct 2026, 04:27
65,314
-13
14 Oct 2026, 02:00
65,327
-34
11 Oct 2026, 09:15
65,361
-30
7 Oct 2026, 00:42
65,391
-40
2 Oct 2026, 02:01
65,431
-105
18 Sept 2026, 15:40
65,536
-1
16 Sept 2026, 10:38
65,537
+1
14 Sept 2026, 16:18
65,536
-1
13 Sept 2026, 04:38
65,537
-21
11 Sept 2026, 03:57
65,558
-15
8 Sept 2026, 08:40
65,573
-24
5 Sept 2026, 01:59
65,597
-20
3 Sept 2026, 07:06
65,617
-24
1 Sept 2026, 22:08
65,641
-27
31 Aug 2026, 18:47
65,668
first reading
Engagement
160 posts held, back to 31 July 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 151 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
29.1%
avg views ÷ 65,242 subscribers
Avg views / post
19,000
50 posts measured
Reaction rate
1.93%
reactions ÷ views · ER floor
Posts in window
50
of 160 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 19 October 2026
Posts held
160 (31 July 2026 – 19 October 2026)
Views total
950,120
Reactions total
18,373
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
20 Oct 2026, 06:22 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
38m 14s
Average length
50s
Measured directly from 46 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
66,585 reactions across 158 posts, in 19 distinct kinds. The most used accounts for 36.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
😁
23,974
36.0%
🔥
14,427
21.7%
👍
8,417
12.6%
❤
4,605
6.92%
custom 5458924238037590515
3,212
4.82%
custom 5456188142006575553
2,611
3.92%
💩
2,050
3.08%
😢
1,491
2.24%
💯
1,251
1.88%
🫡
1,053
1.58%
custom 5456509804992271929
984
1.48%
🤷♂
900
1.35%
😍
536
0.805%
🗿
378
0.568%
🤝
262
0.393%
🥴
228
0.342%
👎
82
0.123%
🥱
80
0.12%
😡
44
0.066%
Custom emoji. 3 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 158 of the 160 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 66,585 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 160 most recent posts we hold, published 31 July 2026 to 19 October 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
52
across the posts below
Posts paid on
31
of 158 we hold a reading for · 20%
Most on one post
11
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @by_pit_stop. 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 160 most recent posts we hold for this entry, published 31 July 2026 to 19 October 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.
Advertising
Ad load
0.625%
1 of 160 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
15,700
over 1 measured post
Median views · rest
20,100
over 157 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.
Advertising tokens recorded on this entry
erid
Posts
First seen
Last seen
2W5zFK5ysMs
1
31 August 2026
31 August 2026
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 160 most recent posts we hold, published 31 July 2026 to 19 October 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.
А прикиньте, если ёбнуть все серваки ВК например, то это может быть беспрецедентны случаем в истории, когда хуяк и как будто сервиса никогда не было. Вместо ВК подставьте что угодно из того, чем вы пользуетесь каждый день и представьте, что это исчезло без следа навсегда, без возможности восстановить. И не только у вас, а вообще у всех. Для большей наглядности мысленного эксперимента представте телегу, например. Ост…
Вот уже хуй знает сколько лет с момента, как БЕСПЛАТНОЕ облако стало платным, маилсру каждые 10 дней присылает мне, что через 10 дней облако-хуёблако заморозится/удалится/сгорит, поэтому срочно успейте дать нам денег, чтобы не потерять то, что я сам оттуда давно удалил, когда уходил. Ничего личного, просто наебалово
Пасоны, мы короче все продали, нихуя не осталось, реально одна худи "мыши" осталась маленького размера. Но меня заебли обращения людей, которым не хватило размеров. Поэтому мы подумали запустить предзаказ, наберётся партия - сделаем и отправим всем кто оплатил. заказы собираем неделю, может 2, потом недель 5-6 все будет делаться, то есть где-то в декабре все поучат худейки.
заказ тут @Nice_merch_bot
Showing the 12 most recent of 160 posts we hold for @by_pit_stop. 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.
Polls
The 4 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
Я ещё молодой, чтобы меня ебали проблемы старперов31%
The shares total 109%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
К теме последнего кружка: кто знает, что такое изжога?
Я знаю77%
Понятия не имею, что это25%
The shares total 102%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
The shares total 104%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
The shares total 169%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 160 most recent posts we hold, published 31 July 2026 to 19 October 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
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 20 October 2026 — this
entry's latest reading, not the date you are reading this.
“Заповедник Матвеева” (@by_pit_stop), 65,242 subscribers as measured 20 October 2026. Telegram Register, tgregister.com/channel/by_pit_stop.
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.
