Telegram RegisterThe public register of Telegram
Telegram profile photo for زاپاس کاباره خونه

Channel

زاپاس کاباره خونه

@kabare_home

On this record: Growth · Engagement · Reactions · Posts · Cite this entry

2,525subscribers

-65 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002076206818
TypeChannel
Username@kabare_home
Created18 April 2024measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live29 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/kabare_home

Growth

2,5252,5912,5587 August 2026 — 2,590 subscribers7 August 2026 — 2,590 subscribers8 August 2026 — 2,591 subscribers11 August 2026 — 2,582 subscribers14 August 2026 — 2,563 subscribers17 August 2026 — 2,551 subscribers20 August 2026 — 2,538 subscribers24 August 2026 — 2,534 subscribers27 August 2026 — 2,528 subscribers29 August 2026 — 2,525 subscribers7 August 202629 August 2026
10 measurements spanning 22 days, net -65. 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 2,515–2,601 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 17:332,525-3
27 Aug 2026, 03:242,528-6
24 Aug 2026, 02:092,534-4
20 Aug 2026, 19:442,538-13
17 Aug 2026, 21:042,551-12
14 Aug 2026, 23:042,563-19
11 Aug 2026, 06:112,582-9
8 Aug 2026, 11:552,591+1
7 Aug 2026, 14:332,590no change
7 Aug 2026, 14:212,590first reading

Engagement

10 posts held, back to 18 April 2024the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 10 posts for this entry, the most recent from 8 February 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

802 reactions across 8 posts, in 14 distinct kinds. The most used accounts for 28.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍22728.3%
20425.4%
👎13917.3%
🔥506.23%
🤔425.24%
😁404.99%
🍌374.61%
😱242.99%
🤩131.62%
101.25%
🥰80.998%
👏40.499%
👌30.374%
😭10.125%

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

Measured over the 10 most recent posts we hold, published 18 April 2024 to 8 February 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 Feb 2026, 13:01 UTC≈3,380 views18 reactionsread 7 August 2026

رفقا چنل جدید زدیم تشریف بیارید👄💯 https://t.me/+IvWagzYej5VkMzM0

👎7👍5👏42

6 Jul 2025, 20:16 UTC≈20,500 views49 reactionsread 7 August 2026

https://t.me/+IvWagzYej5VkMzM0 لینک چنلمون رو بدید رفقاتون بیان 🤤❤️

33👎15😭1

13 May 2025, 05:55 UTC≈42,900 views89 reactionsread 7 August 2026

سریع جوین بشید که بترکونیم😘

🤔4224👎23

13 May 2025, 05:55 UTC≈42,900 views192 reactionsread 7 August 2026

رفقا چنلمون فیلتر شد وارد چنل جدیدمون بشید که صفا سیتی بریم روی پستای جدید https://t.me/+zyEXux7tRSI0MGI0

👎5850🍌37👍3410👌3

21 Feb 2025, 09:11 UTC≈74,400 views88 reactionsread 7 August 2026

رفقا کلی پست p2 داریم میزنیم بریزید توی‌چنلمون ❤️

👍4417👎13🔥11🥰2😁1

29 Jan 2025, 19:11 UTC≈81,100 views203 reactionsread 7 August 2026

رفقا چنل اصلی مون راه اندازی شد اینجا جوین باشید فیلتر شدیم بهتون بگیم 🥰🍑

👍8244🔥24😱24👎23🥰6

17 Jan 2025, 10:59 UTC≈76,200 views110 reactionsread 7 August 2026

اینجا چنل زاپاسمونه رفق

👍4732🔥15🤩13😁3

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

“زاپاس کاباره خونه” (@kabare_home), 2,525 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/kabare_home.

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.