Telegram RegisterThe public register of Telegram

Channel

Таня Ф.

@tanya_f

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cross-platform identity · Cite this entry

21,286subscribers

-33 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001117456942
TypeChannel
Username@tanya_f
DescriptionДля связи: @tfrepbot
Created21 March 2017measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held11
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/tanya_f

Growth

21,28621,31921,302.55 August 2026 — 21,319 subscribers6 August 2026 — 21,319 subscribers6 August 2026 — 21,317 subscribers7 August 2026 — 21,316 subscribers8 August 2026 — 21,312 subscribers9 August 2026 — 21,313 subscribers10 August 2026 — 21,311 subscribers11 August 2026 — 21,303 subscribers12 August 2026 — 21,299 subscribers13 August 2026 — 21,293 subscribers14 August 2026 — 21,286 subscribers5 August 202614 August 2026
11 measurements spanning 9 days, net -33. 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 21,281–21,324 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 22:0421,286-7
13 Aug 2026, 10:2621,293-6
12 Aug 2026, 08:3621,299-4
11 Aug 2026, 08:5621,303-8
10 Aug 2026, 07:0221,311-2
9 Aug 2026, 06:4321,313+1
8 Aug 2026, 07:1421,312-4
7 Aug 2026, 09:1321,316-1
6 Aug 2026, 11:2521,317-2
6 Aug 2026, 02:0521,319no change
5 Aug 2026, 22:1121,319first reading

Engagement

29 posts held, back to 22 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 21 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
21.6%
avg views ÷ 21,286 subscribers
Avg views / post
4,600
29 posts measured
Reaction rate
1.69%
reactions ÷ views · ER floor
Posts in window
29
of 29 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 14 August 2026
Posts held29 (22 July 202614 August 2026)
Views total133,370
Reactions total2,257
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 05:57 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,110
Videos
250
Links
5,040

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

Reaction mix

2,257 reactions across 29 posts, in 6 distinct kinds. The most used accounts for 60.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1,36460.4%
👍48721.6%
🔥29012.8%
😢743.28%
👎401.77%
🤯20.089%

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

Measured over the 29 most recent posts we hold, published 22 July 2026 to 14 August 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
1
across the posts below
Posts paid on
1
of 29 we hold a reading for · 3%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @tanya_f. 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 29 most recent posts we hold for this entry, published 22 July 2026 to 14 August 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

14 Aug 2026, 06:00 UTC≈1,690 views77 reactionsread 15 August 2026

https://www.youtube.com/live/v5dJCJUkrfk?si=lWC9stA36Yfv54Fq

53🔥21👎3

14 Aug 2026, 06:00 UTC≈1,710 views48 reactionsread 15 August 2026

Заканчиваю вахту утр - приходите похулиганить!

🔥417

11 Aug 2026, 14:00 UTC≈3,100 views139 reactionsread 15 August 2026
Forwarded from @romashovaol

Завтра снег пройдет, хорошая новость на «Медиазоне» В суде отбили сироту Антона Филимонова, которого обманом заставили подписать контракт в колледже, когда ему было 17 Теперь никто никуда не поедет Все же огласка и грамотная работа юристов еще могут кого-то спасти. И, конечно, готовность самого человека бороться Я первая из журов написала про историю Антона, так что для меня это все близко к сердцу Удивляюсь, чт

120👍18👎1

11 Aug 2026, 13:07 UTC≈2,900 views47 reactionsread 15 August 2026
Forwarded from @mediazzzonaPhoto

В Сербии пройдет кинофестиваль «Медиазоны» и независимой студии raz/rez В сентябре нашей редакции исполнится 12 лет, и мы решили провести в Сербии три показа наших фильмов о войне, репрессиях, контроле над телом и борьбе за историческую память. Все — на русском языке с английскими субтитрами. После показов будут дискуссии с создателями фильмов, журналистами и с другими спикерами. Наши инфорпартнеры «Новости Сербия».

29👍17👎1

11 Aug 2026, 05:55 UTC≈3,270 views114 reactionsread 15 August 2026

Давненько не брал я в руки шашек https://www.youtube.com/live/kozpklDko94?si=WnC25xr3tf5AuizG

86👍21🔥6👎1

10 Aug 2026, 16:50 UTC≈3,630 views84 reactionsread 15 August 2026

Слушали решение ВС в прямом эфир и с колес комментируем https://www.youtube.com/live/qoXWfh6ZGqs?si=AFQIEcQ5MiJ-nPfB

😢6415👍4👎1

10 Aug 2026, 15:50 UTC≈3,690 views75 reactionsread 15 August 2026

Включайте через 5 минут! https://www.youtube.com/live/qoXWfh6ZGqs?si=3LFeKVwL1cKigSoT

👍4925👎1

10 Aug 2026, 12:20 UTC≈3,670 views95 reactionsread 15 August 2026
Forwarded from @tfelgnotifyPhoto

Ваня, не матерись! “Яблоко” судят, сербские братушки предают, “Колобок” катится в кринж | 10.8.26 10 августа 2026, 18:55 МСК, 17:55 CEST Подкаст “Ваня, не матерись!” в прямом эфире! Обсуждаем неожиданный поворот в судьбе партии “Яблоко”, вой зетников из-за предательства сербских братушек, приключения фильма “Колобок” и многое другое. Включайте в 18:55 мск! 📺 https://youtube.com/live/qoXWfh6ZGqs 📺 https://twitch.t

62🔥21👍11👎1

8 Aug 2026, 10:26 UTC≈3,910 views100 reactionsread 15 August 2026
Forwarded from @sparkhomenkovoice

Сегодня в 14 часов по Москве будем разговаривать с Татьяной Фельгенгауэр про яблоки. Премьера - на ее собственном канале. Вот тут: https://www.youtube.com/live/h1MgNLaP0Fo?is=jhT1zdmx6gWc66ss Не пропустите. Мы немножко заранее затеяли этот разговор. Сезон еще впереди. Но яблоки уже начинаются кое-где. Будем варить прямо в эфире моментальное яблочное варенье. И еще испечем несколько яблок с ореховой начинкой. Ну и

76🔥15👍7👎2

5 Aug 2026, 16:02 UTC≈4,950 views85 reactionsread 15 August 2026

Не очень логично получилось: чтобы не грустили - вот вам грустная глава. Но что поделать.

67👍14🔥2😢2

5 Aug 2026, 16:01 UTC≈4,970 views64 reactions1 Starread 15 August 2026

Но чтобы вы не грустили, в стандартные 21 мск (20 CEST) предлагаю вам послушать очередную главу книги. Это грустная и личная глава. В этом ролике я прерываюсь на довольно долгое воспоминания. К сожалению, тяжелые. Таня Ф. читает и комментирует книгу «Наш бизнес — смерть» о ЧВК «Вагнер» и Пригожине | Часть 7 https://youtu.be/LJxcA5NHDYM

59👍5

5 Aug 2026, 12:17 UTC≈4,320 views81 reactionsread 15 August 2026

Дорогие, сегодня стрима не будет - маленький отпуск.

67👍11😢3

Showing the 12 most recent of 29 posts we hold for @tanya_f. 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.

Citation-graph rank

Citation-graph rank — 213,190 of 1,350,102entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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 10 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.

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.

И Грянул Грэм
@gremtelegram · 113,310
Telegram ranks this channel #48 of 96 here — alongside 95 others — read 14 August 2026
Накипело. Майкл Наки
@Nackepelo · 212,710
Telegram ranks this channel #79 of 96 here — alongside 95 others — read 11 August 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.

Cross-platform identity — Wikidata

A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.

Q4482488 on Wikidata, read 9 August 2026
LabelTatiana Felgenhauer
DescriptionRussian journalist
X / Twitter@t_felg
YouTubeUC0OiowQ-fTqw3Kq3bfopO_Q

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

“Таня Ф.” (@tanya_f), 21,286 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/tanya_f.

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.