Channel
@monstark8
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
398subscribers
-5 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002015489837 |
|---|---|
| Type | Channel |
| Username | @monstark8 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 2 times, most recently 19 September 2026 |
| On Telegram | t.me/monstark8 |
Gaming — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 29% 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 |
|---|---|---|
| 12 Sept 2026, 00:35 | 398 | -1 |
| 4 Sept 2026, 04:00 | 399 | -3 |
| 21 Aug 2026, 03:43 | 402 | +3 |
| 15 Aug 2026, 02:07 | 399 | -2 |
| 8 Aug 2026, 14:44 | 401 | -2 |
| 8 Aug 2026, 05:47 | 403 | no change |
| 7 Aug 2026, 18:39 | 403 | first reading |
9 posts held, back to 23 July 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 9 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
230 reactions across 9 posts, in 8 distinct kinds. The most used accounts for 38.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5350702035819833989 | 88 | 38.3% | |
| custom 5373310043586310463 | 78 | 33.9% | |
| 😍 | 50 | 21.7% | |
| ⚡ | 4 | 1.74% | |
| 👾 | 4 | 1.74% | |
| 😈 | 4 | 1.74% | |
| 🎉 | 1 | 0.435% | |
| 💯 | 1 | 0.435% |
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 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 9 of the 9 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 230 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 23 July 2026 to 7 August 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.
У меня иногда недалеко от дома стоит прям салатовый мустанг, я каждый раз хожу и хочу оставить владельцу записку, что я очень хочу фотосет с его машиной 😂 Но когда его вижу, при мне нету бумажки и ручки! А у меня не закрытый гештальт с фотосетом с машиной, так как единственный, который был в жизни, я не увидела фоток так как это была коммерция и я без понятия куда она пошла 😅
😍6
С пятницей всех! Фотограф Каяна И ее прекрасный мотоцикл #фотосеты@monstark8
custom 53507020358198339899😍6custom 53733100435863104636
На фотосеты много планов, но времени будет поменьше. Так что теперь буду жонглировать временем :) Крафта дома выше крыши делать. Визажистом все так же работаю, но больше по вечерам теперь и определенные дни только доступны. Человеческие выходные очень редко выпадать будут. Фотограф Каяна Обе съемки мы с ней сделали с промежутком 2-3 месяца 😁 #фотосеты@monstark8
😍10custom 53507020358198339894custom 53733100435863104632⚡1🎉1
Video message, posted without a caption
😍12custom 53507020358198339895custom 53733100435863104632
У меня сейчас будет достаточно молчаливый месяц, хоть и буду стараться выложить, что имею. Я сейчас закончу обучение на новой работе и месяц буду привыкать к ночному графику 3/3. И вообще посмотреть как у меня идёт. Думаю послезавтра утром расскажу в кружочке, чему учусь и где стажируюсь :) Там как раз самостоятельный день. Фотограф Каяна #фотосеты@monstark8
custom 537331004358631046317custom 53507020358198339896😍5😈4
Мой мужчина собирает красивые украшения как у меня на шее 🥰 https://t.me/Luxe_in_Tenebris666 Можно купить любой кулон и он соберёт вам его красиво! Фотограф Каяна #фотосеты@monstark8
custom 53733100435863104639custom 53507020358198339897😍6
Ну что, расчехлили зонтики?☔️ Фотограф Каяна #фотосеты@monstark8
custom 535070203581983398921custom 537331004358631046312👾4
Rock and Ride 🤟🔥 Пока выкладывала фотосет с мотоциклом, вспомнила что Мыш Рокера свою не доделала. Фотки остались только плохого качества, так что подтягиваю в телефоне как могу под немного старину, что бы скрыть плохое качество 😂 А я тогда поехала в Воронеж, мне нашли идеальный байк и девушку фаерщика пригласили 🥹 Последнее фото еле нашла тоже в инсте, в свое время заказывала у Николая Жарова обработку, но все ра…
custom 535070203581983398920custom 537331004358631046314😍5💯1
Я уже путаюсь конечно, что я выложила, что нет. Так что, ну упс, если будет, что то повторятся))) Фотограф Каяна #фотосеты@monstark8
custom 535070203581983398916custom 537331004358631046316⚡3
Showing the 9 most recent of 9 posts we hold for @monstark8. 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.
Named by 1 registered channel — 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.
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.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“K8Stark Визажист/Модель 🔞” (@monstark8), 398 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/monstark8.
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.