Channel
@nexxfor
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
202subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001960911269 |
|---|---|
| Type | Channel |
| Username | @nexxfor |
| Description | не[кс]форы и их приключения контакты для связи:@kinnkilsp / @mi_re_ni |
| Created | 10 May 2023 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/nexxfor |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 11:20 | 202 | no change |
| 7 Aug 2026, 19:56 | 202 | first reading |
6 posts held, back to 7 June 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 6 posts for this entry, the most recent from 19 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 8 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.
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.
108 reactions across 6 posts, in 8 distinct kinds. The most used accounts for 21.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 6287203406851345941 | 23 | 21.3% | |
| custom 5769531913492501246 | 21 | 19.4% | |
| custom 6176860023365308473 | 17 | 15.7% | |
| custom 6176731217296100707 | 16 | 14.8% | |
| custom 6141004261988765126 | 14 | 13.0% | |
| custom 6176883113109491086 | 7 | 6.48% | |
| custom 5767279005577254220 | 6 | 5.56% | |
| custom 5767413455233488146 | 4 | 3.70% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.
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 6 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 108reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 7 June 2026 to 19 June 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.
★ вот и вторая порция фотографий с рандома! выражаем всем ребятам, что посетили наше мероприятие, а также благодарность за ожидание. https://disk.yandex.ru/d/7-tZCXjas1qDhA #нексфор#нефор#рандом2026
custom 57695319134925012464custom 61768600233653084734custom 57672790055772542203
🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 и вновь на связи нексфор! 🤍недавно прошел долгожданный рандом. ✨хотим сказать вам большое спасибо!✨ 🤍рандом проходил в домашней обстановке, не без трудностей и непредвиденных обстоятельств, но мы надеемся, что всем понравилось так же, как и нашей команде! 🤍 🎀в этот раз наше мероприятие вышло на новый уровень, хотим выразить огромную благодарность за поддержку и иницитиву каждому человеку, что смог пос…
custom 62872034068513459418custom 61410042619887651267custom 61768600233653084736custom 57674134552334881463custom 57695319134925012461
Сегодня (точнее уже вчера) наша Sunday #rehearsal прошла в таком красивом Японском формате (благодаря команде NEX4R)🐉❤️ Можете теперь рассмотреть вчерашние спойлеры более подробно :) Так вот, подобные мероприятия это всегда про возможность нарядиться, выступить и покайфовать от красивой атмосферы✨ А мы такое любим) В этот раз свои выступления показали: ❤️DANIELL & KONAN (дуэт под “REDRED” by CORTIS) ❤️MOORNEDD (с…
custom 62872034068513459415custom 57695319134925012462custom 61767312172961007072custom 61768600233653084732custom 57672790055772542201custom 57674134552334881461custom 61768831131094910861
⭐и вновь на связи нексфор! 🎀хотим поблагодарить всех кто пришел на мероприятие!😘 🤲🤲🤲🤲🤲🤲🤲🤲🤲🤲 🌟мы были рады видеть ваши выступления, вовлеченность во время мероприятия и чувствовать поддержку и теплоту от всех, кто пришел повеселиться и провести это время вместе с нами🌟 так же приносим извинения за внезапные технические шоколадки🤩
custom 61768831131094910866custom 57695319134925012465custom 61410042619887651265
🤩Сегодня в этот по-настоящему жаркий день мы побывали на мероприятие от @nexxfor. Ритмы, движение, музыка, свет, свое пространство и полное отключение головы от рабочих чатов хотя бы на пару часов. Компания собралась своя, своя в хорошем смысле. Атмосфера — живая, расслабленная, но при этом жаркая. Без пафоса, без напряжения, без этого вот всего «как положено». И знаете что? Это тот случай, когда люди не смотрят на …
custom 57695319134925012467custom 61767312172961007077custom 62872034068513459415custom 57672790055772542202custom 61410042619887651261custom 61768600233653084731
🌟🤩#mixten_party🌟🌟 🤩В этот летний день мы шагнули в мир древней Азии на мероприятии от NEX4R! 🤩К сожалению, прийти смогли только : утончённая Мун, якудза Айми и пикми Энди, но мы повеселились за всю команду🐉 🤩Атмосфера захватила с первых минут, а каждое выступление поразило своей красотой. Огромное спасибо за такой невероятный день!🤩
custom 61767312172961007077custom 62872034068513459415custom 61768600233653084734custom 57695319134925012462custom 61410042619887651261
Showing the 6 most recent of 6 posts we hold for @nexxfor. 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 — 158,881 of 1,481,217entries 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 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.
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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“NEX4R” (@nexxfor), 202 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/nexxfor.
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.