Telegram RegisterThe public register of Telegram
Telegram profile photo for ФЕДЕРАША

Channel

ФЕДЕРАША

@federasha_tg

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

32,892subscribers

-1,412 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-1002497185238
TypeChannel
Username@federasha_tg
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live30 August 2026
Measurements held24
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/federasha_tg

Growth

32,89234,30433,5987 August 2026 — 34,304 subscribers7 August 2026 — 34,304 subscribers8 August 2026 — 34,280 subscribers9 August 2026 — 34,206 subscribers10 August 2026 — 34,132 subscribers11 August 2026 — 34,081 subscribers11 August 2026 — 34,031 subscribers12 August 2026 — 33,974 subscribers14 August 2026 — 33,895 subscribers15 August 2026 — 33,830 subscribers16 August 2026 — 33,744 subscribers17 August 2026 — 33,690 subscribers18 August 2026 — 33,626 subscribers19 August 2026 — 33,554 subscribers20 August 2026 — 33,484 subscribers22 August 2026 — 33,415 subscribers23 August 2026 — 33,282 subscribers25 August 2026 — 33,220 subscribers26 August 2026 — 33,159 subscribers27 August 2026 — 33,108 subscribers28 August 2026 — 33,053 subscribers29 August 2026 — 33,002 subscribers30 August 2026 — 32,947 subscribers30 August 2026 — 32,892 subscribers7 August 202630 August 2026
24 measurements spanning 23 days, net -1,412. 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 32,680–34,516 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 24
Measured (UTC)SubscribersChange
30 Aug 2026, 23:0832,892-55
30 Aug 2026, 00:5432,947-55
29 Aug 2026, 00:5533,002-51
28 Aug 2026, 02:3733,053-55
27 Aug 2026, 04:0733,108-51
26 Aug 2026, 03:1533,159-61
25 Aug 2026, 04:2333,220-62
23 Aug 2026, 23:3433,282-133
22 Aug 2026, 07:3633,415-69
20 Aug 2026, 22:4333,484-70
19 Aug 2026, 23:0733,554-72
18 Aug 2026, 20:3433,626-64
17 Aug 2026, 21:0433,690-54
16 Aug 2026, 20:0533,744-86
15 Aug 2026, 10:3533,830-65
14 Aug 2026, 00:3733,895-79
12 Aug 2026, 22:1433,974-57
11 Aug 2026, 22:4234,031-50
11 Aug 2026, 00:5834,081-51
10 Aug 2026, 04:1634,132first reading

Engagement

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

ERR · 30 days
4.96%
avg views ÷ 32,892 subscribers
Avg views / post
1,630
139 posts measured
Reaction rate
2.62%
reactions ÷ views · ER floor
Posts in window
139
of 139 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 30 August 2026
Posts held139 (3 August 202630 August 2026)
Views total226,840
Reactions total5,936
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken30 Aug 2026, 18:25 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
1h 10m
Average length
30s

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

5,936 reactions across 139 posts, in 52 distinct kinds. The most used accounts for 31.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁1,88531.8%
🤣1,12318.9%
🤮61310.3%
2814.73%
💊2143.61%
🤡2123.57%
💩1943.27%
👍1742.93%
🥴1632.75%
🙈1622.73%
🔥1302.19%
🙉1031.74%
👏961.62%
😭751.26%
😢681.15%
🤔400.674%
😱330.556%
🥰320.539%
😐310.522%
💅300.505%
32 further kinds2774.67%

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

Measured over the 139 most recent posts we hold, published 3 August 2026 to 30 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.

Recent posts

30 Aug 2026, 18:20 UTC81 views2 reactionsread 30 August 2026
Video

Пришел нормальным, ушел Малышевой ФЕДЕРАША — Подписаться

😢1😨1

30 Aug 2026, 16:15 UTC454 views16 reactionsread 30 August 2026
Video

Амбассадор магния ФЕДЕРАША — Подписаться

🤣13🤪2😁1

30 Aug 2026, 14:15 UTC622 views22 reactionsread 30 August 2026
Video

Нишевость их боялась ФЕДЕРАША — Подписаться

😁13🌚6🤣3

30 Aug 2026, 12:15 UTC753 views31 reactionsread 30 August 2026
Video

В конце чуть от себя добавил ФЕДЕРАША — Подписаться

😐12😁8😢8🤣2😭1

30 Aug 2026, 05:45 UTC≈1,080 views31 reactionsread 30 August 2026
Video

Чуть не крякнул подводник ФЕДЕРАША — Подписаться

😁25🤮41👍1

29 Aug 2026, 19:02 UTC≈1,150 views37 reactionsread 30 August 2026
Video

С первого раза не понял ФЕДЕРАША — Подписаться

🤣36🔥1

29 Aug 2026, 17:33 UTC≈1,250 views35 reactionsread 30 August 2026
Video

Быть ей или быть с ней? ФЕДЕРАША — Подписаться

😁245🤡4👏1🤣1

29 Aug 2026, 16:18 UTC≈1,230 views35 reactionsread 30 August 2026
Video

Обзор на мыло, который мы заслужили ФЕДЕРАША — Подписаться

😁22🤮4🙈4🤡3💊1🤣1

29 Aug 2026, 15:32 UTC≈1,190 views29 reactionsread 30 August 2026
Video

Что за программа в телевизоре? ФЕДЕРАША — Подписаться

😁21🗿3🍌2🏆1🤣1🙏1

29 Aug 2026, 13:26 UTC≈1,210 views31 reactionsread 30 August 2026
Video

Даже жабры есть ФЕДЕРАША — Подписаться

😁243🍓3🤮1

29 Aug 2026, 07:55 UTC≈1,270 views33 reactionsread 30 August 2026
Video

Бедный Наговицын на майке закурил даже ФЕДЕРАША — Подписаться

😁23🤮10

28 Aug 2026, 19:10 UTC≈1,310 views33 reactionsread 30 August 2026
Video

Целевая трека ФЕДЕРАША — Подписаться

🤮23🤣7🙈2🙏1

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

“ФЕДЕРАША” (@federasha_tg), 32,892 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/federasha_tg.

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.