4 measurements spanning 3 days, net -3. 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 1,180–1,183 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
10 Aug 2026, 14:26
1,180
-2
7 Aug 2026, 23:31
1,182
no change
7 Aug 2026, 21:41
1,182
-1
7 Aug 2026, 19:11
1,183
first reading
Engagement
20 posts held, back to 20 February 2025 — the 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
27.9%
avg views ÷ 1,180 subscribers
Avg views / post
329
1 post measured
Reaction rate
2.43%
reactions ÷ views · ER floor
Posts in window
1
of 20 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
Window
Rolling 30 days · latest post in window 16 July 2026
Posts held
20 (20 February 2025 – 16 July 2026)
Views total
329
Reactions total
8
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Aug 2026, 23:31 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.
Reaction mix
267 reactions across 19 posts, in 27 distinct kinds. The most used accounts for 18.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
48
18.0%
😭
43
16.1%
👏
25
9.36%
🐳
21
7.87%
😇
19
7.12%
🔥
18
6.74%
👍
17
6.37%
🙏
9
3.37%
🆒
7
2.62%
💔
7
2.62%
❤🔥
6
2.25%
🌭
6
2.25%
🕊
5
1.87%
💋
4
1.50%
🦄
4
1.50%
⚡
3
1.12%
🍓
3
1.12%
🍾
3
1.12%
🎃
3
1.12%
😁
3
1.12%
7 further kinds
13
4.87%
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 20 of the 20 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 267reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 20 February 2025 to 16 July 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 plans to release Serverless bots.
(https://core.telegram.org/bots/serverless)
(currently in closed beta, will be public soon TM)
Currently,it is far easier for many to vibe code(make with AI) bots. with Serverless feature, if it's free, hosting will be managed by Telegram, so very easy, like Free Heroku Era.
that'll be the best thing to happen to many people,
as you can actually have a personal bot. and c…
hello guys,
for a few days bot is dying a lot.
For some failures, I need my laptop and can't fix it in my office hours.
But, I'll fix this problem this weekend so stay stuned.
meanwhile remember
@famtreebbot is available in case you are dying to use it. (you should !)
^
Buying bot money with real money.
prices have dropped.
everything will be 10 INR/million.
so, for 10 million it is 100INR.
to purchase, dm @invisibleobsidian
don't expect instant replies there won't be any changes in prices even if you're mass buying.
I had to do this not to gain money but to stop people from doing it in black.
To keep the "community" like vibe, (without me being active)
We'll try to revive @fam_tree_memes.
You can send memes or really anything related to fam-tree to @fam_tree_support_bot or @fam_tree_official
then , we'll forward it.
You can add: memes, beautiful trees, /q of jokes/drama and maybe some ads of groups.
If idea of this channel really worked out, then there'll be a fam tree community site.
Federated Groups (group listing):
Now,
You can add your group chat to bot's list of groups.
Then doing /groups will show your group chat with number of messages done on that day.
Active groups will be on top.
this way, your group will join other number of groups who will play fam tree.
On how to set it up, please DM me @fam_tree_official (or comment below)
(This will be new official account maintained by board memb…
Showing the 12 most recent of 20 posts we hold for @fam_tree. 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 — 808,074 of 1,151,006entries 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
Named by 2 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.
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 10 August 2026 — this
entry's latest reading, not the date you are reading this.
“Fam Tree Development” (@fam_tree), 1,180 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/fam_tree.
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.