Channel
@kxiha
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Citations · Cite this entry
8,253subscribers
+1,335 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003520803819 |
|---|---|
| Type | Channel |
| Username | @kxiha |
| Description | 收录:车祸监控 意外事故 彻底疯狂 溺水救援 死神来了（快跑） @btlot @qqmua |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/kxiha |
Memes & entertainment — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 53% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 07:16 | 8,253 | +34 |
| 1 Nov 2026, 01:19 | 8,219 | +11 |
| 29 Oct 2026, 10:35 | 8,208 | +33 |
| 26 Oct 2026, 16:36 | 8,175 | +31 |
| 24 Oct 2026, 00:37 | 8,144 | +45 |
| 21 Oct 2026, 01:59 | 8,099 | +39 |
| 18 Oct 2026, 03:09 | 8,060 | +24 |
| 14 Oct 2026, 23:46 | 8,036 | +39 |
| 11 Oct 2026, 18:17 | 7,997 | +83 |
| 5 Oct 2026, 07:20 | 7,914 | +89 |
| 26 Sept 2026, 13:22 | 7,825 | +114 |
| 17 Sept 2026, 06:22 | 7,711 | +71 |
| 13 Sept 2026, 04:19 | 7,640 | +77 |
| 9 Sept 2026, 06:17 | 7,563 | +124 |
| 3 Sept 2026, 12:59 | 7,439 | +49 |
| 31 Aug 2026, 03:29 | 7,390 | +66 |
| 28 Aug 2026, 02:55 | 7,324 | +35 |
| 25 Aug 2026, 05:15 | 7,289 | +30 |
| 22 Aug 2026, 12:06 | 7,259 | +70 |
| 19 Aug 2026, 07:28 | 7,189 | first reading |
139 posts held, back to 5 August 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 18 pages of Telegram’s post history, 20 posts per page.
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 6 of 46 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 5 November 2026 |
|---|---|
| Posts held | 139 (5 August 2026 – 5 November 2026) |
| Views total | 4,092 |
| Reactions total | 6 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 5 Nov 2026, 11:17 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.
Lifetime counters from Telegram’s own channel header, read 5 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 109 videos 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.
13 reactions across 12 posts, in 4 distinct kinds. The most used accounts for 38.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 5 | 38.5% | |
| 👍 | 5 | 38.5% | |
| 😱 | 2 | 15.4% | |
| 😨 | 1 | 7.69% |
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 13 of the 139 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 13 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 139 most recent posts we hold, published 5 August 2026 to 5 November 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.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
Measured over the 139 most recent posts we hold, published 5 August 2026 to 5 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Telegram’s own ‘edited’ marker: 0 of 46 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
拉特尔：一则爆炸事件撼动了拉特尔市。爆炸发生在维拉施拉奥·德什穆克路上，当时一名快递员正在从一辆快递车上卸货。爆炸导致一名快递公司员工严重受伤。监控录像显示，在将箱子从车上卸下时，突然发生了一次巨大的爆炸。该工人伤势严重，已被送往医院，目前情况危急。拉特尔警方、排爆小组和法医团队在事发后不久抵达现场，并展开联合调查，以确定爆炸原因。初步报告显示，爆炸发生在卸货过程中，这表明箱子可能包含爆炸物。#爆炸 @qqmua
缅甸人民国防军（PDF）抵抗力量突袭警察局
#火疗 #头发着火 🤣 #技师 有点东西哦
马片 第一次看马的鸡儿，真大！ #马 #交配
#外卖员 #搞破坏 多大仇 ？
民主党人今天醒来就像这样
中国航天就是屌 👍
👍1
谢谢群主送的超长蛋挞，收到货了，非常大根本吃不完，想要的群友可以私信群主领取。
👍1
也不是买不起，这样穿起来比较凉快 内裤烂了
👍1
#女性力量 #女人打架 撕逼大战
👍1
#摩托 #车祸 🥲
👍1
年纪轻轻，就拥有自动驾驶代步工具了😁 #猫猫头 扫地机器人
Showing the 12 most recent of 139 posts we hold for @kxiha. 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.
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.
Named by 16 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.
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.
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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“超级现场🚷意外|车祸|监控” (@kxiha), 8,253 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/kxiha.
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.