Telegram RegisterThe public register of Telegram
Telegram profile photo for Потешный Волчара | Woof🐺

Channel

Потешный Волчара | Woof🐺

@elfswolchalive

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

87subscribers

-1 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001649919386
TypeChannel
Username@elfswolchalive
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live24 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 24 August 2026
On Telegramt.me/elfswolchalive

Growth

878887.58 August 2026 — 88 subscribers9 August 2026 — 88 subscribers24 August 2026 — 87 subscribers8 August 202624 August 2026
3 measurements spanning 17 days, net -1. 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 87–88 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 15:0887-1
9 Aug 2026, 15:3288no change
8 Aug 2026, 01:3188first reading

Engagement

13 posts held, back to 24 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 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
38.9%
avg views ÷ 87 subscribers
Avg views / post
33.9
8 posts measured
Reaction rate
31.0%
reactions ÷ views · ER floor
Posts in window
8
of 13 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 August 2026
Posts held13 (24 July 20268 August 2026)
Views total271
Reactions total84
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 15:32 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
5m 12s
Average length
52s

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

143 reactions across 13 posts, in 8 distinct kinds. The most used accounts for 33.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52223183122218515294833.6%
🔥4028.0%
custom 53189632110499011951611.2%
custom 52197880396135946091510.5%
custom 5828087131079186297128.39%
custom 531877310720744740353.50%
🌚42.80%
custom 523574768711396135932.10%

Custom emoji. 6 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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

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

8 Aug 2026, 19:14 UTC18 views9 reactionsread 9 August 2026
Video message

Video message, posted without a caption

custom 52197880396135946095🔥2custom 52223183122218515292

Signed Wolcha

8 Aug 2026, 18:31 UTC19 views10 reactionsread 9 August 2026
Video

Я не сдержалась и пошла в пляс. Муж не разрешил наступать на ногу((((((((

custom 53189632110499011955🔥3custom 52197880396135946092

Signed Wolcha

8 Aug 2026, 17:25 UTC21 views8 reactionsread 9 August 2026

Сегодня свадьба моей мамки, но я не могу отжигать пьяная под всякие треки.

custom 58280871310791862974🔥2custom 53189632110499011952

Signed Wolcha

8 Aug 2026, 17:24 UTC21 views8 reactionsread 9 August 2026
Video message

Video message, posted without a caption

custom 52223183122218515294🔥2custom 52197880396135946092

Signed Wolcha

2 Aug 2026, 06:45 UTC51 views22 reactionsread 9 August 2026
Photo

Сегодня уже год, как мы семья. 😇😭💖

custom 522231831222185152912🔥8custom 58280871310791862972

Signed Wolcha

1 Aug 2026, 20:00 UTC49 views8 reactionsread 9 August 2026
Video

Я уже давно дома. Я повторяю историю прошлого года, когда после отпуска я вышла на одну смену и слегла на больничный. Пс. Не обращайте внимания на то какая я тут убитая

🌚4🔥2custom 53189632110499011952

Signed Wolcha

1 Aug 2026, 16:49 UTC44 views8 reactionsread 9 August 2026
Video message

Video message, posted without a caption

custom 52357476871139613593custom 53187731072074474032🔥1custom 52223183122218515291custom 58280871310791862971

Signed Wolcha

30 Jul 2026, 20:07 UTC48 views11 reactionsread 9 August 2026
Video

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

🔥6custom 52223183122218515293custom 52197880396135946092

Signed Wolcha

29 Jul 2026, 07:50 UTC50 views16 reactionsread 9 August 2026
Photo

Принимаем поздравления на вкусняшки сюда https://tbank.ru/cf/AW7WTu35u3j 😆😱 Малышка хэппибезднулась третий раз.

custom 52223183122218515298custom 58280871310791862975custom 53187731072074474033

Signed Wolcha

26 Jul 2026, 11:34 UTC58 views11 reactionsread 9 August 2026

Моя волчья стая, подпишитесь кто не подписан плиз. Я маленькими шажочками иду к своей первой тысячи… И если шо можно попросить попросить друзей ваших? У меня каждый день интересный контент🥺 https://www.instagram.com/elfs_wolcha?igsh=MXd1c3BlMHllaHpw&utm_source=qr

custom 53189632110499011956custom 52223183122218515293🔥2

Signed Wolcha

25 Jul 2026, 19:46 UTC61 views10 reactionsread 9 August 2026
Video

Вита сегодня на фруктовом приколе. До этого она сегодня ещё дыню похавала с нами.

custom 52223183122218515296🔥3custom 53189632110499011951

Signed Wolcha

24 Jul 2026, 19:44 UTC52 views12 reactionsread 9 August 2026
Photo

Запоздалая распаковка покупок. Забыла ещё показать там что купили прикольную камеру гоупро и еще куклу барби для моей любимой @Ant0ta

custom 52223183122218515296🔥4custom 52197880396135946092

Signed Wolcha

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

Citation-graph rank

Citation-graph rank — 486,624 of 1,622,561entries 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

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.

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

“Потешный Волчара | Woof🐺” (@elfswolchalive), 87 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/elfswolchalive.

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.