слишком давно ничо не было
custom 52831494329786904228custom 53706345237740493164custom 53710066225607025723

Channel
@antixiw
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
128subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002158313737 |
|---|---|
| Type | Channel |
| Username | @antixiw |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 9 October 2026 |
| On Telegram | t.me/antixiw |
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 26 September 2026 and assigned it the closest of 31 fixed categories, at 65% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Oct 2026, 05:00 | 128 | -1 |
| 27 Sept 2026, 21:54 | 129 | +1 |
| 13 Sept 2026, 20:21 | 128 | +1 |
| 29 Aug 2026, 10:14 | 127 | -2 |
| 22 Aug 2026, 08:35 | 129 | -2 |
| 15 Aug 2026, 10:07 | 131 | -1 |
| 9 Aug 2026, 00:46 | 132 | no change |
| 7 Aug 2026, 19:33 | 132 | first reading |
7 posts held, back to 25 June 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 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 7 posts for this entry, the most recent from 2 August 2026. An engagement rate over an empty window would be a number about nothing.
100 reactions across 7 posts, in 4 distinct kinds. The most used accounts for 35.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5283149432978690422 | 35 | 35.0% | |
| custom 5371006622560702572 | 35 | 35.0% | |
| custom 5262945447256802532 | 18 | 18.0% | |
| custom 5370634523774049316 | 12 | 12.0% |
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 7 of the 7 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 100 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 25 June 2026 to 2 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.
слишком давно ничо не было
custom 52831494329786904228custom 53706345237740493164custom 53710066225607025723
Photo, posted without a caption
custom 53710066225607025726custom 52629454472568025324custom 52831494329786904222
я не знаю чо выкладывать,у собаки лучше фотки чем у меня📎
custom 52831494329786904226custom 53706345237740493162custom 53710066225607025722custom 52629454472568025321
ОН ТАКОЙ УПОРОТЫШ Я ОРУ
custom 52831494329786904226custom 52629454472568025323custom 53706345237740493163custom 53710066225607025721
мама не вписалась чутка🙄
custom 53710066225607025728custom 52831494329786904224custom 53706345237740493163
зая моя
custom 53710066225607025729custom 52629454472568025326custom 52831494329786904225
потолстела после мака ХВХЫХЫХЫХ
custom 53710066225607025726custom 52629454472568025324custom 52831494329786904224
Showing the 7 most recent of 7 posts we hold for @antixiw. 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.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“𝕞𝕞” (@antixiw), 128 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/antixiw.
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.