Channel
@ArmathosOFC
On this record: Growth ยท Engagement ยท Posts ยท Citations ยท Handles named that no longer answer ยท Cite this entry
1,033subscribers
-11 since we began measuring on 6 August 2026
Risers and fallers across the register ยท movement among entries of 1,000โ3,162.
| Telegram ID | -1003459529158 |
|---|---|
| Type | Channel |
| Username | @ArmathosOFC |
| Created | Between 1 November 2025 and 31 March 2026โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 26 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 26 August 2026 |
| On Telegram | t.me/ArmathosOFC |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Aug 2026, 07:13 | 1,033 | -1 |
| 23 Aug 2026, 06:45 | 1,034 | -1 |
| 20 Aug 2026, 00:47 | 1,035 | -1 |
| 16 Aug 2026, 18:27 | 1,036 | -6 |
| 10 Aug 2026, 14:42 | 1,042 | -3 |
| 7 Aug 2026, 04:23 | 1,045 | +1 |
| 6 Aug 2026, 13:01 | 1,044 | no change |
| 6 Aug 2026, 09:22 | 1,044 | first reading |
18 posts held, back to 13 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 pageof 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.
| Window | Rolling 30 days ยท latest post in window 30 July 2026 |
|---|---|
| Posts held | 18 (13 July 2026 โ 30 July 2026) |
| Views total | 285 |
| Reactions total | โ |
| Forwards / comments | not exposed by the public surface โ not measured, not estimated |
| Readings taken | 6 Aug 2026, 13: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.
https://t.me/ArmathosOFC/3750?comment=6712 https://t.me/ArmathosOFC/3750?comment=6713 https://t.me/ArmathosOFC/3750?comment=6714 https://t.me/ArmathosOFC/3750?comment=6715 kirim ss akun kalian yang no zoom + foto kalian bebas jangan yang miror selfi kirim ke @reyvanderassist_bot
Ok ditunggu ya manis
jadi kok ga php
iya saua edit
Udh ayo, awas kamu PHP-in saya
ini yang ber 4 ini beneran mau jj?
kalau mimin ajakin jj kalian pada mau ga
sepi nyaa ch ini
sepi nya..
DOR
di catat ya tuan dan nona jika ingin berkunjung
Sticker, posted without a caption
Showing the 12 most recent of 18 posts we hold for @ArmathosOFC. 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 โ 941,291 of 1,623,166entries 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.
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 18 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.
@ArmathosOFC named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handleโs history โ see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today โ not that anything โdiedโ. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant โ a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel โ we have no record it ever was one.
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 26 August 2026 โ this entry's latest reading, not the date you are reading this.
โ๐ฆ๐๐ข๐ช ๐ฅ๐ข๐ ๐๐๐|| ๐๐๐ข๐ฆ๐ ๐ ๐๐ ๐๐๐ฅโ (@ArmathosOFC), 1,033 subscribers as measured 26 August 2026. Telegram Register, tgregister.com/channel/ArmathosOFC.
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.