Channel
@PhNextoyb
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
279subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001869857267 |
|---|---|
| Type | Channel |
| Username | @PhNextoyb |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 2 times, most recently 16 September 2026 |
| On Telegram | t.me/PhNextoyb |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 23 September 2026 and assigned it the closest of 31 fixed categories, at 92% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 15:57 | 279 | +1 |
| 30 Aug 2026, 16:13 | 278 | -3 |
| 24 Aug 2026, 13:35 | 281 | -2 |
| 16 Aug 2026, 05:37 | 283 | +3 |
| 8 Aug 2026, 08:33 | 280 | no change |
| 7 Aug 2026, 14:21 | 280 | first reading |
4 posts held, back to 11 November 2025 — 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 4 posts for this entry, the most recent from 9 January 2026. An engagement rate over an empty window would be a number about nothing.
102 reactions across 4 posts, in 7 distinct kinds. The most used accounts for 26.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5233643359297359199 | 27 | 26.5% | |
| custom 5289722755871162900 | 23 | 22.5% | |
| custom 5309911056372494688 | 18 | 17.6% | |
| custom 5318868949402667784 | 15 | 14.7% | |
| custom 5334987944484686335 | 13 | 12.7% | |
| custom 5195302250670476252 | 5 | 4.90% | |
| custom 5276337494588137957 | 1 | 0.98% |
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 are Telegram’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 4 of the 4 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 102 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 11 November 2025 to 9 January 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.
основной движ в инсте не пропускайте!
custom 53188689494026677848custom 53349879444846863352custom 51953022506704762521custom 52336433592973591991custom 52763374945881379571custom 52897227558711629001
| метро | руки |
custom 523364335929735919919custom 53349879444846863359custom 53188689494026677846custom 53099110563724946884
🔹а теперь немного синих наблюдений
custom 530991105637249468813custom 52897227558711629007custom 52336433592973591994custom 53188689494026677841custom 53349879444846863351
📸 Десять ваших лучших #фотонедели Поздравляю авторов 👏 @Jenya_Gubanova @nextoyb @NSerezhko @KonstantinMatveev @mmmaricat @Maintech710 @mequinte @dmtr1234 @Taty80Lev Светлана Семендяева Вы прислали очень много классных кадров, из которых выбрать 10 было еще тем квестом 😅 Все молодцы, кто поделился своей работой и поучаствовал в этом челлендже! Более широкую выборку можно посмотреть здесь https://annazakharova.ru/fo…
custom 528972275587116290015custom 51953022506704762524custom 52336433592973591993custom 53099110563724946881custom 53349879444846863351
Showing the 4 most recent of 4 posts we hold for @PhNextoyb. 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.
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.
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.
@PhNextoyb named 1 handle 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.
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“Ph: @nextoyb” (@PhNextoyb), 279 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/PhNextoyb.
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.