Channel
@scottscout
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
56,715subscribers
-142 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001428078242 |
|---|---|
| Type | Channel |
| Username | @scottscout |
| Description | Scott Scout 成立目的為提供客觀現場資訊及情報，以確保現場手足訊息流通。 本頻道並不會提議或慫恿手足作任何行動，一切行動交由現場手足全權決定。 Channel link: https://t.me/scottscout 報料 ： https://t.me/scottscout/148254 🛑維持有限度運作之公告： https://t.me/scottscout/165860 |
| Created | 10 June 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/scottscout |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 13:18 | 56,715 | -18 |
| 13 Aug 2026, 03:34 | 56,733 | -5 |
| 12 Aug 2026, 06:23 | 56,738 | -26 |
| 11 Aug 2026, 03:15 | 56,764 | -30 |
| 10 Aug 2026, 06:00 | 56,794 | -6 |
| 9 Aug 2026, 06:42 | 56,800 | -23 |
| 8 Aug 2026, 09:37 | 56,823 | -17 |
| 7 Aug 2026, 12:45 | 56,840 | -5 |
| 6 Aug 2026, 11:00 | 56,845 | -12 |
| 6 Aug 2026, 09:00 | 56,857 | no change |
| 6 Aug 2026, 08:59 | 56,857 | first reading |
20 posts held, back to 2 July 2021 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 21 pagesof 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 20 posts for this entry, the most recent from 22 December 2021. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 14 August 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.
#巴打報料 警方三輛水炮車（又稱：人群管理特別用途車）在 2019 年至 2020 年反修例運動期間多次出動，警方去年提出再增購 3 部水炮車 。警方今日（21 日）回覆查詢時確認， 3 輛較小型的「水炮車」今日已經抵港，換言之未來將有 6 輛水炮車可供調配。 東方今日(22日)引消息報道，指警方購入的 3 輛中國製的水炮車已抵港，報道指三車車身較細，可於橫街窄巷行走，將交予機電工程署作驗收，警方預計明年第 1 季起接收，水炮水力則與之前的水炮車相同。 警方今日回覆《立場》查詢時表示，警隊已經額外採購三輛較小型的水炮車，讓警隊在不同環境下執行人群管理工作時，有多一個行動裝備的選項，該批車輛已於今日到港。 警方指，會要求所有操作人員在使用車輛前必須接受相關的駕駛、操作及安全訓練，並嚴格遵守相關守則及指引，當中包括車輛基本操作、安全指引等，使人員能掌握技巧，安全和有效地操作車輛。 警方又稱，有嚴謹的武力使用守則，包括只會使用…
【為工程巴送上生日祝福】 去年工程巴因網上言論，被還押將近一年半。今年是他於收押所渡過的第二個生日，將面對明年的漫長審訊過程，任誰也快樂不起。願我們再次把祝福化成文字為工程巴送上鼓勵和力量！ 生日祝福請送到： @youarenotalonehk_mail2bot 截止日期：2021年10月13日 23:00 —————————————————— 歡迎大家支持工程巴嘅patreon💛 http://www.patreon.com/engineers9up Instagram：不實用Engineer's 9up
▍831襲擊事件2周年 🇬🇧 全英國 集會及活動時間 整合 🇬🇧 英國各地將會於各地有不同人仕與機構自發舉辦,形式包括集會,分享,相片展等，去悼念、記念、解釋有關831兩周年活動，希望大家抽空參與。 📍地點包括: Birmingham, Bristol, Cambridge, Edinburgh, Exeter, Leeds, Guildford, Liverpool, London, Manchester, Nottingham, Reading, Southampton ⚠️留意活動日子由8月28至31日期間進行⚠️ 英國831活動詳情連結 🌐 bit.ly/831UK_Assemblies 📣資料如有錯漏，請按主辦單位宣佈為準。 Credit: @britonshk
https://thestandnews.page.link/fY2DvehjCSrPN3peA
https://thestandnews.page.link/P2K7z37YuRDackvb9
有喺初選果陣做票站主任嘅請注意 請務必盡快清理好敏感資料以及聯絡定律師 啲警曱可能今明兩日會郁
#手足投稿 #factcheck 何謂factcheck 就光城者新聞，不如大家一齊做一次fact-check嘅練習 警方國安處：港獨組織「光城者」策劃製土製炸藥 以國安法 24 條恐怖活動罪ㅤ拘捕 5 男 4 女 1. 這是真實的資訊，還是意見？ 光城者一直有擺街站，做各種文宣活動，係真實嘅資訊。 以下是國安處所提供嘅未能確認事實嘅資訊。 “他指出，被捕人屬「激進港獨組織」，組織名為「光城者」，合謀製造土製炸藥 TATP。組織有「行動書籍」，打算針對公共設施，襲擊海底隧道、鐵路、法庭、街道垃圾筒，甚至打算用汽車炸彈，計劃已到實踐階段。” 2. 這則資訊發佈的目的是甚麼？ 明顯國安處嘅目的係要將光城者定義為恐怖組織，有如梁烈士嘅行動被定義為「孤狼式恐怖襲擊」。 3.是誰發佈這則資訊？ 國安處 4. 資訊來源是否值得信賴？ 以721，831為例，政府所發佈資訊非完全可信及有偏袒成份。 5. 這則資訊是否能在其他管道獲…
Scott Scout 認證哨兵消息主頻道 pinned «#公告 🌀🌀🌀🌀🌀🌀🌀🌀🌀🌀 【Scott Scout Channel 維持有限度運作】 Scott Scout 成立目的始於為街頭抗爭手足提供客觀現場資訊及情報，以確保現場手足訊息流通。隨著時局、抗爭形式轉變，本頻亦失去當初最大作用。有見及此，由即日起本頻運作模式將作以下調整： 1. 除有重大遊行、活動、緊急事件外，本頻將停止日常報哨 2. 仍接受緊急或重要之報料/爆料👇🏿 @Scottscout_NT_mk2_bot 一浪浪街頭抗爭，一步步撕破謊言，香港人覺醒，國際社會開始正視中共惡行，手…»
#荃灣 1318 白田壩街 一衝停泊 一隊軍裝brief緊
#九龍灣 2330 觀塘道九龍灣站外西行線RB
#銅鑼灣 2352 軒尼詩道Sogo外各警車逐步撤離 淨一鬼私一鬼van未走 渣甸街兩籠上緊狗撤離
#銅鑼灣 2130 Time square 對出羅素街 12 藍分兩隊向希慎及波斯富街行
Showing the 12 most recent of 20 posts we hold for @scottscout. 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.
Citation-graph rank — 257,281 of 1,345,403entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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 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.
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.
@scottscout named 3 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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“Scott Scout 認證哨兵消息主頻道” (@scottscout), 56,715 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/scottscout.
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.