Telegram RegisterThe public register of Telegram
Telegram profile photo for Актерский МАркет

Channel

Актерский МАркет

@MArketchbbfan

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

82subscribers

-13 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-1003175665607
TypeChannel
Username@MArketchbbfan
DescriptionЛЮБОЙ МАТЕРИАЛ С КАНАЛА, ВКЛЮЧАЯ ИДЕИ ВИДЕО МОЖНО БРАТЬ ТОЛЬКО С ОТМЕТКОЙ Фан Елены и команды авторов сп Владельц - Мальвина Админы - Алиска(ст) и Арина(мл) @MArketchbbbot Анон бот Начало 09.11.2025
CreatedBetween 1 September 2025 and 30 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 October 2026
Last confirmed live10 October 2026
Measurements held7
On Telegramt.me/MArketchbbfan

Growth

829588.57 August 2026 — 95 subscribers15 August 2026 — 92 subscribers22 August 2026 — 89 subscribers29 August 2026 — 86 subscribers7 September 2026 — 85 subscribers14 September 2026 — 82 subscribers10 October 2026 — 82 subscribers7 August 202610 October 2026
7 measurements spanning 64 days, net -13. 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 80–97 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Oct 2026, 13:2482no change
14 Sept 2026, 15:3982-3
7 Sept 2026, 10:5685-1
29 Aug 2026, 13:1786-3
22 Aug 2026, 01:5889-3
15 Aug 2026, 05:2892-3
7 Aug 2026, 18:5395first reading

Engagement

20 posts held, back to 14 August 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.

ERR · 30 days
14.6%
avg views ÷ 82 subscribers
Avg views / post
12.0
1 post measured
Reaction rate
8.33%
reactions ÷ views · ER floor
Posts in window
1
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 29 September 2026
Posts held20 (14 August 2026 – 29 September 2026)
Views total12
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Oct 2026, 13:24 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
987
Videos
129
Links
320

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

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5224609587079974433133.3%
custom 5226517965603638034133.3%
custom 5474565740130497583133.3%

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

Measured over the 20 most recent posts we hold, published 14 August 2026 to 29 September 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

29 Sept 2026, 17:43 UTC12 views1 reactionsread 10 October 2026
Forwarded from @grimchroniclesPhoto

МАСШТАБНЫЙ КОНКУРС В ЧЕСТЬ ПРЕДСТОЯЩЕГО ХЭЛЛОУИНА Условие для участия: переслать этот конкурс 3 друзьям, или в тгк (от 30 подписчиков). Условия будут проверяться. Скрины пересылки под пост ниже. Итоги будут подведены 31 октября в 15:00 по мск при условии, что количество участников превысит 50. Желаю всем удачи! С любовью, команда мрачных хроник. 🖤

custom 54745657401304975831

10 Sept 2026, 12:25 UTC19 viewsread 10 October 2026
Forwarded from @elenaraytmanPhoto

СТРАШНАЯ ПЕРЕПИСКА | ДОМ ЗА ЛЕСОМ 11 Часть https://youtu.be/G9eaN7yNwj8

18 Aug 2026, 11:07 UTC47 viewsread 10 October 2026

🌟 моя как раз ест тот корм что не ест рэйс

18 Aug 2026, 08:41 UTC46 viewsread 10 October 2026

какой умничка!! все быстро схватывает, молодечик на счет корма с моим Зевсом у нас было две проблемы 1 размер кусочков был слишком большой, ему было неудобно есть но тут сразу отпадает, тк на кружочке как лена показала кусочки маленькие 2 ему может не нравится вкус корма. мой не ест корм с лососем, может рэйсу тоже не нравится вкус того корма

18 Aug 2026, 08:39 UTC22 viewsread 10 October 2026
Forwarded from @elenaraytmanVideo message

Video message, posted without a caption

18 Aug 2026, 08:39 UTC20 viewsread 10 October 2026
Forwarded from @elenaraytmanVideo message

Video message, posted without a caption

17 Aug 2026, 19:37 UTC26 viewsread 10 October 2026

нам просто нужно было вывести криса из комы🐈

17 Aug 2026, 19:37 UTC20 viewsread 10 October 2026
Forwarded from @nighttyped

Артур: Что там с Крисом? X: Он в глубокой коме. Мы полностью подавили его волю, как и задумывали. На слиянии сопротивления не будет, сосуд открыт для хозяина. Артур: Хорошо. Начинайте призыв. Саргат должен забрать его тело прежде, чем Крис очнётся. X: Ритуал уже начался. Артур: Он будет нами доволен. X: Думаешь? Артур: Считаешь Крис не выдержит? X: Крис выдержит, его с детства к этому готовили. Но ты же понима…

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

Forward network

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.

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

“Актерский МАркет” (@MArketchbbfan), 82 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/MArketchbbfan.

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.