Ρ ΠΎΡΠ΅Π½Ρ ΡΡΡΠ°Π» Π±ΠΎΡΡ
π12β€5π4
Signed πΒ°.πππππππΛβ

Channel
@mitsukrol
On this record: Growth Β· Engagement Β· What this channel posts Β· Reactions Β· Stars Β· Posts Β· Citations Β· Cite this entry
224subscribers
-1 since we began measuring on 9 August 2026
Risers and fallers across the register Β· movement among entries of Under 1,000.
| Telegram ID | -1001645284066 |
|---|---|
| Type | Channel |
| Username | @mitsukrol |
| Created | Between 1 December 2021 and 31 March 2023β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 9 August 2026 |
| On Telegram | t.me/mitsukrol |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 18:41 | 224 | -1 |
| 9 Aug 2026, 07:46 | 225 | first reading |
18 posts held, back to 17 April 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 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 18 posts for this entry, the most recent from 13 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 videos 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.
201 reactions across 15 posts, in 6 distinct kinds. The most used accounts for 29.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| π | 60 | 29.9% | |
| β€ | 47 | 23.4% | |
| π | 40 | 19.9% | |
| π | 27 | 13.4% | |
| π | 19 | 9.45% | |
| π | 8 | 3.98% |
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 18 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 201reactions in total: the kind of figure the paragraph above means by βa reaction total printed elsewhere on the pageβ.
Measured over the 18 most recent posts we hold, published 17 April 2026 to 13 July 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 @mitsukrol. 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 18 most recent posts we hold for this entry, published 17 April 2026 to 13 July 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.
Ρ ΠΎΡΠ΅Π½Ρ ΡΡΡΠ°Π» Π±ΠΎΡΡ
π12β€5π4
Signed πΒ°.πππππππΛβ
Π½Π΅ ΡΠΏΡΠ°ΡΠΈΠ²Π°ΠΉΡΠ΅ Ρ ΡΡΠΊΠ°ΡΠ°ΡΠ°Π½ΠΎΠ² ΡΡΠΎ ΠΏΡΠΎΠΈΠ·ΠΎΡΠ»ΠΎ 20 ΠΈΡΠ½Ρ (Π½Π΅ Π·Π½Π°Ρ Π½Π΅ ΡΠΈΡΠ°Π»Π°)
β€4π2
Signed πΒ°.πππππππΛβ
ΠΠ«Π§Π’Π’ΠΠΠΠΠΠ’Ππππ
Signed πΒ°.πππππππΛβ
Β«ΠΌΠ°ΠΌΠ°, Ρ Π΄ΡΠΌΠ°Π» Π²Ρ ΠΏΡΠΎ ΠΌΠ΅Π½Ρ Π·Π°Π±ΡΠ»ΠΈΒ»
π3β€1
Signed πΒ°.πππππππΛβ
ΠΈ Π²ΠΎΡ ΠΎΠ±ΡΠ·Π°ΡΠ΅Π»ΡΠ½ΠΎ Π ΡΠΈ Π²ΠΏΠΈΡ Π½ΡΡΡ Π΄Π°π
π7π1
Signed πΒ°.πππππππΛβ
ΠΎΡ Π±Π»ΠΈΠ½
β€10π8π6π1
Signed πΒ°.πππππππΛβ
Video, posted without a caption
π2
Signed πΒ°.πππππππΛβ
ΡΡΠ°
π8π6π1
Signed πΒ°.πππππππΛβ
Video, posted without a caption
π5π4π1
Signed πΒ°.πππππππΛβ
ΡΡΠΈΠΊΠ°ΡΠ° ΡΠΎΠΆΠΈ Π±ΡΠ΄ΡΡπ₯Ίπ₯Ί
π3π2π1
Signed πΒ°.πππππππΛβ
Ρ Π΄Π½Π΅ΠΌ ΡΠ°Π½Π΄ΠΎΠΌΠ½ΡΡ ΠΏΠ΅ΠΉΡΠΈΠ½Π³ΠΎΠ²
π4π1
Signed πΒ°.πππππππΛβ
Π·Π°Ρ ΠΎΡΠ΅Π»ΠΎΡΡ
π11π5π5
Signed πΒ°.πππππππΛβ
Showing the 12 most recent of 18 posts we hold for @mitsukrol. 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 β 566,774 of 1,160,990entries 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.
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.
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 August 2026 β this entry's latest reading, not the date you are reading this.
βΛβπMΠΈΡΡ!!οΎ:3ΛΒ°β (@mitsukrol), 224 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/mitsukrol.
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.