Channel
@Radiokocsher
On this record: Topic · Growth · Engagement · What this channel posts · View velocity · Stars · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Telegram's recommendations · Domains linked from posts · Cite this entry
1,152,592subscribers
+493,958 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1001279727614 |
|---|---|
| Type | Channel |
| Username | @Radiokocsher |
| Description | 🐐 Support @AvAmeshkut |
| Created | 6 April 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 61 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/Radiokocsher |
Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Nov 2026, 00:21 | 1,152,592 | -9,238 |
| 6 Nov 2026, 21:29 | 1,161,830 | -1,777 |
| 5 Nov 2026, 18:31 | 1,163,607 | +8,951 |
| 4 Nov 2026, 19:25 | 1,154,656 | +8,264 |
| 3 Nov 2026, 18:26 | 1,146,392 | +8,119 |
| 2 Nov 2026, 16:24 | 1,138,273 | +7,737 |
| 1 Nov 2026, 13:54 | 1,130,536 | +7,861 |
| 31 Oct 2026, 12:00 | 1,122,675 | +4,569 |
| 30 Oct 2026, 08:28 | 1,118,106 | +8,281 |
| 29 Oct 2026, 07:00 | 1,109,825 | -6,763 |
| 28 Oct 2026, 04:48 | 1,116,588 | -8,027 |
| 27 Oct 2026, 02:46 | 1,124,615 | -9,068 |
| 26 Oct 2026, 03:28 | 1,133,683 | +3,103 |
| 25 Oct 2026, 01:00 | 1,130,580 | +9,286 |
| 23 Oct 2026, 23:46 | 1,121,294 | +19,196 |
| 23 Oct 2026, 01:19 | 1,102,098 | +9,243 |
| 22 Oct 2026, 01:00 | 1,092,855 | +17,301 |
| 20 Oct 2026, 16:36 | 1,075,554 | +114 |
| 19 Oct 2026, 15:07 | 1,075,440 | +19,007 |
| 18 Oct 2026, 14:10 | 1,056,433 | first reading |
1,887 posts held, back to 5 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 197 pages of Telegram’s post history, 20 posts per page.
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 53 of 604 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 November 2026 |
|---|---|
| Posts held | 1,887 (5 August 2026 – 8 November 2026) |
| Views total | 52,453,350 |
| Reactions total | 0 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Nov 2026, 00:15 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.
Lifetime counters from Telegram’s own channel header, read 8 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 12 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.
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
Computed from 428 of this channel’s own posts over the last 30 days (3 of the 24-hour readings behind this are interpolated, not measured directly): across 410 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 6.3 hours of being posted; a typical post has already reached 22.1% of its 24-hour view count within the first hour, and 63.6% within the first six; the median 24-hour reach across those posts is 76,000 views — 6.59% of this channel’s own subscriber count (90th percentile 85,510).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /831248 Nov 2026, 23:06 UTC | 210 minutes – 69 minutes old | 4,120 views ~no reaction reading | 60 minutes: 3,698 interp. | not yet at 24h | 24 minutesprovisional — final view count still climbing |
| /831238 Nov 2026, 22:32 UTC | 39 minutes – 1.7 hours old | 9,230 views ~no reaction reading | 60 minutes: 7,737 interp.still climbing at last reading | not yet at 24h | 22 minutesprovisional — final view count still climbing |
| /831228 Nov 2026, 22:02 UTC | 49 minutes – 2.2 hours old | 14,000 views ~no reaction reading | 60 minutes: 11,187 interp.still climbing at last reading | not yet at 24h | 26 minutesprovisional — final view count still climbing |
| /831218 Nov 2026, 20:47 UTC | 554 minutes – 3.5 hours old | 25,200 views ~no reaction reading | 60 minutes: 15,153 interp. → 3.0 hours: 24,596 interp.still climbing at last reading | not yet at 24h | 54 minutesupper bound — already past half at first reading · provisional — final view count still climbing |
| /831208 Nov 2026, 19:56 UTC | 714 minutes – 4.3 hours old | 33,900 views ~no reaction reading | 60 minutes: 17,253 interp. → 3.0 hours: 31,794 interp.still climbing at last reading | not yet at 24h | 58 minutesprovisional — final view count still climbing |
| /831198 Nov 2026, 19:27 UTC | 911 minutes – 4.8 hours old | 38,200 views ~no reaction reading | 60 minutes: 19,781 interp. → 3.0 hours: 34,432 interp.still climbing at last reading | not yet at 24h | 56 minutesprovisional — final view count still climbing |
| /831188 Nov 2026, 19:26 UTC | 911 minutes – 4.8 hours old | 36,600 views ~no reaction reading | 60 minutes: 19,320 interp. → 3.0 hours: 33,040 interp.still climbing at last reading | not yet at 24h | 53 minutesprovisional — final view count still climbing |
| /831178 Nov 2026, 18:20 UTC | 1115 minutes – 5.9 hours old | 43,700 views ~no reaction reading | 60 minutes: 17,978 interp. → 3.0 hours: 35,822 interp. → 6.0 hours: 43,700still climbing at last reading | not yet at 24h | 78 minutesprovisional — final view count still climbing |
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Radiokocsher. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 19 September 2026 to 8 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Telegram’s own ‘edited’ marker: 17 of 604 posts held from the last 30 days (2.81%) 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).
🃏🔥 آس و شاه روی میز؛ این یعنی یه بلکجک تمامعیار! 👑 💎 کازینو زنده ZOMABET | جایی که هر کارت یه داستان تازه داره! ❗️ یه طرف دیلرهای حرفهای، یه طرف تو و تصمیمهات! از هیجان رسیدن به عدد ۲۱ تا لحظهای که کارت آخر رو میشه؛ اینجا هر دست یه تجربه متفاوته! 😈⚡️ 🥂 بلکجک، رولت و کلی بازی زنده با فضایی لوکس و جذاب؛ همه توی زومابت! 🎰✨ 🎁 بونوسهای ویژه ZOMABET: 🪙 ۱۰۰٪ بونوس واریز کریپتو 💵 ۳۰٪ بونوس واریز تومانی 💎 ۵۰ دلار بو…
وقتی تازه دندوناتو لمینت کردی.
درستش همینه. تا می تونید فحش بدید .
منم همینطور گربه، منم همینطور
😫
نظریه نامحبوب: داشتن جشن ازدواج جمع جور با دوستات خیلی بهتره تا اون جشنا با هزار نفر دعوتی
⚔️ شب های مبارزه | جایی که قدرت، تمرکز و جسارت حرف اول رو میزنن! 👊💥 از ضربات سنگین تا ناکاوتهای غیرمنتظره؛ تو دنیای مبارزات، هیچچیز تا آخرین ثانیه قطعی نیست! 😈⚡️ 🏆 هر راند یه نبرد جدیده و هر مبارزه میتونه یه پایان غافلگیرکننده داشته باشه! 💚 مسابقات بوکس رو با ضرایب ویژه ZOMABET دنبال کن! 🎯 🎁 بونوسهای ویژه ZOMABET: 🪙 ۱۰۰٪ بونوس واریز کریپتو 💵 ۳۰٪ بونوس واریز تومانی 💎 ۵۰ دلار بونوس ثبتنام 🌐 ZOMABET.COM 🤩 کانال…
تو دیگه منو نفرین نکن، من خودم گرایشم به مردهاست، از قبل نفرین شدم
هرکی این لباس رو نداره زندگیو باخته
این داستان که در ایران سکسورکر مرد نداریم، خودش ریشه در زنستیزی داره.
چقدر کم عقل تشریف دارید، میگم زندگی طرف بخاطر پخش شدن ویدیوش خراب شد میگید میخواست کیر ساک نزنه کصخلا شماهم سکس میکنید دیگه تنها فرقش اینه که فیلم شما درنیومده
از زیباییهای دین مبین اسلام:
Showing the 12 most recent of 1,887 posts we hold for @Radiokocsher. 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.
@Radiokocsher edited 3 posts 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.
We recorded 5 posts on @Radiokocsher as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 8 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
This channel appears in 695 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
One domain this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“رادیوکصشر” (@Radiokocsher), 1,152,592 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/Radiokocsher.
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.