2 measurements spanning 2 days. 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 33–35 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
11 Aug 2026, 00:01
34
no change
9 Aug 2026, 00:45
34
first reading
Engagement
10 posts held, back to 7 May 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
65.2%
avg views ÷ 34 subscribers
Avg views / post
22.2
6 posts measured
Reaction rate
5.56%
reactions ÷ views · ER floor
Posts in window
9
of 10 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 1 of 6 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 6 August 2026
Posts held
10 (7 May 2026 – 6 August 2026)
Views total
133
Reactions total
1
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
11 Aug 2026, 00:01 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
Photos
750
Videos
90
Links
7
Lifetime counters from Telegram’s own channel header, read 11 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.
Video runtime
58s
Average length
58s
Measured directly from 1 video 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
1 reaction across 1 post, in 1 kind.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
1
100.0%
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 1 of the 10 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 1reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 7 May 2026 to 6 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.
Битва при Платеях: конец персидского вторжения(греко-персидские войны)🇬🇷 🇮🇷
После разорения Афин войско Мардония, в котором сражались персы, мидийцы и скифы-саки, отступило в Беотию и заняло позицию у города Платеи. Там его ожидала большая греческая армия под командованием спартанца Павсания.
Согласно Геродоту, под руководством Мардония находилось 300 тысяч воинов из империи Ахеменидов и около 50 тысяч греков, котор…
Речь Павсания перед Платеями
(Греко-персидские войны)🇬🇷
🇮🇷
Перед началом сражения при Платеях собралась многонациональная армия Ахеменидов. В её рядах стояли персы, мидийцы, скифы-саки, греки, финикийцы, арабы и ассирийцы.
Спартанский командующий Павсаний обратился к своим воинам:
«Мужи спартанские! Долго я размышлял над словами о победе. Время доказало их мудрость. От свободного грека к свободному греку разнеслось…
Железом и огнём: кара Персии(греко-персидские войны) 🇬🇷🇮🇷
Весной 479 года до н. э. персидское войско под командованием Мардония снова вошло в Аттику. Афины не были полностью пусты — часть жителей осталась в городе. Персы заняли его и принялись методично разрушать всё, что ещё уцелело после прошлогоднего разорения. Они сжигали храмы, рушили дома, ломали стены и уничтожали всё ценное. Огонь пожирал квартал за квартало…
Битва при Саламине (греко-персидские войны) 🇬🇷🇮🇷
(сентябрь 480 г. до н. э.)
После поражения при Фермопилах и падения Афин персы заняли Среднюю Грецию. Греческий флот численностью около 370 триер занял узкий пролив у острова Саламин. Ахеменидский флот значительно превосходил его силами. В его составе сражались финикийцы, египтяне, ионийские греки, а также иранские народы — персы и мидийцы.
Командование формально пр…
Ахеменидский царь в короне убивает греческого гоплита. Оттиск с цилиндрической печати, созданной приблизительно в 500–475 гг. до н.э., во времена Ксеркса.
Фермопильское сражение(Греко-Персидские войны)🇬🇷🇮🇷
Битва между могущественной армией Ахеменидской державы под командованием Ксеркса I и объединёнными Греческими силами во главе с Леонидом I. Битва произошло в узком проходе Фермопилы во время Греко-персидских войн.
Греки попытались закрепиться в узком ущелье, надеясь нейтрализовать численное превосходство персов. Несколько дней они сдерживали натиск, однако войска ир…
ФРАКИЙЦЫ В АРМИИ АХЕМЕНИДОВ
Фракийцы — индоевропейский народ юго-восточной части Балкан (территории современной Болгарии и северо-западной части Турции), соседствующие с Западной Азией(MENA) — вошли в состав Ахеменидской империи после военных походов персов при Дарии I.
В ходе скифского похода персидская армия прошла через Фракию силой, подчинив местные восточнобалканские племена и установив контроль над восточными…
Showing the 10 most recent of 10 posts we hold for @TheFirstWestAsianW. 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.
Citation-graph rank
Citation-graph rank — 874,087 of 1,350,102entries 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
“Первый Западный Азиатский” (@TheFirstWestAsianW), 34 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/TheFirstWestAsianW.
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.