Telegram RegisterThe public register of Telegram
Telegram profile photo for ksenshi

Channel

ksenshi

@ksenshiiii

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

274subscribers

+2 since we began measuring on 9 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001608765901
TypeChannel
Username@ksenshiiii
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live18 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/ksenshiiii

Growth

2702762739 August 2026 — 272 subscribers10 August 2026 — 272 subscribers17 August 2026 — 271 subscribers25 August 2026 — 270 subscribers1 September 2026 — 276 subscribers11 September 2026 — 273 subscribers18 September 2026 — 274 subscribers2749 August 202618 September 2026
7 measurements spanning 41 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 269–277 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 22:40274+1
11 Sept 2026, 10:18273-3
1 Sept 2026, 16:02276+6
25 Aug 2026, 02:36270-1
17 Aug 2026, 18:08271-1
10 Aug 2026, 03:20272no change
9 Aug 2026, 10:17272first reading

Engagement

8 posts held, back to 30 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 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 8 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
5s
Average length
5s

Measured directly from 1 video 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.

Reaction mix

167 reactions across 8 posts, in 6 distinct kinds. The most used accounts for 35.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54385062598651670195935.3%
custom 54745271713241712413521.0%
custom 54384065650842966133018.0%
custom 54179001492402534222313.8%
custom 5417883295788586160137.78%
custom 527146794227231657874.19%

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

Measured over the 8 most recent posts we hold, published 30 July 2026 to 8 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

8 Aug 2026, 12:00 UTC72 views9 reactionsread 9 August 2026
Forwarded from @gloom_event

Posted without readable text

custom 52714679422723165784custom 54178832957885861603custom 54384065650842966132

8 Aug 2026, 11:42 UTC102 views10 reactionsread 9 August 2026
Photo

Photo, posted without a caption

custom 54384065650842966136custom 54385062598651670192custom 54745271713241712412

5 Aug 2026, 20:29 UTC170 views21 reactionsread 9 August 2026
Photo

собирали сегодня с девочками бусики и браслетики 🌎 low cortisol vibes и даже жара страшнючая нам не помешала

custom 543850625986516701910custom 54745271713241712417custom 54384065650842966133custom 52714679422723165781

3 Aug 2026, 21:22 UTC227 views27 reactionsread 9 August 2026
Photo

Photo, posted without a caption

custom 54385062598651670198custom 54179001492402534227custom 54745271713241712417custom 54384065650842966133custom 52714679422723165782

2 Aug 2026, 17:51 UTC249 views17 reactionsread 9 August 2026
Photo

Photo, posted without a caption

custom 54179001492402534229custom 54178832957885861605custom 54745271713241712413

31 Jul 2026, 13:41 UTC290 views24 reactionsread 9 August 2026
Video

purple rain

custom 543850625986516701916custom 54178832957885861605custom 54745271713241712413

30 Jul 2026, 20:16 UTC289 views36 reactionsread 9 August 2026
Photo

Photo, posted without a caption

custom 547452717132417124113custom 543850625986516701912custom 54384065650842966138custom 54179001492402534223

30 Jul 2026, 13:53 UTC274 views23 reactionsread 9 August 2026
Photo

прогулка в июле в шапке и куртке ощущается очень странно + прогулка после трех дней с температурой под 39 ощущается очень странно + прогулка с контуженной головой после сотряса ощущается очень странно

custom 543850625986516701911custom 54384065650842966138custom 54179001492402534224

Showing the 8 most recent of 8 posts we hold for @ksenshiiii. 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.

Forward network

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.

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

“ksenshi” (@ksenshiiii), 274 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/ksenshiiii.

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.