Telegram RegisterThe public register of Telegram
Telegram profile photo for Анфисёнок

Channel

Анфисёнок

@wfisaw

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

29,230subscribers

+17,472 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002077235039
TypeChannel
Username@wfisaw
Descriptionсотрудничество t.me/fisanfisa
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live8 October 2026
Measurements held36
Confirmed unchanged1 time, most recently 8 October 2026
On Telegramt.me/wfisaw

Topic

Personal blog — 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 11 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 why it has no browse page of its own yet.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Views per post sit far above this size band

35,600 average views per post against 29,230 subscribers — an engagement rate of 121.9%. Across the 6,285 registered channels in the same cohort — 10,056–31,621 subscribers, posting mainly in Russian — the middle half sit between 5.62% and 24.1%, with a median of 12.0%.

What this was computed from
Window30 days (9 September 2026 – 9 October 2026)
Posts measured25 of 25 published in the window (0 exact, 25 rounded by Telegram)
Views totalled890,500
Mature posts only125.2% over 24 posts read at least 24h after publication
Subscribers29,230 measured 8 October 2026
Cohortb10000:rus · 6,285 channels · p10 2.75% · p25 5.62% · p50 12.0% · p75 24.1% · p90 47.9%
Position in cohort99.841th percentile · 10.2× the cohort median
Uncertainty±0.1% of the figure, from Telegram’s rounding
Post languageRussian · 100.0% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the key err_high, last confirmed 9 October 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

11,60029,23020,4157 August 2026 — 11,758 subscribers7 August 2026 — 11,758 subscribers8 August 2026 — 11,753 subscribers9 August 2026 — 11,749 subscribers10 August 2026 — 11,729 subscribers11 August 2026 — 11,706 subscribers12 August 2026 — 11,690 subscribers12 August 2026 — 11,678 subscribers14 August 2026 — 11,668 subscribers16 August 2026 — 11,656 subscribers17 August 2026 — 11,647 subscribers18 August 2026 — 11,642 subscribers19 August 2026 — 11,641 subscribers20 August 2026 — 11,726 subscribers21 August 2026 — 11,716 subscribers22 August 2026 — 11,717 subscribers24 August 2026 — 11,725 subscribers25 August 2026 — 11,720 subscribers26 August 2026 — 11,716 subscribers27 August 2026 — 11,705 subscribers28 August 2026 — 11,695 subscribers30 August 2026 — 11,684 subscribers31 August 2026 — 11,669 subscribers1 September 2026 — 11,655 subscribers2 September 2026 — 11,640 subscribers3 September 2026 — 11,629 subscribers5 September 2026 — 11,612 subscribers8 September 2026 — 11,600 subscribers11 September 2026 — 11,936 subscribers13 September 2026 — 11,930 subscribers14 September 2026 — 11,926 subscribers16 September 2026 — 13,179 subscribers18 September 2026 — 16,794 subscribers25 September 2026 — 19,811 subscribers3 October 2026 — 27,616 subscribers8 October 2026 — 29,230 subscribers7 August 20268 October 2026
36 measurements spanning 61 days, net +17,472. 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 8,956–31,875 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 36
Measured (UTC)SubscribersChange
8 Oct 2026, 03:5929,230+1,614
3 Oct 2026, 17:0127,616+7,805
25 Sept 2026, 00:5719,811+3,017
18 Sept 2026, 16:2116,794+3,615
16 Sept 2026, 09:0113,179+1,253
14 Sept 2026, 17:4111,926-4
13 Sept 2026, 01:0011,930-6
11 Sept 2026, 04:5811,936+336
8 Sept 2026, 07:3611,600-12
5 Sept 2026, 01:1811,612-17
3 Sept 2026, 10:5811,629-11
2 Sept 2026, 04:2411,640-15
1 Sept 2026, 03:1611,655-14
31 Aug 2026, 06:0611,669-15
30 Aug 2026, 02:3711,684-11
28 Aug 2026, 06:5411,695-10
27 Aug 2026, 04:0711,705-11
26 Aug 2026, 05:3511,716-4
25 Aug 2026, 06:2611,720-5
24 Aug 2026, 03:2411,725first reading

Engagement

80 posts held, back to 16 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 56 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
121.9%
avg views ÷ 29,230 subscribers
Avg views / post
35,600
25 posts measured
Reaction rate
0.929%
reactions ÷ views · ER floor
Posts in window
25
of 80 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 8 October 2026
Posts held80 (16 July 2026 – 8 October 2026)
Views total890,500
Reactions total8,273
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Oct 2026, 05:58 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
≈1,340
Videos
≈200
Links
≈84

Lifetime counters from Telegram’s own channel header, read 9 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
5m 22s
Average length
32s

Measured directly from 10 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

12,538 reactions across 80 posts, in 54 distinct kinds. The most used accounts for 17.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥2,22017.7%
🤯2,14617.1%
❤‍🔥1,79914.3%
👍1,51512.1%
🥰9607.66%
😢5434.33%
💋5244.18%
🤪4293.42%
💘2552.03%
💯2481.98%
💊2461.96%
🤬1871.49%
🗿1811.44%
😡1621.29%
😱1581.26%
👏1080.861%
🌚750.598%
🙈750.598%
😨730.582%
💔670.534%
34 further kinds5674.52%

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

Measured over the 80 most recent posts we hold, published 16 July 2026 to 8 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.

Recent posts

8 Oct 2026, 19:44 UTC≈12,200 views447 reactionsread 9 October 2026
Photo

Бог знает, где твоей душе будет спокойно. Он разрушает то, что ты так считала своим домом, чтобы показать тебе, как на самом деле ощущается дом, тепло, забота и безопасность. «Почему ты не плачешь?» Потому что я выплакала все слёзы. И иногда то, что мы называем потерей, оказывается самым большим подарком судьбы. Горящие глаза невозможно купить за булгури. И самое дорогое в жизни невозможно разделить пополам. И однажд…

👍200❤‍🔥116💯66🔥43🗿7🤪6👏5🤯3

7 Oct 2026, 19:42 UTC≈21,700 views326 reactionsread 9 October 2026

Я думаю, мне уже и с хавером вас знакомить не надо. Сергей познакомил его с вами раньше, чем успела это сделать я. И сейчас он подтверждает то, что он фотографирует и распространяет фото этого человека в интернете, в том числе его соц.сети и ложную информацию о нём. И делает это, видимо, на протяжении всех этих 2-3 недель, занимаясь преследованием, сталкерством и делая фото людей без их согласия на рабочем месте. Спа…

💘149❤‍🔥69🤯61🗿13🤔10🤪7👏6🔥5

7 Oct 2026, 18:22 UTC≈22,300 views319 reactionsread 9 October 2026
Voice message

КАК МЫ ЗАКРЫВАЛИ ОБЩИЙ СЧЁТ В БАНКЕ

🤯197🙈45🤬23👍16😨12🍌8😍7🏆4

7 Oct 2026, 17:07 UTC≈22,800 views475 reactionsread 9 October 2026
Video message

Video message, posted without a caption

🤯297🤪75🔥33😱12💔11🍌9💘9🙊9

4 Oct 2026, 07:50 UTC≈47,500 views621 reactionsread 9 October 2026

Кстати, там одна Ирина в комментариях очень переживает, какого это моим родителям смотреть, как мы с Ларисой выпили по 50-100 гр лимончелло, и мы такие бууухие алкоголички выходим в эфир Моя мама открыла и выпила не одну бутылку шампанского после нашего расставания с Сергеем)) Кроме того, мои родители не раз созванивались с Ларисой и благодарили её за её добро и помощь мне. И обсуждали мы ЧИСТО РУССКИМИ СЛОВАМИ эту …

👍275😢182🤯78💊20🔥20🥰15🤪10💘7

3 Oct 2026, 23:46 UTC≈41,300 views154 reactionsread 9 October 2026
Voice message

Voice message, posted without a caption

❤‍🔥74😢40🔥21💔6🌭3😱3👍2💘2

3 Oct 2026, 23:38 UTC≈40,800 views371 reactionsread 9 October 2026

Это как в тиктоке видос: друг, с которым тебе нельзя было общаться в отношениях 😂😂 Я столько ловлю инсайтов после расставания. Многие вещи, которые совершенно нормальны для всех, мной воспринимаются: «А НИХУЯ Ж СЕБЕ» Прошел месяц, а я порой до сих пор вздрагиваю: «а я отправила кружок, как я иду с работы?»,«а можно мне разговаривать по телефону?», «а можно меня подвезут до работы/или ещё куда-то?» а потом ловлю себ…

❤‍🔥193😢92👍36🙏28🤯10🍌4😱4✍1

3 Oct 2026, 23:22 UTC≈36,700 views174 reactionsread 9 October 2026
Video message

Video message, posted without a caption

❤‍🔥115💊26🕊14🥰9👍5💘4💅1

3 Oct 2026, 23:14 UTC≈37,000 views254 reactionsread 9 October 2026
Video message

Video message, posted without a caption

😢128💔47😭30💘15💊13❤‍🔥8😱6👏3

3 Oct 2026, 13:25 UTC≈38,500 views351 reactionsread 9 October 2026
Photo

Нападки продолжаются (Пишут Ларисе)

🤯237😢56🤬22🔥13👾6🤔6👀5💔2

3 Oct 2026, 09:09 UTC≈38,900 views327 reactionsread 9 October 2026
Photo

Сергей продолжает меня поливать грязью в своем блоге. А так же шантажирует, что если я не прекращу рассказывать людям о том, что он говорит обо мне, как преследует и что делает, то он продолжит делать карикатуры и шаржи с использованием фото других людей. Я снова и снова перестаю обсуждать его и пропадаю из блога, а возвращаюсь в него только тогда, когда он снова и снова нападает на меня. Я писала ему ещё в среду о …

👍149❤‍🔥58💯41🤯25😱17💊13🤪13💋4

2 Oct 2026, 17:19 UTC≈39,700 views223 reactionsread 9 October 2026
Video message

Video message, posted without a caption

❤‍🔥88🗿47🤯40💊15🤓10🤬7💘4🤷‍♀4

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

“Анфисёнок” (@wfisaw), 29,230 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/wfisaw.

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.