Telegram RegisterThe public register of Telegram
Telegram profile photo for Xyeta

Channel

Xyeta

@xyeta66

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

331subscribers

-21 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001813177085
TypeChannel
Username@xyeta66
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live1 October 2026
Measurements held9
Confirmed unchanged1 time, most recently 1 October 2026
On Telegramt.me/xyeta66

Topic

Personal blog — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 22 September 2026 and assigned it the closest of 31 fixed categories, at 56% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

331352341.57 August 2026 — 352 subscribers8 August 2026 — 352 subscribers8 August 2026 — 351 subscribers16 August 2026 — 349 subscribers23 August 2026 — 345 subscribers30 August 2026 — 344 subscribers9 September 2026 — 343 subscribers17 September 2026 — 340 subscribers1 October 2026 — 331 subscribers7 August 20261 October 2026
9 measurements spanning 55 days, net -21. 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 328–355 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Oct 2026, 10:18331-9
17 Sept 2026, 10:39340-3
9 Sept 2026, 12:01343-1
30 Aug 2026, 21:02344-1
23 Aug 2026, 14:57345-4
16 Aug 2026, 18:35349-2
8 Aug 2026, 12:33351-1
8 Aug 2026, 06:47352no change
7 Aug 2026, 12:16352first reading

Engagement

17 posts held, back to 24 May 2025 — 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 17 posts for this entry, the most recent from 15 February 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

464 reactions across 16 posts, in 3 distinct kinds. The most used accounts for 42.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 526252280100004322019942.9%
custom 526277745390599017817136.9%
custom 54341212528747564569420.3%

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

Measured over the 17 most recent posts we hold, published 24 May 2025 to 15 February 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

15 Feb 2026, 04:24 UTC457 views37 reactionsread 8 August 2026
Photo

У него сегодня день рождения!! 2 года уже

custom 526252280100004322018custom 526277745390599017810custom 54341212528747564569

26 Dec 2025, 07:41 UTC606 views31 reactionsread 8 August 2026
Photo

Ты мне скажи норм фотка или нет я чета нихуя не понимаю

custom 526277745390599017812custom 526252280100004322010custom 54341212528747564569

12 Dec 2025, 17:45 UTC522 views24 reactionsread 8 August 2026
Photo

Photo, posted without a caption

custom 526277745390599017810custom 52625228010000432208custom 54341212528747564566

23 Nov 2025, 05:06 UTC570 views19 reactionsread 8 August 2026
Photo

ходил за сухариками(щас дома уже)

custom 52625228010000432209custom 52627774539059901789custom 54341212528747564561

7 Nov 2025, 21:27 UTC698 views9 reactionsread 8 August 2026
Photo

Photo, posted without a caption

custom 52627774539059901785custom 52625228010000432203custom 54341212528747564561

6 Nov 2025, 08:12 UTC582 views18 reactionsread 8 August 2026
Photo

Photo, posted without a caption

custom 52627774539059901789custom 52625228010000432208custom 54341212528747564561

5 Nov 2025, 07:51 UTC555 views20 reactionsread 8 August 2026
Photo

я червяк 👹

custom 526277745390599017813custom 52625228010000432206custom 54341212528747564561

9 Oct 2025, 05:48 UTC715 views12 reactionsread 8 August 2026
Photo

хватит с меня кса

custom 52625228010000432208custom 52627774539059901783custom 54341212528747564561

14 Sept 2025, 06:53 UTC890 views16 reactionsread 8 August 2026

комп сгорел)

custom 526277745390599017810custom 52625228010000432205custom 54341212528747564561

4 Sept 2025, 20:33 UTC≈1,070 views25 reactionsread 8 August 2026

бля хочу себе блекворк на шею

custom 526277745390599017812custom 52625228010000432207custom 54341212528747564566

6 Aug 2025, 00:05 UTC≈1,420 views36 reactionsread 8 August 2026
Photo

Photo, posted without a caption

custom 526277745390599017815custom 543412125287475645611custom 526252280100004322010

3 Aug 2025, 13:18 UTC≈1,230 views29 reactionsread 8 August 2026
Photo

🤩🤩🤩

custom 526252280100004322021custom 52627774539059901787custom 54341212528747564561

Showing the 12 most recent of 17 posts we hold for @xyeta66. 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.

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

“Xyeta” (@xyeta66), 331 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/xyeta66.

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.