Telegram RegisterThe public register of Telegram
Telegram profile photo for Дом Зайца

Channel

Дом Зайца

@dom_zaytsa

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

4,332subscribers

-9 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001574546825
TypeChannel
Username@dom_zaytsa
Created5 March 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/dom_zaytsa

Growth

4,3324,3414,336.56 August 2026 — 4,341 subscribers6 August 2026 — 4,341 subscribers7 August 2026 — 4,339 subscribers10 August 2026 — 4,334 subscribers13 August 2026 — 4,332 subscribers6 August 202613 August 2026
5 measurements spanning 7 days, net -9. 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 4,331–4,342 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 16:474,332-2
10 Aug 2026, 14:244,334-5
7 Aug 2026, 05:534,339-2
6 Aug 2026, 10:364,341no change
6 Aug 2026, 10:054,341first reading

Engagement

26 posts held, back to 5 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 6 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
15.0%
avg views ÷ 4,332 subscribers
Avg views / post
648
26 posts measured
Reaction rate
23.4%
reactions ÷ views · ER floor
Posts in window
26
of 26 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 held26 (5 August 20268 August 2026)
Views total16,846
Reactions total3,939
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 18:20 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 53s
Average length
1m 58s

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

3,939 reactions across 26 posts, in 21 distinct kinds. The most used accounts for 52.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2,07352.6%
🥰57914.7%
🙏3649.24%
👍2155.46%
🔥1594.04%
😍1223.10%
❤‍🔥1122.84%
🎉1052.67%
😁952.41%
👀411.04%
220.559%
😭140.355%
🤗90.228%
💋70.178%
🤣60.152%
👾40.102%
😎40.102%
👏30.076%
🌚20.051%
🦄20.051%
1 further kind10.025%

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

Measured over the 26 most recent posts we hold, published 5 August 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, 16:12 UTC257 views91 reactionsread 8 August 2026
Photo

#лебедь@dom_zaytsa

❤‍🔥4620🥰13👍6😎4🦄2

8 Aug 2026, 16:09 UTC271 views92 reactionsread 8 August 2026
Photo

В заячью столовую принесли веточки #гвоздичка@dom_zaytsa #лебедь@dom_zaytsa #иллидан@dom_zaytsa

57🥰19❤‍🔥9👍5🎉2

8 Aug 2026, 12:11 UTC408 views142 reactionsread 8 August 2026
Photo

+ 1 русачок Зайчонок не старше трёх дней от роду, найден на парковке. Нашедшие сами привезли зайчонка в офис, проведя несколько часов в дороге. Путешествуйте по России вместе с зайцами! Заяц без нареканий, отлично кушает роялку, вес при приёме 120 гр. Нашедшие назвали Ара. #ара@dom_zaytsa

101🥰28😍7👍4❤‍🔥1😁1

Signed Victoria Arzamastseva

8 Aug 2026, 11:19 UTC444 views132 reactionsread 8 August 2026
Photo

Кому-то приходится быть подушкой. #карамельки@dom_zaytsa #олимпия@dom_zaytsa #пловчиха@dom_zaytsa

🔥65🥰2925😁8👾3👍2

Signed Victoria Arzamastseva

8 Aug 2026, 10:21 UTC452 views74 reactionsread 8 August 2026
Forwarded from @harehand

Таварищи! Уважаемые друзья! Талантливые наши люди! Нам в команду нужен волонтер-авитолог! Продавать сувениры на Авито в помощь зайцам Задачи 1) Написание текстов 2) Редактирование фото в фотошоп и джипити 3) Выставление на Авито, общение с покупателями 4) Сигнал нам, какой товар отнести на отправку// или самостоятельная отправка по желанию Очень нужен человек с опытом успешных продаж на Авито

44👍178🙏5

7 Aug 2026, 18:59 UTC645 views159 reactionsread 8 August 2026
Video

АСМР с веточками. #боровички@dom_zaytsa #овес@dom_zaytsa #вареничка@dom_zaytsa

89🔥28🥰24👍13🤗5

Signed Victoria Arzamastseva

7 Aug 2026, 18:44 UTC606 views167 reactionsread 8 August 2026
Photo

#боровички@dom_zaytsa

104😍28🥰26👍9

Signed Victoria Arzamastseva

7 Aug 2026, 16:38 UTC599 views171 reactionsread 8 August 2026
Photo

#гвоздичка@dom_zaytsa

113🥰47👍11

Signed Victoria Arzamastseva

7 Aug 2026, 15:04 UTC596 views194 reactionsread 8 August 2026
Photo

Смотрите кто отъелся. #лема@dom_zaytsa

123🥰49👍17🔥5

Signed Victoria Arzamastseva

7 Aug 2026, 13:58 UTC563 views149 reactionsread 8 August 2026
Video

Детский сад у Фроси и Каспера #фрося@dom_zaytsa #каспер@dom_zaytsa #опели@dom_zaytsa

103🥰37👍9

Signed Oleg Morozov

7 Aug 2026, 13:24 UTC594 views180 reactionsread 8 August 2026
Photo

Отчет за 11 банок роялки! Фото снятой наличности прикреплю вечером в комментариях к этому посту, так как мы сначала получаем у поставщика Роялку, а потом ему платим. Утром стулья, вечером деньги. Потом еще дозакажем, как будет поступление. Поставщик свято доверяет зайцам. ❤️ Надо будет ему пару зайцев на выкармливание подкинуть, чтобы он не скучал.

107👍30😁18😍12🤣6👏3🤗3🔥1

7 Aug 2026, 13:08 UTC573 views167 reactionsread 8 August 2026
Photo

#летти@dom_zaytsa

113🥰40👍14

Signed Victoria Arzamastseva

Showing the 12 most recent of 26 posts we hold for @dom_zaytsa. 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 — 169,279 of 1,481,217entries 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

Republishes

Channels on the register whose posts this channel has forwarded.

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 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“Дом Зайца” (@dom_zaytsa), 4,332 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/dom_zaytsa.

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.