National news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 9 August 2026 and assigned it the closest of 31 fixed categories, at 88% 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.
Growth
56 measurements spanning 89 days, net +26,458. 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 120,647–179,682 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 56
Measured (UTC)
Subscribers
Change
4 Nov 2026, 18:47
172,870
+11,738
3 Nov 2026, 16:05
161,132
+14,109
2 Nov 2026, 13:46
147,023
+6,490
1 Nov 2026, 10:36
140,533
-1,825
31 Oct 2026, 07:14
142,358
-2,416
30 Oct 2026, 08:29
144,774
-1,978
29 Oct 2026, 08:59
146,752
+12,531
28 Oct 2026, 08:27
134,221
+2,892
27 Oct 2026, 04:50
131,329
-2,573
26 Oct 2026, 02:01
133,902
-2,075
25 Oct 2026, 00:35
135,977
-1,770
23 Oct 2026, 23:49
137,747
-2,195
23 Oct 2026, 03:08
139,942
-1,708
22 Oct 2026, 04:07
141,650
+1,010
20 Oct 2026, 22:59
140,640
+13,181
19 Oct 2026, 18:28
127,459
-918
18 Oct 2026, 20:11
128,377
-1,642
17 Oct 2026, 20:20
130,019
-2,497
16 Oct 2026, 17:37
132,516
-1,536
15 Oct 2026, 19:49
134,052
first reading
Engagement
2,739 posts held, back to 7 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 180 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
2.70%
avg views ÷ 172,870 subscribers
Avg views / post
4,660
955 posts measured
Reaction rate
1.58%
reactions ÷ views · ER floor
Posts in window
955
of 2,739 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 946 of 955 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 4 November 2026
Posts held
2,739 (7 August 2026 – 4 November 2026)
Views total
4,452,743
Reactions total
69,977
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
4 Nov 2026, 15:21 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.
What this channel posts
Video runtime
3h 41m
Average length
2m 08s
Measured directly from 104 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.
Reaction mix
72,351 reactions across 990 posts, in 11 distinct kinds. The most used accounts for 18.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
13,621
18.8%
❤
13,370
18.5%
🔥
13,345
18.4%
🎉
13,305
18.4%
😁
10,734
14.8%
👏
2,695
3.72%
🥰
2,638
3.65%
🤩
2,634
3.64%
⚡
4
0.006%
🤬
4
0.006%
🤡
1
0.001%
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 990 of the 1,000 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 72,351 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 4 October 2026 to 4 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.
Recent posts
Telegram’s own ‘edited’ marker: 7 of 955 posts held from the last 30 days (0.733%) 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).
Showing the 12 most recent of 2,739 posts we hold for @f_kbg. 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.
Posts edited after publishing
@f_kbg edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
16 September 2026
Most recent edit
16 September 2026
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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@f_kbg named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@gx1813 named in 1 post, 9 October 2026 – 9 October 2026
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 14 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
Kajal Online Hub @kajal_online_hub · 90,079 Telegram ranks this channel #1 of 79 here — alongside 78 others — read 14 August 2026
全球华人新闻吃瓜头条大曝光 @dnyqqbj · 86,843 Telegram ranks this channel #23 of 72 here — alongside 71 others — read 14 August 2026
泰国大事件|全球大事件曝光 悬赏 @xinwen0888 · 79,170 Telegram ranks this channel #43 of 70 here — alongside 69 others — read 17 August 2026
Пруф @proof24_ua · 152,278 Telegram ranks this channel #52 of 77 here — alongside 76 others — read 14 August 2026
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 4 November 2026 — this
entry's latest reading, not the date you are reading this.
“东南亚快曝光” (@f_kbg), 172,870 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/f_kbg.
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.
