9 Apr 2026, 20:58 UTC79 viewsread 13 August 2026
>>> family husbands🌪️ <<< mothers & fathers ^ sisters ; kids `` puppies # hraniteli • b-frieds ; g-friends epsteinshi " obijenki ™ teammates !! kumiho * gossips ° hedgehog omegas $ alfas
Channel
info ayanovskie
@ayanovskieinfo
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
2subscribers
+0 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003716308054 |
|---|---|
| Type | Channel |
| Username | @ayanovskieinfo |
| Created | 19 February 2026 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/ayanovskieinfo |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 19:16 | 2 | no change |
| 9 Aug 2026, 20:15 | 2 | first reading |
Engagement
8 posts held, back to 19 February 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 8 posts for this entry, the most recent from 9 April 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Links
- 1
Lifetime counters from Telegram’s own channel header, read 13 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.
Recent posts
25 Mar 2026, 17:24 UTC96 viewsread 13 August 2026
администрация владелец - аянчик интерактив админы - яся, креган, андре
22 Feb 2026, 07:31 UTC235 viewsread 13 August 2026
набор на союзы закрыт.
22 Feb 2026, 07:28 UTC245 viewsread 13 August 2026
союзники аяновских зайчата - милфы - фюмири - мурасаки - неоми - ланвиарс - амбассадоры - люминара - ланери - авелон - дестройские - склиф - блоккидс - таурин - виспо - чармские - лорион - приквел - мириэль - аверлесс - будуар - бесправные - лицемеры - понивиль - вишневские - еверскиез если вас нет писать -
22 Feb 2026, 07:28 UTC247 viewsread 13 August 2026
краш лист - семья лучшие из лучших
22 Feb 2026, 07:23 UTC244 viewsread 13 August 2026
любимая семья - мужья - наймит🤩 - сестрички - зайчата - подружки - юген - щенята - дестройские - мамы - маллет - папы - папские - хранители - блоккидс - эпштейнши - рифазэрит - обиженки - таурин - тиммейтеры - стимские - кумихо - люминара - сплетницы - комфорт - ёжик - рэйновские - элпэ - ланвиарс - омежки - будуар - детишки - делюкс - альфы - еверскиез - джуди - чармские самые прекрасные
22 Feb 2026, 07:19 UTC200 viewsread 13 August 2026
правила для сотрудничества🌪️ - для нас главное дружеские отношения. - заключаем 0+ только актив. - рп и вз не заключаем. - союзы заключаются 1:1 до 5:5. - о всех изменениях предупреждать лично админа. - норма - минимум 30 соо в неделю/зеркально. - рп держится на канале 4-5 часов. - о выходных предупреждаем заранее. - союз лист. - писать - набор закрыт.
19 Feb 2026, 05:30 UTCviews —
Channel created
Showing the 8 most recent of 8 posts we hold for @ayanovskieinfo. 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 — 436,707 of 1,481,346entries 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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“info ayanovskie” (@ayanovskieinfo), 2 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/ayanovskieinfo.
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.