4 measurements spanning 4 days, net +6. 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,643–2,651 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
11 Aug 2026, 06:03
2,650
+3
8 Aug 2026, 08:52
2,647
+3
7 Aug 2026, 13:33
2,644
no change
7 Aug 2026, 12:20
2,644
first reading
Engagement
20 posts held, back to 3 January 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 1 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
29.5%
avg views ÷ 2,650 subscribers
Avg views / post
781
4 posts measured
Reaction rate
1.09%
reactions ÷ views · ER floor
Posts in window
4
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 7 August 2026
Posts held
20 (3 January 2026 – 7 August 2026)
Views total
3,122
Reactions total
34
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Aug 2026, 13:33 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
237 reactions across 20 posts, in 6 distinct kinds. The most used accounts for 92.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
220
92.8%
👍
11
4.64%
🔥
3
1.27%
👏
1
0.422%
😁
1
0.422%
🙏
1
0.422%
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 237reactions 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 3 January 2026 to 7 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.
Advertising
Ad load
5.00%
1 of 20 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
1,580
over 1 measured post
Median views · rest
1,660
over 19 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
Advertising tokens recorded on this entry
erid
Posts
First seen
Last seen
backStackEntry
1
12 February 2026
12 February 2026
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 20 most recent posts we hold, published 3 January 2026 to 7 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
#آموزش_اندروید
🚨🚨 چطور رویدادهای یکباره (Single-shot Events) را درست مدیریت کنیم؟
❗️در قسمت قبل گفتیم که نگهداشتن رویدادهایی مثل نمایش Snackbar، Toast یا Navigation داخل State باعث اجرای تکراری آنها میشود. حالا راهکار اصولی چیست؟
❗️برای مدیریت این رویدادها دو دیدگاه اصلی در معماری اندروید وجود دارد:
1️⃣ روش اول: الگوی Event-Consumption (روش رسمی و پیشنهادی گوگل)
در این روش، رویداد داخل State قرار دارد، اما U…
#آموزش_اندروید
🚨🚨 چرا نباید رویدادها را داخل State نگه داریم؟!
❗️یکی از رایجترین اشتباهاتی که حتی در پروژههای بزرگ هم دیده میشود، نگهداری رویدادهای یکباره (Single-shot Events) داخل StateFlow یا LiveData است.
❗️فرض کنید بعد از ثبت موفق اطلاعات، میخواهید یک Snackbar نمایش دهید. خیلی از برنامهنویسها این کار را انجام میدهند:
uiState = uiState.copy(
showSnackBar = true
)
• در نگاه اول همه چیز درست کار میکن…
تا حالا شده حس کنی بیشتر از چیزی که الان هستی، ظرفیت داری… اما ندونی از کجا باید شروع کنی؟
تا حالا شده بین هدفهات، انتخاب مسیر درست، رشد شخصی و ساختن آینده بهتر سردرگم بشی؟
دوره Life Spark دقیقاً برای همینه…
یک مسیر کامل و کاربردی برای اینکه خودت رو بهتر بشناسی، هدفهات رو مشخص کنی و قدمبهقدم برای ساختن نسخه بهتر خودت حرکت کنی..
در این دوره یاد میگیری چطور:
✅ مسیر رشد شخصی خودت رو پیدا کنی
✅ هدفگذاری اصولی داش…
🎙️دانشجویارکست | مسیـر واقعـی رشـد در دنیـای کامپیوتـر
هر برند موفقـی، یه داستان برای گفتن داره…
اما داستان دانشجویار از کجا شروع شد؟
و چه چالشهایی پشت مسیر شکلگیریش بود؟
در اولین قسمت دانشجویارکست، آقای پاسبان، همبنیانگذار دانشجویار، از روزهای آغازین، چالشها، تصمیمهای مهم و تجربههایی میگن که کمتر درباره صحبت شده✨
📺 اگر دوست داری پشتصحنه شکلگیری دانشجویار رو از زبان یکی از بنیانگذارانش بشنوی، همین حالا …
بزرگـتریـن چالـش بعد از
یادگـیری کامپیوتـر چیــه؟🤔
مهمترین و پررنگترین مشکل کاربرای ما همیشه پیدا کردن پروژه و ارتباط گرفتن با کارفرما بوده و هنوز هم هست.👀
در واقع، تقریباً هر کسی که وارد دنیای کامپیوتر میشه، یه جا از خودش میپرسه:
👈 حالا دقیقاً باید چه مسیری برم؟ از کجا شروع کنم؟ چطور وارد بازار کار بشم؟
به همین خاطر ما دانشجویارکست رو آماده کردیم؛ مجموعهای از ویدیوها با حضور افراد مختلف و باتجربهی دانشجویار …
#آموزش_اندروید
🚨🚨 کاتلین ۲.۰ و کامپایلر K2؛ شتابدهنده جدید پروژههای شما!
❗️اگر برنامهنویس اندروید هستید، حتماً بارها موقع بیلد شدن پروژههای سنگین به صفحه مانیتور خیره شدهاید! با انتشار Kotlin 2.0، موتور زیرین این زبان یعنی کامپایلر به طور کامل از نو نوشته شده و «کامپایلر K2» متولد شده است. این آپدیت یک گام رو به جلو برای پرفورمنس و هوشمندی کاتلین است.
✅ ویژگیها و تغییرات کلیدی در Kotlin 2.0:
1️⃣ بهبود محسوس…
#آموزش_اندروید
🚨🚨 راز افزایش عملکرد در Compose با Stable و Immutable (بخش دوم)
❗️در پست قبلی با مفهوم Stability و مشکل ناپایداری لیستها آشنا شدیم. حالا وقت آن رسیده که ببینیم چگونه میتوانیم به Compose کمک کنیم تا Recompositionهای غیرضروری را حذف کند.
1️⃣ استفاده از کلاس Wrapper و انوتیشن @Immutable
اگر در کلاسی از List یا لایبرریهای جاوا استفاده کردهاید و مطمئن هستید دادهها بعد از ساخت تغییر نمیکنند، با انو…
#آموزش_اندروید
🚨🚨 چرا Composable شما بیدلیل Recompose میشود؟ (بخش اول)
❗️یکی از بزرگترین مزیتهای Jetpack Compose این است که فقط بخشهای لازم رابط کاربری را مجدداً رسم میکند. اما اگر دادهها و کلاسهای شما به درستی طراحی نشده باشند، ممکن است Compose تصور کند همه چیز تغییر کرده و دوباره Composableها را اجرا کند.
❕در اینجا مفهوم بسیار مهمی به نام Stability وارد میدان میشود.
✅ مفهوم Stability:
زمانی که Compos…
#آموزش_اندروید
🚨🚨 استفاده از PredictiveBackHandler در Compose (بخش سوم)
❗️اگر بخواهید پا را فراتر از انیمیشنهای پیشفرض بگذارید و همزمان با حرکت انگشت کاربر، تغییر خاصی "داخل" صفحه ایجاد کنید (مثلاً لرزش یک آیکون یا تغییر شفافیت یک المان خاص)، باید از PredictiveBackHandler استفاده کنید.
⚠️ یک هشدار فنی:
وقتی از این Handler استفاده میکنید، شما مدیریت بازگشت را از سیستم میگیرید. این یعنی سیستم دیگر به صورت خودکا…
#آموزش_اندروید
🚨🚨 تعامل Predictive Back با Navigation Compose (بخش دوم)
❗️در نسخههای جدید Navigation Compose (از ۲.۷ به بالا)، پشتیبانی داخلی از Predictive Back اضافه شده است. این یعنی اگر انیمیشنهای بازگشت (pop) را تعریف کنید، خودِ کتابخانه Navigation جادوی هماهنگی با انگشت کاربر را انجام میدهد.
⚠️ نکته کلیدی:
در این حالت، مدیریت ژست بازگشت کاملاً بر عهده Navigation است. انیمیشنهای popExitTransition به صورت …
#آموزش_اندروید
🚨🚨 هماهنگی با سیستم جدید Predictive Back (بخش اول)
❗️قابلیت Predictive Back به کاربر اجازه میدهد پیش از رها کردن دست، پیشنمایشی از صفحه قبلی را ببیند. برای اینکه اپلیکیشن شما با این سیستم جدید هماهنگ شود، باید پشتیبانی از OnBackInvokedCallback را در مانیفست فعال کنید. این کار به سیستمعامل اجازه میدهد مدیریت انیمیشنهای بازگشت را به دست بگیرد.
✅ مراحل فعالسازی:
• اصلاح مانیفست: اعلام پشتیبانی ر…
اگر میخوای بدونی آینده مشاغل کامپیوتری به چه سمتی میره و چطور میشه برای ۳ تا ۵ سال آینده برنامهریزی کرد…👀
ما فصل دوم دوره لایف اسپارک "جرقه زندگی" رو بهصورت رایگان و مرحلهای در آپارات و یوتیوب دانشجویار منتشر میکنیم تا قبل از تهیه این دوره، با فضای آموزش آشنا بشی😍✌️
قسمتهای منتشرشده:
👈 قسمت اول فصل دوم
- آپارات:
https://www.aparat.com/v/prf3b9n?refererRef=channel_page
- یوتیوب:
https://youtu.be/7850rBTAhqk
…
❤6
Showing the 12 most recent of 20 posts we hold for @KotlinMag. 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
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.
Mentions
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 11 August 2026 — this
entry's latest reading, not the date you are reading this.
“برنامه نویسی اندروید با زبان کاتلین” (@KotlinMag), 2,650 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/KotlinMag.
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.