Telegram RegisterThe public register of Telegram
Telegram profile photo for INFO ONIX

Channel

INFO ONIX

@FK0NIXXAII

On this record: Growth · Engagement · Posts · Citations · Cite this entry

18subscribers

+11 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003518000557
TypeChannel
Username@FK0NIXXAII
Created10 July 2026 — measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live13 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 13 September 2026
On Telegramt.me/FK0NIXXAII

Growth

71812.56 August 2026 — 7 subscribers12 August 2026 — 7 subscribers22 August 2026 — 9 subscribers29 August 2026 — 10 subscribers4 September 2026 — 14 subscribers13 September 2026 — 18 subscribers6 August 202613 September 2026
6 measurements spanning 38 days, net +11. 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 5–20 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Sept 2026, 08:2118+4
4 Sept 2026, 22:1714+4
29 Aug 2026, 04:3710+1
22 Aug 2026, 16:039+2
12 Aug 2026, 17:487no change
6 Aug 2026, 18:327first reading

Engagement

13 posts held, back to 10 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 13 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

24 Jul 2026, 16:00 UTC231 viewsread 12 August 2026

❤️ ТРЕБОВАНИЯ К АДМИНИСТРАЦИИ. ✔️Если вы хотите занимать должность админа по нью, то... • В неделю должно приходить не менее 4-х новых участников. • При отсутствии (или просьбе) владельца приписывать тэги с именем нового участника. • Соблюдать правила конференции и быть активным. ✔️Если вы хотите занимать должность админа по интерактивам, то... • В неделю должно проводиться не менее 2-х инт. • Уведомлять владельца …

20 Jul 2026, 05:35 UTC357 viewsread 12 August 2026

❤️ UNIONS. ✔️О Наших Принципах. • Мы всегда на стороне тех, кто прав, даже если это друзья. Нейтралитет — только пока нет полной картины. Уважение к нам — это база, без неё ничего не работает. ✔️По Делу. • О любых сменах юзов, перезагрузках или уходе подписчика — только в личку. Иначе не узнаем. • Если у вас рест, я могу не появляться у вас в канале. • Не подписались на нас —разрыв, но всегда можно начать заново.…

10 Jul 2026, 20:44 UTC420 viewsread 12 August 2026

🎁 INITIALS. Без Инициала и Подписки На Инфо Заявка Будет Отклонена. В ник: oni | nxx В био / инфо: @FK0NIXXAI | https://t.me/FK0NIXXAI

10 Jul 2026, 20:39 UTC410 views0 reactionsread 12 August 2026

ADMINISTRATION. 🎁 OWNER 🎀 Senior admin. × Admin by interactive. 🎀 Admin by unions. 🎀 Admin by chat. 🎀 Admin by chat. 🎀 Admin by chat. × Admin by new. × Admin by new. Вы можете подать свою кандидатуру на админство, написав об этом владельцу.

10 Jul 2026, 20:38 UTC332 viewsread 12 August 2026

К0НФЕРЕНЦИЯ ИСКЛЮЧИТЕЛЬНО СКЗ ВИРТ. Нотвирт, не скз — Нахуй. 1.1. Конфликты. В нашем чате не приветствуются ссоры. Огромная просьба решать все вопросы и недопонимания с другим человеком в лс. Каждому участвовавшему в каком либо конфликте выдается пред. 1.2. Поведение. Мы просим вести себя с остальными участниками подобающе. Если на вас прилетит жалоба на оскорбления/окорбительный юмор — в чате прилетит пред. Следит…

Showing the 12 most recent of 13 posts we hold for @FK0NIXXAII. 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 2 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.

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 13 September 2026 — this entry's latest reading, not the date you are reading this.

“INFO ONIX” (@FK0NIXXAII), 18 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/FK0NIXXAII.

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.