Telegram RegisterThe public register of Telegram

Channel

Kenway Playground

@kenwayplayground

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

1,268subscribers

+6 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002535677072
TypeChannel
Username@kenwayplayground
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/kenwayplayground

Growth

1,2621,2681,2656 August 2026 — 1,262 subscribers6 August 2026 — 1,262 subscribers9 August 2026 — 1,264 subscribers13 August 2026 — 1,268 subscribers6 August 202613 August 2026
4 measurements spanning 7 days, net +6. 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 1,261–1,269 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 00:251,268+4
9 Aug 2026, 17:021,264+2
6 Aug 2026, 08:151,262no change
6 Aug 2026, 04:171,262first reading

Engagement

15 posts held, back to 26 July 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
50.9%
avg views ÷ 1,268 subscribers
Avg views / post
646
14 posts measured
Reaction rate
4.06%
reactions ÷ views · ER floor
Posts in window
15
of 15 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. It is computed over the 13 of 14 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 5 August 2026
Posts held15 (26 July 20265 August 2026)
Views total9,038
Reactions total343
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 08:15 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.

Recent posts

3 Aug 2026, 16:31 UTC≈633 views19 reactionsread 6 August 2026

https://artifacts.serverhive.in/?id=vos-ascp-peridot-20260803-162646281295

3 Aug 2026, 08:54 UTC≈612 views29 reactionsread 6 August 2026

Now both type of users will be happy... Use whatever you want..let the kernel handle everything

2 Aug 2026, 17:25 UTC≈648 views33 reactionsread 6 August 2026

A big thanks to all testers for testing.. I know still many people asking I didn't managed to send build to all. Already have quite a number of testers really.. will release soon tonight (maybe late) if you didn't get beta build. Thank you

2 Aug 2026, 17:24 UTC≈658 views28 reactionsread 6 August 2026
Photo

Also one more update to native bypass charging fully managed from kernel .. with all testers now I'm certain its perfect.

2 Aug 2026, 17:20 UTC≈651 views32 reactionsread 6 August 2026
Photo

currently working on a new solution for thermal management.. while xiaomi slow fast superfast not doing anything really.. if limit it thermal profile not very good. Some wants high charging speed without temp worries but some prefer same charging while device cool. Acca or other battery manager apps not doing anything properly.. so this is best solution for .. fully managed by kernel we just change node value to cha

Showing the 12 most recent of 15 posts we hold for @kenwayplayground. 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 — 614,362 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.

Mentions

Named by 2 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.

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.

“Kenway Playground” (@kenwayplayground), 1,268 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/kenwayplayground.

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.