Telegram RegisterThe public register of Telegram

Channel

marksemibratov фотографер

@mark_semibratov

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

330subscribers

+0 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-1001509874215
TypeChannel
Username@mark_semibratov
Description@marksemibratov
CreatedBetween 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live7 August 2026
Measurements held2
On Telegramt.me/mark_semibratov

Growth

3306 Aug 2026, 19:51 — 330 subscribers6 Aug 2026, 21:47 — 330 subscribers6 Aug 2026, 19:516 Aug 2026, 21:47
2 measurements taken within a single day. 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 329–331 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Aug 2026, 21:47330no change
6 Aug 2026, 19:51330first reading

Engagement

3 posts held, back to 26 August 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 9 October 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
726
Videos
17
Links
52

Lifetime counters from Telegram’s own channel header, read 6 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.

Reaction mix

80 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 52.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53075856107545650614252.5%
custom 53079658442092777503847.5%

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 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 80reactions 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 26 August 2025 to 9 October 2025, 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

9 Oct 2025, 16:07 UTC433 views28 reactionsread 6 August 2026
Photo

@xrustalic

custom 530796584420927775017custom 530758561075456506111

16 Sept 2025, 12:45 UTC665 views32 reactionsread 6 August 2026
Forwarded from @okkomoviesPhoto

🔥 ОСТОРОЖНО, ВЫСОКОЕ НАПРЯЖЕНИЕ 🔥 Звезда сериала «ЛИХИЕ» Егор Кенжаметов — в новом фотосете специально для Okko. В сериале Юрия Быкова актёр сыграл молодого Лиховцева, который ещё ребёнком попадает в криминал и совершает ужасные вещи. Жертвы приходят в ночных кошмарах, а постоянная рефлексия сводит с ума. Читайте интервью Егора Кенжаметова для Okkoлокино — о железобетонных мужиках, узнаваемости и главной мечте. 📸

custom 530758561075456506122custom 530796584420927775010

26 Aug 2025, 16:14 UTC535 views20 reactionsread 6 August 2026
Forwarded from @csskatanaPhoto

🩸✨marksemibratov

custom 530796584420927775011custom 53075856107545650619

Showing the 3 most recent of 3 posts we hold for @mark_semibratov. 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 — 854,997 of 1,169,250entries 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.

Forward network

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.

Mentions

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

“marksemibratov фотографер” (@mark_semibratov), 330 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/mark_semibratov.

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.