Channel
@morok_spb
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry
356subscribers
+3 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003750328150 |
|---|---|
| Type | Channel |
| Username | @morok_spb |
| Created | Between 1 February 2026 and 30 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/morok_spb |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 22:36 | 356 | -1 |
| 31 Aug 2026, 01:23 | 357 | -1 |
| 14 Aug 2026, 22:16 | 358 | +5 |
| 6 Aug 2026, 21:17 | 353 | no change |
| 6 Aug 2026, 16:38 | 353 | first reading |
15 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 15 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
192 reactions across 15 posts, in 9 distinct kinds. The most used accounts for 22.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5206471588001651428 | 43 | 22.4% | |
| custom 5307553364140107920 | 32 | 16.7% | |
| custom 5276358174855667647 | 24 | 12.5% | |
| custom 5213035633764744612 | 22 | 11.5% | |
| custom 5341719463907570263 | 22 | 11.5% | |
| custom 5233715377308974887 | 19 | 9.90% | |
| custom 5235551712051214378 | 17 | 8.85% | |
| custom 5249082538365840353 | 10 | 5.21% | |
| custom 5226875792213967400 | 3 | 1.56% |
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 15 of the 15 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 192 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 23 July 2026 to 5 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @morok_spb. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 15 most recent posts we hold for this entry, published 23 July 2026 to 5 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
🌟 🌟⭐️⭐️ 🌟⭐️⭐️⭐️ 🌟⭐️⭐️⭐️ заброшка 36.6: как это было video music: привычка вредить, липс — загоны edit: @eugene_d15 (behance) camera: png 🌚 MOROK
custom 53075533641401079208custom 52130356337647446125custom 52490825383658403531custom 53417194639075702631
⭐️ 🖤 напоминаем, что мы будем помогать в организации вот здесь уже завтра. приходите, будет классно. читайте подробности, ставьте реакции, зовите друзей. ⭐️⭐️ KIRILIK. ⭐️⭐️ 1 августа, 18:30. ⭐️⭐️ клуб 'action', ⭐️⭐️ лиговский пр., 113. ⭐️⭐️ билеты.
custom 52064715880016514285custom 52763581748556676474custom 53417194639075702632
⭐️ ⭐️⭐️⭐️ заброшка 36.6. финиш. ⭐️ мы устали морально и физически – но как же мы довольны. вышло атмосферно, весело, шумно, смешно, красиво, ярко, громко и тепло. спасибо всем, кто к нам пришел, всем, кто участвовал и помогал – ценим каждого. а ещё спасибо бару 'наше место' – место действительно стало нашим и даже больше. ещё услышимся. ⭐️⭐️ пожалуйста, расскажите в комментариях, как вам, скиньте фото и видео. бу…
custom 53075533641401079206custom 52064715880016514283custom 52337153773089748873custom 52355517120512143782custom 53417194639075702632
Wonder Polly Crystals + Технолесье 💎🎁🍄🧚
custom 53075533641401079204custom 52355517120512143783custom 52064715880016514281custom 52130356337647446121
Video message, posted without a caption
custom 52130356337647446125custom 52064715880016514282custom 52355517120512143782custom 53417194639075702632
Video message, posted without a caption
custom 52268757922139674003custom 52763581748556676472custom 52064715880016514281
Video message, posted without a caption
custom 52130356337647446124custom 52064715880016514283custom 52763581748556676472
Video message, posted without a caption
custom 52355517120512143784custom 52763581748556676473custom 52064715880016514282
@DikobRaZo
custom 52064715880016514287custom 53417194639075702635custom 52763581748556676474
@NastyaNissi
custom 52337153773089748874custom 52064715880016514283custom 52490825383658403533custom 52763581748556676473custom 53075533641401079201
у нас тут такая красота, а вы пропускает. или нет? 💕
custom 520647158800165142810custom 53075533641401079206custom 52337153773089748873custom 52763581748556676472
уже началось! @privychkavredit
custom 53417194639075702638custom 52130356337647446122custom 52064715880016514281custom 52763581748556676471
Showing the 12 most recent of 15 posts we hold for @morok_spb. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 17 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.
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“MOROK” (@morok_spb), 356 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/morok_spb.
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.