Telegram RegisterThe public register of Telegram
Telegram profile photo for نرخ انس کهکشان

Channel

نرخ انس کهکشان

@qheimat_ounce

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

24,798subscribers

+287 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001459105711
TypeChannel
Username@qheimat_ounce
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live6 November 2026
Measurements held59
Confirmed unchanged1 time, most recently 6 November 2026
On Telegramt.me/qheimat_ounce

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 46% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

24,51124,80524,6586 August 2026 — 24,511 subscribers6 August 2026 — 24,511 subscribers7 August 2026 — 24,526 subscribers8 August 2026 — 24,531 subscribers9 August 2026 — 24,525 subscribers10 August 2026 — 24,529 subscribers11 August 2026 — 24,537 subscribers12 August 2026 — 24,544 subscribers13 August 2026 — 24,562 subscribers15 August 2026 — 24,555 subscribers16 August 2026 — 24,556 subscribers17 August 2026 — 24,569 subscribers18 August 2026 — 24,570 subscribers19 August 2026 — 24,585 subscribers20 August 2026 — 24,595 subscribers21 August 2026 — 24,616 subscribers23 August 2026 — 24,620 subscribers24 August 2026 — 24,610 subscribers25 August 2026 — 24,612 subscribers26 August 2026 — 24,611 subscribers27 August 2026 — 24,610 subscribers28 August 2026 — 24,615 subscribers29 August 2026 — 24,641 subscribers30 August 2026 — 24,634 subscribers31 August 2026 — 24,644 subscribers1 September 2026 — 24,647 subscribers2 September 2026 — 24,643 subscribers4 September 2026 — 24,649 subscribers6 September 2026 — 24,656 subscribers9 September 2026 — 24,665 subscribers12 September 2026 — 24,667 subscribers13 September 2026 — 24,663 subscribers15 September 2026 — 24,676 subscribers17 September 2026 — 24,700 subscribers28 September 2026 — 24,714 subscribers5 October 2026 — 24,740 subscribers9 October 2026 — 24,756 subscribers14 October 2026 — 24,761 subscribers15 October 2026 — 24,757 subscribers17 October 2026 — 24,753 subscribers18 October 2026 — 24,746 subscribers19 October 2026 — 24,750 subscribers20 October 2026 — 24,748 subscribers21 October 2026 — 24,744 subscribers22 October 2026 — 24,753 subscribers23 October 2026 — 24,761 subscribers24 October 2026 — 24,760 subscribers25 October 2026 — 24,761 subscribers27 October 2026 — 24,765 subscribers28 October 2026 — 24,772 subscribers29 October 2026 — 24,800 subscribers30 October 2026 — 24,795 subscribers31 October 2026 — 24,801 subscribers1 November 2026 — 24,805 subscribers2 November 2026 — 24,784 subscribers4 November 2026 — 24,773 subscribers4 November 2026 — 24,779 subscribers5 November 2026 — 24,794 subscribers6 November 2026 — 24,798 subscribers24,7986 August 20266 November 2026
59 measurements spanning 92 days, net +287. 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 24,467–24,849 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 59
Measured (UTC)SubscribersChange
6 Nov 2026, 22:2524,798+4
5 Nov 2026, 22:0724,794+15
4 Nov 2026, 22:4424,779+6
4 Nov 2026, 00:5824,773-11
2 Nov 2026, 23:1524,784-21
1 Nov 2026, 22:1124,805+4
31 Oct 2026, 20:4924,801+6
30 Oct 2026, 22:1624,795-5
29 Oct 2026, 22:4524,800+28
28 Oct 2026, 22:0124,772+7
27 Oct 2026, 01:2824,765+4
25 Oct 2026, 23:1824,761+1
24 Oct 2026, 22:3524,760-1
23 Oct 2026, 21:2624,761+8
22 Oct 2026, 23:1524,753+9
21 Oct 2026, 17:4824,744-4
20 Oct 2026, 12:5924,748-2
19 Oct 2026, 12:3924,750+4
18 Oct 2026, 15:0024,746-7
17 Oct 2026, 18:0024,753first reading

Engagement

1,991 posts held, back to 6 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 127 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.10%
avg views ÷ 24,798 subscribers
Avg views / post
273
783 posts measured
Reaction rate
0.175%
reactions ÷ views · ER floor
Posts in window
783
of 1,991 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. It is computed over the 39 of 783 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 November 2026
Posts held1,991 (6 August 2026 – 6 November 2026)
Views total213,975
Reactions total198
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Nov 2026, 14:40 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

243 reactions across 44 posts, in 4 distinct kinds. The most used accounts for 87.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤21387.7%
🔥239.47%
👍52.06%
😎20.823%

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

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 1 October 2026 to 6 November 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

Telegram’s own ‘edited’ marker: 0 of 783 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

Showing the 12 most recent of 1,991 posts we hold for @qheimat_ounce. 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.

Forward network

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

آن تايم انس
@ontimeounce · 53,612
Telegram ranks this channel #18 of 79 here — alongside 78 others — read 24 August 2026
نقدی(پله)
@NaghdP · 72,795
Telegram ranks this channel #39 of 73 here — alongside 72 others — read 21 August 2026
🔺پله آهنی آنلاین 🔻
@tehranpelle · 57,062
Telegram ranks this channel #53 of 77 here — alongside 76 others — read 23 August 2026
آبشده نقدی پایتخت
@abshdanaghdy · 178,601
Telegram ranks this channel #57 of 71 here — alongside 70 others — read 12 August 2026
JUST IN TIME
@abshdh · 198,185
Telegram ranks this channel #62 of 82 here — alongside 81 others — read 12 August 2026
نرخ لحظه ای دلار تهران
@NerkhDollarIRT · 90,282
Telegram ranks this channel #66 of 73 here — alongside 72 others — read 18 August 2026
️️کینگ پاور ترید️️
@king_powr · 49,223
Telegram ranks this channel #67 of 75 here — alongside 74 others — read 26 August 2026

This channel appears in 7 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“نرخ انس کهکشان” (@qheimat_ounce), 24,798 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/qheimat_ounce.

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.