☀️COLLAR 8點直樂VIURIETY (8月11日)- DAY FC🌙入場名額🎉已經完成通知 請各位Night留意PM ⚠️獲選者請以PM回覆訊息以確認名額⚠️
❤8

Channel
@daysinformation
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
2,268subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001798124509 |
|---|---|
| Type | Channel |
| Username | @daysinformation |
| Created | Between 1 January 2022 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 27 August 2026 |
| On Telegram | t.me/daysinformation |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 08:27 | 2,268 | +1 |
| 24 Aug 2026, 02:54 | 2,267 | -3 |
| 20 Aug 2026, 10:28 | 2,270 | -1 |
| 17 Aug 2026, 16:18 | 2,271 | +2 |
| 14 Aug 2026, 03:14 | 2,269 | +1 |
| 10 Aug 2026, 23:47 | 2,268 | -2 |
| 7 Aug 2026, 23:09 | 2,270 | no change |
| 7 Aug 2026, 05:00 | 2,270 | first reading |
20 posts held, back to 19 May 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 2 pagesof 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.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 20 (19 May 2026 – 6 August 2026) |
| Views total | 1,834 |
| Reactions total | 83 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 16:43 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.
684 reactions across 20 posts, in 10 distinct kinds. The most used accounts for 78.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 538 | 78.7% | |
| 😢 | 58 | 8.48% | |
| 😭 | 38 | 5.56% | |
| 👍 | 19 | 2.78% | |
| 😱 | 10 | 1.46% | |
| 🫡 | 9 | 1.32% | |
| 😨 | 7 | 1.02% | |
| 🤩 | 3 | 0.439% | |
| 🔥 | 1 | 0.146% | |
| 😍 | 1 | 0.146% |
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 20 of the 20 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 684reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 19 May 2026 to 6 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @daysinformation. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 19 May 2026 to 6 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
☀️COLLAR 8點直樂VIURIETY (8月11日)- DAY FC🌙入場名額🎉已經完成通知 請各位Night留意PM ⚠️獲選者請以PM回覆訊息以確認名額⚠️
❤8
☀️COLLAR 8點直樂VIURIETY - DAY FC🌙 活動日期:8 月 11 日(星期二)晚上時段 集合時間:晚上 6 時 30 分(逾時不候) 集合地點:將軍澳景嶺路3號HKDI 大門口對出巴士站(港鐵調景嶺站A2出口)[https://maps.app.goo.gl/gXfxJpUGHm8UiKSb6] 其他詳情會於 8 月 7 日前以PM方式另行聯繫獲挑選的Nights,如沒有獲選則不獲通知。 開放填表時間:8 月 6 日中午 12 時 表格連結:https://forms.gle/VN11hkGiLYhBBQkbA ============活動條款及細則============ ❗️ 是次活動DayHKFC 2026年度會員優先以實名登記參與,如有餘額,才會安排TG非會員參與 。 ❗️ 參加者必須年滿 18 歲 ❗️ Day FC將按 是否持有Day FC手牌、填表先後次序 及 是否正確完成表單挑選參…
❤30
公告 有關 MUSIC UNBOUNDED LIVE MACAU - COLLAR 4EVE 演出取消的消息,我們正儘快了解詳情,並於日內以電郵通知已預購人士有關退款安排。 不便之處,敬請見諒。 COLLAR UNION
😭38😨7
☀️COLLAR 8點直樂VIURIETY (7月28日)- DAY FC🌙入場名額🎉已經完成通知 請各位Night留意PM ⚠️獲選者請以PM回覆訊息以確認名額⚠️
❤29
☀️COLLAR 8點直樂VIURIETY - DAY FC🌙 活動日期:7 月 28 日(星期二)晚上時段 集合時間:晚上 6 時 15 分(逾時不候) 集合地點:將軍澳景嶺路3號HKDI 大門口對出巴士站(港鐵調景嶺站A2出口)[https://maps.app.goo.gl/gXfxJpUGHm8UiKSb6] 其他詳情會於 7 月 24 日前以PM方式另行聯繫獲挑選的Nights,如沒有獲選則不獲通知。 開放填表時間:7 月 22 日下午 6 時 表格連結:https://forms.gle/ebs7yY1tcJAzr7Bt6 ============活動條款及細則============ ❗️ 是次活動DayHKFC 2026年度會員優先以實名登記參與,如有餘額,才會安排TG非會員參與 。 ❗️ 參加者必須年滿 18 歲 ❗️ Day FC將按 是否持有Day FC手牌、填表先後次序 及 是否正確完成表單挑選…
❤22
已通知候補人士 請在限期前按指示回覆
❤18
已通知獲選人士 請在限期前按指示回覆
❤28😢5
叱咤903星空下音樂會 門票訂購 COLLAR UNION 現開放「叱咤903星空下音樂會」門票預購!詳情如下: 日期:2026年8月15日 時間:晚上7時30分至8時30分 地點:昂坪市集戶外涼亭前 (指定Fan Zone Area) 票價:$100 *票價已包括纜車夜航成人門票乙張+音樂會手帶乙條 集合地點及時間:下午5時20分東涌纜車站售票處 *集合詳細地點時間詳情會DM 獲選者,獲選者必須依時於指定地點集合 ⭐️門票數量有限,每人限購1張。 ⭐️獲選者將於7月19日前收到 TG DM。如未獲選中則不獲通知。 ⭐️名額先到先得。各 FC 將以 Telegram DM 通知付款安排,獲選者須於7月20日下午2時前確認或付款。 ⏰訂購日期及時間:2026年7月18日中午12點至7月19日上午11:59時 ⚠️填表時請務必正確揀選所屬的 FC 單位,每FC名額將分開計算。 >>表格<< ===活動條款及細則=== …
❤28😱3
Hello 大家 由於節目組通知有更改,所以星期二許軼不會出席🙏🏻 希望好快會再見🩵
😢53🫡9😱7
☀️COLLAR 8點直樂VIURIETY - DAY FC🌙 活動日期:7 月 21 日(星期二)晚上時段 集合時間:晚上 6 時 15 分(逾時不候) 集合地點:將軍澳景嶺路3號HKDI 大門口對出巴士站(港鐵調景嶺站A2出口)[https://maps.app.goo.gl/gXfxJpUGHm8UiKSb6] 其他詳情會於 7 月 18 日前以PM方式另行聯繫獲挑選的Nights,如沒有獲選則不獲通知。 開放填表時間:7 月 16 日下午 6 時 表格連結: ============活動條款及細則============ ❗️ 是次活動DayHKFC 2026年度會員優先以實名登記參與,如有餘額,才會安排TG非會員參與 。 ❗️ 參加者必須年滿 18 歲 ❗️ Day FC將按 是否持有Day FC手牌、填表先後次序 及 是否正確完成表單挑選參加者 ❗ 未曾參與過 COLLAR 成員《8點直樂 VIURIETY…
❤26
☀️7月15日《After One More Bite》簽名會Fans Zone入場名額 - DAY FC🌙 活動時間:2026 年 7 月 15 日 (星期三) 活動地點:點子出版攤位外(Hall 1B-E02)/ 博覽道入口大堂(Hall 1B出入口扶手電梯直落) 名額:少量 是次簽書活動之Fans Zone名額與購買新書/簽名活動名額無關,Fans Zone申請僅限於提供位置停留,請自行判斷衡量是否報名。 因受場地限制及人流管制,為免發生意外,現場不能使用腳架及梯。 如選擇進入Fans Zone,請停留至該節簽名完畢,否則將視作放棄名額,特別理由除外(排隊等候簽名等) 由於場地限制所以人數有限,請大家保持冷靜並遵守規則,否則會展或主辦方面有權腰斬活動。 FC將會以PM方式另行聯繫獲挑選的Nights,如沒有獲選則不獲通知。 開放填表時間:即時 報名連結🔗:https://forms.gle/9pP1pxj…
❤31
☀️COLLAR 8點直樂VIURIETY (7月7日)- DAY FC🌙入場名額🎉已經完成通知 請各位Night留意PM ⚠️獲選者請以PM回覆訊息以確認名額⚠️
❤31
Showing the 12 most recent of 20 posts we hold for @daysinformation. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
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.
@daysinformation named 2 handles 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.
References a handle that is not a live channel — we have no record it ever was one.
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.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“Day HKFC official channel” (@daysinformation), 2,268 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/daysinformation.
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.