Telegram RegisterThe public register of Telegram
Telegram profile photo for Serialy

Channel

Serialy

@besprintsipnye_serialy

On this record: Topic · Growth · Engagement · What this channel posts · Advertising · Posts · Cite this entry

44,689subscribers

-962 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001375752283
TypeChannel
Username@besprintsipnye_serialy
Description…. Secuгe Netwoгk Любой пост может быть рекламным. Администрация не отвечает за содержание рекламы. Все действия с рекламой — на вашей ответственности.
Created13 February 2020measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live17 September 2026
Measurements held31
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/besprintsipnye_serialy

Topic

Film & TV — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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

44,68945,65745,1737 August 2026 — 45,651 subscribers8 August 2026 — 45,644 subscribers8 August 2026 — 45,646 subscribers10 August 2026 — 45,652 subscribers11 August 2026 — 45,657 subscribers12 August 2026 — 45,558 subscribers13 August 2026 — 45,531 subscribers14 August 2026 — 45,472 subscribers15 August 2026 — 45,458 subscribers18 August 2026 — 45,443 subscribers19 August 2026 — 45,448 subscribers20 August 2026 — 45,441 subscribers21 August 2026 — 45,429 subscribers23 August 2026 — 45,384 subscribers24 August 2026 — 45,381 subscribers25 August 2026 — 45,374 subscribers26 August 2026 — 45,358 subscribers27 August 2026 — 45,331 subscribers28 August 2026 — 45,295 subscribers29 August 2026 — 45,287 subscribers30 August 2026 — 45,176 subscribers31 August 2026 — 45,159 subscribers1 September 2026 — 45,116 subscribers2 September 2026 — 45,084 subscribers4 September 2026 — 45,046 subscribers6 September 2026 — 44,980 subscribers10 September 2026 — 44,866 subscribers12 September 2026 — 44,818 subscribers14 September 2026 — 44,778 subscribers15 September 2026 — 44,734 subscribers17 September 2026 — 44,689 subscribers7 August 202617 September 2026
31 measurements spanning 41 days, net -962. 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 44,544–45,802 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 31
Measured (UTC)SubscribersChange
17 Sept 2026, 21:3744,689-45
15 Sept 2026, 17:4244,734-44
14 Sept 2026, 03:0044,778-40
12 Sept 2026, 08:2144,818-48
10 Sept 2026, 04:5944,866-114
6 Sept 2026, 22:0044,980-66
4 Sept 2026, 10:5845,046-38
2 Sept 2026, 19:3545,084-32
1 Sept 2026, 17:2445,116-43
31 Aug 2026, 14:4645,159-17
30 Aug 2026, 17:2945,176-111
29 Aug 2026, 14:0245,287-8
28 Aug 2026, 15:5745,295-36
27 Aug 2026, 18:1445,331-27
26 Aug 2026, 20:4345,358-16
25 Aug 2026, 19:5145,374-7
24 Aug 2026, 17:1345,381-3
23 Aug 2026, 03:3745,384-45
21 Aug 2026, 13:1845,429-12
20 Aug 2026, 12:5345,441first reading

Engagement

6 posts held, back to 13 February 2020the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 91 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
no view readings in window
Avg views / post
no view readings
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 6 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 7 September 2026
Posts held6 (13 February 20207 September 2026)
Views total
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken22 Sept 2026, 09: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

Photos
4

Lifetime counters from Telegram’s own channel header, read 22 September 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.

Advertising

Ad load
16.7%
1 of 6 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
9,080
over 1 measured post
Median views · rest
63,000
over 3 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
eridPostsFirst seenLast seen
2SDnjbuHsTY14 June 20264 June 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 6 most recent posts we hold, published 13 February 2020 to 7 September 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.

Recent posts

4 Jun 2026, 10:27 UTC≈9,080 viewsread 22 September 2026
Advertisementerid 2SDnjbuHsTYPhoto

Photo, posted without a caption

Showing the 6 most recent of 6 posts we hold for @besprintsipnye_serialy. 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.

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

“Serialy” (@besprintsipnye_serialy), 44,689 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/besprintsipnye_serialy.

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.