Telegram RegisterThe public register of Telegram
Telegram profile photo for Никулина|Фотограф Ростов 📸

Channel

Никулина|Фотограф Ростов 📸

@ph_alya

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

431subscribers

-4 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002128672379
TypeChannel
Username@ph_alya
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live22 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/ph_alya

Growth

4314354337 August 2026 — 435 subscribers7 August 2026 — 434 subscribers8 August 2026 — 434 subscribers14 August 2026 — 432 subscribers22 August 2026 — 431 subscribers7 August 202622 August 2026
5 measurements spanning 15 days, net -4. 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 430–436 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 10:26431-1
14 Aug 2026, 21:08432-2
8 Aug 2026, 05:17434no change
7 Aug 2026, 23:52434-1
7 Aug 2026, 12:10435first reading

Engagement

3 posts held, back to 25 December 2025the 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 3 posts for this entry, the most recent from 17 February 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
2s
Average length
2s

Measured directly from 1 video 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.

Reaction mix

133 reactions across 3 posts, in 6 distinct kinds. The most used accounts for 58.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😍7858.6%
custom 54677859152104202802418.0%
🎉1511.3%
custom 546983324451604518575.26%
🔥53.76%
🥰43.01%

Custom emoji. 2 of the rows above are 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 3 of the 3 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 133reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 3 most recent posts we hold, published 25 December 2025 to 17 February 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.

Recent posts

17 Feb 2026, 10:46 UTC446 views51 reactionsread 8 August 2026
Photo

Привет, 26💓 Встречаю в новом статусе для себя и с благодарностью за все,что было. Дальше будет только лучше 🎈🎉

😍31🎉15🔥5

Signed Алина

2 Jan 2026, 13:48 UTC773 views62 reactionsread 8 August 2026
Photo

Наша большая любовь 💕

😍40custom 546778591521042028011custom 54698332445160451857🥰4

Signed Алина

25 Dec 2025, 15:48 UTC659 views20 reactionsread 8 August 2026
Photo

Женя, Алёна и Катюшка🫶💕

custom 546778591521042028013😍7

Signed Алина

Showing the 3 most recent of 3 posts we hold for @ph_alya. 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.

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

“Никулина|Фотограф Ростов 📸” (@ph_alya), 431 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/ph_alya.

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.