Gambling & betting — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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
30 measurements spanning 44 days, net +117,088. 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”.
Measurement log — every subscribers count we have recorded, most recent 20 of 30
Measured (UTC)
Subscribers
Change
26 Sept 2026, 00:20
204,781
+76,244
19 Sept 2026, 09:39
128,537
+29,368
17 Sept 2026, 00:39
99,169
-91
15 Sept 2026, 05:15
99,260
-49
13 Sept 2026, 11:56
99,309
-220
11 Sept 2026, 14:35
99,529
-249
9 Sept 2026, 01:18
99,778
-524
5 Sept 2026, 14:21
100,302
-300
3 Sept 2026, 16:15
100,602
-68
2 Sept 2026, 07:16
100,670
-270
1 Sept 2026, 04:08
100,940
-157
31 Aug 2026, 05:25
101,097
-105
30 Aug 2026, 08:18
101,202
-49
29 Aug 2026, 05:23
101,251
-40
28 Aug 2026, 03:28
101,291
-33
27 Aug 2026, 06:06
101,324
-72
26 Aug 2026, 05:24
101,396
-300
25 Aug 2026, 02:11
101,696
+79,337
23 Aug 2026, 14:26
22,359
-892
22 Aug 2026, 01:38
23,251
first reading
Engagement
1,179 posts held, back to 12 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 96 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
1.37%
avg views ÷ 204,781 subscribers
Avg views / post
2,810
696 posts measured
Reaction rate
0.585%
reactions ÷ views · ER floor
Posts in window
696
of 1,179 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 653 of 696 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 30 September 2026
Posts held
1,179 (12 August 2026 – 30 September 2026)
Views total
1,955,447
Reactions total
11,089
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
30 Sept 2026, 04:13 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
Photos
≈34,000
Videos
≈6,640
Links
≈14,400
Lifetime counters from Telegram’s own channel header, read 30 September 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.
Video runtime
3h 57m
Average length
37s
Measured directly from 382 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
15,199 reactions across 948 posts, in 12 distinct kinds. The most used accounts for 13.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🥰
2,076
13.7%
❤🔥
2,069
13.6%
🔥
2,061
13.6%
🎉
2,015
13.3%
💯
2,013
13.2%
🤩
1,260
8.29%
❤
1,255
8.26%
👍
1,241
8.17%
😍
1,175
7.73%
👏
17
0.112%
😁
16
0.105%
⚡
1
0.007%
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 948 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 15,199 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 19 August 2026 to 30 September 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.
Showing the 12 most recent of 1,179 posts we hold for @feilvbin2025. 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.
Mentions
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.
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 25 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.
迪拜新闻|海豹资讯曝光|dubai news @dibai_01 · 178,705 Telegram ranks this channel #1 of 50 here — alongside 49 others — read 15 August 2026
菲律宾今日新闻|海豹资讯曝光|philippine news @baoguang_123 · 119,228 Telegram ranks this channel #1 of 73 here — alongside 72 others — read 14 August 2026
This channel appears in 2 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 26 September 2026 — this
entry's latest reading, not the date you are reading this.
“菲律宾新闻大事件|philippine news” (@feilvbin2025), 204,781 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/feilvbin2025.
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.
