Telegram RegisterThe public register of Telegram

Channel

زاپ Ko3enj

@Ko3enj

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

71,581subscribers

-1,929 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001147542525
TypeChannel
Username@Ko3enj
Descriptionب احترام اعضای گل هیچگونه تبلیغات و ممبر فروشی نداره کصنج ♥️ هیچگونه آیدی خاله و صیغه یاب و این کسشعرات رو نداریم و هرچیزی تو این زمینه (خاله و صیغه) ببینید تو دنیای مجازی صدی صد فیکه فیککککک. فداتون♥️
Created2 September 2017measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live12 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/Ko3enj

Growth

71,58173,51072,545.57 August 2026 — 73,510 subscribers8 August 2026 — 73,256 subscribers9 August 2026 — 72,980 subscribers10 August 2026 — 72,710 subscribers11 August 2026 — 72,430 subscribers12 August 2026 — 71,581 subscribers7 August 202612 August 2026
6 measurements spanning 5 days, net -1,929. 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 71,292–73,799 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 12:5371,581-849
11 Aug 2026, 12:2572,430-280
10 Aug 2026, 12:0872,710-270
9 Aug 2026, 11:5272,980-276
8 Aug 2026, 10:5673,256-254
7 Aug 2026, 13:1673,510first reading

Engagement

4 posts held, back to 2 September 2017the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 17 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
6.69%
avg views ÷ 71,581 subscribers
Avg views / post
4,790
1 post measured
Reaction rate
0.626%
reactions ÷ views · ER floor
Posts in window
1
of 4 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 12 August 2026
Posts held4 (2 September 201712 August 2026)
Views total4,790
Reactions total30
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 07:25 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

Links
3

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

538 reactions across 3 posts, in 4 distinct kinds. The most used accounts for 42.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
22742.2%
🏆12823.8%
🌭10219.0%
🔥8115.1%

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

Measured over the 4 most recent posts we hold, published 2 September 2017 to 12 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

12 Aug 2026, 07:19 UTC≈4,790 views30 reactionsread 13 August 2026

کصنج دوباره فیلـتر شد💔! برای همراهیمون تو کانال جدید عضو بشید❤️👇 https://t.me/+eLy-2dHH7XJiZTk8

🔥1510🏆5

10 May 2026, 11:30 UTC≈85,900 views169 reactionsread 13 August 2026

کصنج جدید جوین شدی؟؟ دوستان استارت زدیم حمایت کنید ک پیوسته بترکونیم کنار هم😘❤️ سبک ایکس بزودی https://t.me/+eLy-2dHH7XJiZTk8

63🔥40🌭33🏆33

9 Dec 2025, 08:05 UTC≈250,000 views339 reactionsread 13 August 2026

اینجا زاپاسه دوستان حتما عضو بمونید :) هروقت کصنج بگا رفت اینجا ادامه میدیم❤️ کانال فعلی 👇 👇👇 https://t.me/Kosenjio

154🏆90🌭69🔥26

Showing the 4 most recent of 4 posts we hold for @Ko3enj. 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.

Posts edited after publishing

@Ko3enj edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
12 August 2026
Most recent edit
12 August 2026

Citation-graph rank

Citation-graph rank — 736,015 of 1,169,250entries 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.

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.

Names

Channels on the register whose handles appear in this channel's posts.

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

“زاپ Ko3enj” (@Ko3enj), 71,581 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Ko3enj.

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.