Telegram RegisterThe public register of Telegram

Channel

⊹─ luk_folow ˙˙˙ᶜᵒˢᵖˡᵃʸ'⁶⁴⁷

@mawykai

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

476subscribers

-2 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-1001891015134
TypeChannel
Username@mawykai
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/mawykai

Growth

4764784776 August 2026 — 478 subscribers7 August 2026 — 478 subscribers13 August 2026 — 476 subscribers6 August 202613 August 2026
3 measurements spanning 7 days, net -2. 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 476–478 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 15:36476-2
7 Aug 2026, 08:24478no change
6 Aug 2026, 23:32478first reading

Engagement

12 posts held, back to 4 August 2026the 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.

ERR · 30 days
22.7%
avg views ÷ 476 subscribers
Avg views / post
108
11 posts measured
Reaction rate
14.2%
reactions ÷ views · ER floor
Posts in window
12
of 12 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 6 August 2026
Posts held12 (4 August 20266 August 2026)
Views total1,189
Reactions total169
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 23:32 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.

Reaction mix

169 reactions across 11 posts, in 8 distinct kinds. The most used accounts for 23.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54586400615264720424023.7%
custom 54587488702279476173822.5%
custom 54586772903029924473218.9%
custom 54584941829622639933118.3%
custom 5325784057202636611169.47%
custom 542689308061364557895.33%
custom 542468612455349877021.18%
custom 542737229158969764310.592%

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

Measured over the 12 most recent posts we hold, published 4 August 2026 to 6 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.

Recent posts

6 Aug 2026, 21:11 UTC35 views8 reactionsread 6 August 2026

нет, я отказываюсь работать, моя гофре плойка просто ужасная.

custom 54584941829622639935custom 54586772903029924473

Signed мαƒ #johnjane

6 Aug 2026, 21:02 UTC41 views10 reactionsread 6 August 2026
Photo

два одинаковых фото. я возвращаюсь немного в строй. скоро я выставлю ещё коспы на продажу, тк мне нужно копить на кое какого оборванца.✍️✍️

custom 54586400615264720427custom 54586772903029924472custom 54584941829622639931

Signed мαƒ #johnjane

6 Aug 2026, 15:02 UTC81 views16 reactionsread 6 August 2026

поактивнее тапаем кошечку и я закину вам вторую

custom 54584941829622639937custom 54586772903029924475custom 54586400615264720424

Signed мαƒ #johnjane

6 Aug 2026, 13:52 UTC73 views2 reactionsread 6 August 2026
Forwarded from @cosnene

https://t.me/cosplaypermlove впервые вижу чтобы что-то подобное было у нашего города . . . зачастую мне надоела вся эта морока с подслушками и оскорблениями людей 😔 захотелось сделать что-то, куда людям будет приятно заходить хотелось бы попросить пермских ребят распространить данный тгк

custom 54587488702279476172

Signed мαƒ #johnjane

6 Aug 2026, 12:26 UTC67 views2 reactionsread 6 August 2026
Forwarded from @cosplaypermlove

Ринкан💋 #тейк

custom 54586400615264720422

Signed мαƒ #johnjane

4 Aug 2026, 22:20 UTC114 views14 reactionsread 6 August 2026

я презираю тимейтов, которые просто стоят и не помогают команде. говорится именно про тех кто может защищать.. 🤩

custom 53257840572026366118custom 54586772903029924473custom 54584941829622639931custom 54586400615264720421custom 54587488702279476171

Signed мαƒ #johnjane

4 Aug 2026, 21:35 UTC116 views10 reactionsread 6 August 2026

не удивляйтесь качеству. я регресс, просто снято давно было.🙊🙊

custom 54584941829622639937custom 53257840572026366111custom 54586400615264720421custom 54587488702279476171

Signed мαƒ #johnjane

4 Aug 2026, 21:35 UTC338 views69 reactionsread 6 August 2026
Photo

🫙💙💙💙💙💙🫙 🫙🫙🫙🫙🫙 🫙 — Нᴇ ᴄʍᴏᴛᴩи ᴛᴀᴋ ᴄᴇᴩьёɜнᴏ - я ʙᴄᴇᴦᴏ ᴧиɯь ʙɜяᴧᴀ ᴛᴏ, чᴛᴏ ᴄᴀʍᴏ ᴨᴩᴏᴄиᴧᴏ ʍᴇня ɜᴀбᴩᴀᴛь! 🫙🫙🫙🫙🫙 🫐🫐🫐 🌸 рт, реакты, коммы??🫙

custom 545874887022794761730custom 545864006152647204217custom 545867729030299244715custom 54584941829622639934custom 53257840572026366113

Signed мαƒ #johnjane

4 Aug 2026, 21:34 UTC102 views16 reactionsread 6 August 2026

чистка прошла, появились новые реакты, значит...✅✅

custom 54586400615264720426custom 54587488702279476174custom 54584941829622639933custom 54586772903029924472custom 53257840572026366111

Signed мαƒ #johnjane

4 Aug 2026, 21:19 UTC108 views14 reactionsread 6 August 2026
Photo

шёл 10 час в форсакене. я выйграла свою вторую катку за убийцу. там ползёт моя красивая джейн. продолжаю прокачивать себе шеда за брайтайс, живу очень счастлива. так же продумываю как делать косплей на джейн и сколько уйдёт.🤩 (у меня будет ручной гашарпун и гость666)

custom 54268930806136455785custom 53257840572026366113custom 54584941829622639933custom 54586400615264720422custom 54586772903029924471

Signed мαƒ #johnjane

4 Aug 2026, 17:25 UTC114 views8 reactionsread 6 August 2026
Video

ᝰ.ᐟ ⲙιkᥲᥒ t᥉ᥙⲙιkι ᝰ.ᐟ Наконец то руки поднялись сделать ее! Я поняла что ето самый мой любимый косплей из всех ⋆˚🐾˖° ᯤ легкое напоминание что у меня есть тик ток! ̤̮ ~ (Там контент выходит раньше) ⌞ ⌝ ⛧°。 ⋆༺♱༻⋆。 °⛧

custom 54268930806136455784custom 54246861245534987702custom 54273722915896976431custom 54586772903029924471

Signed мαƒ #johnjane

Showing the 12 most recent of 12 posts we hold for @mawykai. 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 — 437,216 of 1,340,412entries 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

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 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.

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

“⊹─ luk_folow ˙˙˙ᶜᵒˢᵖˡᵃʸ'⁶⁴⁷” (@mawykai), 476 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/mawykai.

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.