Telegram RegisterThe public register of Telegram
Telegram profile photo for Сериалы

Channel

Сериалы

@serialfilmy

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

41,634subscribers

-1,403 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-1001174908638
TypeChannel
Username@serialfilmy
DescriptionSecuгe Netwoгk Любой пост может быть рекламным. Администрация не отвечает за содержание рекламы. Все действия с рекламой — на вашей ответственности.
Created1 March 2021 — measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live23 October 2026
Measurements held45
Confirmed unchanged1 time, most recently 23 October 2026
On Telegramt.me/serialfilmy

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 100% 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

41,63443,05442,3447 August 2026 — 43,037 subscribers7 August 2026 — 43,037 subscribers8 August 2026 — 43,024 subscribers9 August 2026 — 43,040 subscribers10 August 2026 — 43,054 subscribers11 August 2026 — 43,031 subscribers12 August 2026 — 42,835 subscribers13 August 2026 — 42,827 subscribers14 August 2026 — 42,760 subscribers16 August 2026 — 42,738 subscribers17 August 2026 — 42,740 subscribers18 August 2026 — 42,739 subscribers19 August 2026 — 42,755 subscribers20 August 2026 — 42,729 subscribers21 August 2026 — 42,718 subscribers23 August 2026 — 42,695 subscribers25 August 2026 — 42,699 subscribers26 August 2026 — 42,686 subscribers27 August 2026 — 42,664 subscribers28 August 2026 — 42,629 subscribers29 August 2026 — 42,595 subscribers30 August 2026 — 42,579 subscribers31 August 2026 — 42,482 subscribers1 September 2026 — 42,472 subscribers2 September 2026 — 42,434 subscribers3 September 2026 — 42,407 subscribers4 September 2026 — 42,357 subscribers8 September 2026 — 42,298 subscribers10 September 2026 — 42,246 subscribers12 September 2026 — 42,221 subscribers14 September 2026 — 42,181 subscribers16 September 2026 — 42,138 subscribers18 September 2026 — 42,107 subscribers1 October 2026 — 41,810 subscribers6 October 2026 — 41,760 subscribers11 October 2026 — 41,736 subscribers14 October 2026 — 41,714 subscribers15 October 2026 — 41,703 subscribers15 October 2026 — 41,675 subscribers17 October 2026 — 41,662 subscribers18 October 2026 — 41,640 subscribers19 October 2026 — 41,647 subscribers19 October 2026 — 41,646 subscribers21 October 2026 — 41,637 subscribers23 October 2026 — 41,634 subscribers7 August 202623 October 2026
45 measurements spanning 77 days, net -1,403. 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 41,421–43,267 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 45
Measured (UTC)SubscribersChange
23 Oct 2026, 10:5741,634-3
21 Oct 2026, 04:0141,637-9
19 Oct 2026, 22:4641,646-1
19 Oct 2026, 00:4941,647+7
18 Oct 2026, 02:0741,640-22
17 Oct 2026, 02:2841,662-13
15 Oct 2026, 23:4641,675-28
15 Oct 2026, 03:0641,703-11
14 Oct 2026, 00:1941,714-22
11 Oct 2026, 02:5641,736-24
6 Oct 2026, 18:4141,760-50
1 Oct 2026, 20:1741,810-297
18 Sept 2026, 10:5742,107-31
16 Sept 2026, 02:2142,138-43
14 Sept 2026, 10:3942,181-40
12 Sept 2026, 19:4042,221-25
10 Sept 2026, 22:3542,246-52
8 Sept 2026, 00:5742,298-59
4 Sept 2026, 23:4042,357-50
3 Sept 2026, 10:0342,407first reading

Engagement

5 posts held, back to 1 March 2021 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 149 pages 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 5 posts for this entry, the most recent from 19 May 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
4

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

Reaction mix

151 reactions across 4 posts, in 9 distinct kinds. The most used accounts for 60.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤9260.9%
👍3422.5%
🍌95.96%
💋53.31%
👎42.65%
🔥31.99%
💯21.32%
🎉10.662%
🥰10.662%

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 4 of the 5 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 151 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 5 most recent posts we hold, published 1 March 2021 to 19 May 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.

Recent posts

19 May 2026, 12:51 UTC≈2,990 views9 reactionsread 23 October 2026
Photo

❤️«Эйɸ᧐ρᥙя 3», серии 1-9

💋5❤3🎉1

29 Aug 2025, 14:46 UTC≈12,100 views13 reactionsread 23 October 2026
Photo

🎬 Новинка! «Жизнь по вызову. Фильм»

❤11👍1🥰1

19 Dec 2024, 12:43 UTC≈34,000 views46 reactionsread 23 October 2026
Photo

🔥«Плакса 3», серии 1-2

❤29👍14🔥3

26 Oct 2024, 12:06 UTC≈39,700 views83 reactionsread 23 October 2026
Photo

😍«Жить жизнь 4» (сериал, 2026): новые серии

❤49👍19🍌9👎4💯2

Showing the 5 most recent of 5 posts we hold for @serialfilmy. 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 23 October 2026 — this entry's latest reading, not the date you are reading this.

“Сериалы” (@serialfilmy), 41,634 subscribers as measured 23 October 2026. Telegram Register, tgregister.com/channel/serialfilmy.

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.