Gaming — 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 29 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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 why it has no browse page of its own yet.
Growth
5 measurements spanning 44 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 41–49 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
24 Sept 2026, 20:40
42
-4
26 Aug 2026, 14:17
46
-1
18 Aug 2026, 17:52
47
-1
11 Aug 2026, 17:51
48
no change
11 Aug 2026, 11:47
48
first reading
Engagement
20 posts held, back to 4 July 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 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 27 July 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
48s
Average length
24s
Measured directly from 2 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.
Reaction mix
15 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 53.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🤣
8
53.3%
❤
6
40.0%
👍
1
6.67%
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 6 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 15 reactions 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 4 July 2026 to 27 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.
🔺از تمامی دوستان عزیز که در این سیزن گیم ، مجددا با انرژی بی پایان مشارکت داشتند ، بسیار سپاسگزاریم
از صبر و همراهی کامل شما عزیزان و حمایت شما دوستان گل واقعا ممنونیم
نتایج آخرین جنگ های این سیزن نیز بارگزاری شده و پایان سیزن به این ترتیب اعلام میگردد
🟡•- عراق با تکیه بر برتری کامل هوایی و آتشبار توپخانهای سنگین، عملیات زمینی خود را با یک بمباران تهیه گسترده و ویرانگر با استفاده از بمبافکنهای استراتژیک و جنگندههای تهاجمی بر روی خطوط پیشروی اعتلاف آغاز میکند. بمبهای سنگین و هدایت لیزری ، قوای زرهی. و پیاده نظام اعتلاف غربی را با خاک یکسان کرده و با ایجاد دهانههای عریض و انفجارهای زنجیرهای، ساختار ترکیبی را از ریشه متلاشی میسازند. توپخانههای خودکششی عراق …
➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖
🚙•°[بخش زمینی]
🟡•- عراق : عراق با استقرار نیروهای خود در ویرانههای کویت سیتی و استفاده از ساختمانهای نیمهتخریبشده، زیرزمینها، استحکامات باقی مانده به عنوان پناهگاه و سنگر، یک شبکه دفاعی شهری غیرقابل نفوذ ایجاد کرده است. آرایش دفاعی عراق بر پایه سه جبهه مجزا با پشتیبانی متقابل و ارتباط از طریق استحکامات و بیسیمهای رمزی استوار است که هرگونه نفوذ دشمن را با تلههای مرگبار، کمینهای متحرک و آتش …
اعتلاف با وجود تلفات سنگین و عقبنشینی تاکتیکی ناوگان هوایی، توانسته است با حفظ بخشی از جنگندههای خود و استفاده از پدافندهای زمینی لایهای، همچنان تهدیدی هوایی محدود برای نیروهای ائتلاف ایجاد کند و با اجرای تاکتیکهای آمدوشد و کمینهای هوایی، فشار روانی بر خلبانان عراق را حفظ نماید. با این حال، در کوتاهمدت، آسمان میدان نبرد به طور کامل در اختیار عراق است و این برتری هوایی با تعداد زیاد ، تأثیر مستقیمی بر روند نبرد …
خطوط دفاعی با پشتیبانی متقابل سنگرها که هر نقطه از زمین مقابل زیر آتش حداقل چندین سنگر قرار دارد، و استفاده از تاکتیکهای ضدزره شامل موشکهای کوتاهبرد و توپهای بدون لگد، هرگونه نفوذ زرهی دشمن را در نقاط تنگ با تلههای مرگبار، آتش متقابل و انفجارهای کنترلشده مواجه میسازند. پدافندهای کوتاهبرد و موشکی عراق نیز با وجود اختلالات شدید جنگ الکترونیک مهاجم، به دلیل استفاده از سیستمهای الکترواپتیکی و هدایت تلویزیونی که …
•°[بخش زمینی]
➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖
🟡•- (اعتلاف): نیروی اعتلاف با ترکیبی از بمباران هوایی نسبی به خاطر تلفات توسط بمبافکنهای استراتژیک و جنگندههای چند منظوره ، و آتشبار توپخانهای متمرکز و هماهنگ، خطوط دفاعی اولیه عراق را در مرزهای ناصریه کمی ملایم تر کرده و با اجرای تاکتیکهای پیشروی محتاطانه و مرحلهای، از گرفتار شدن در تلههای فرسایشی و کمینهای کوهستانی (حیف بیابونه) جلوگیری میکند. مهاجم با استفاده از شناسایی ه…
Showing the 12 most recent of 20 posts we hold for @Castlevania_War. 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.
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.
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 24 September 2026 — this
entry's latest reading, not the date you are reading this.
“𝘊𝘢𝘴𝘵𝘭𝘦𝘷𝘢𝘯𝘪𝘢 𝘞𝘢𝘳” (@Castlevania_War), 42 subscribers as measured 24 September 2026. Telegram Register, tgregister.com/channel/Castlevania_War.
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.