Telegram RegisterThe public register of Telegram
Telegram profile photo for 高雄南蠻廖理歐涉入三峽恐攻

Channel

高雄南蠻廖理歐涉入三峽恐攻

@New_Spongebaoo

On this record: Growth · Engagement · Posts · Citations · Cite this entry

458subscribers

+55 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002556380071
TypeChannel
Username@New_Spongebaoo
CreatedBetween 1 March 2025 and 23 June 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/New_Spongebaoo

Growth

403458430.57 August 2026 — 403 subscribers7 August 2026 — 403 subscribers14 August 2026 — 458 subscribers7 August 202614 August 2026
3 measurements spanning 7 days, net +55. 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 395–466 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 00:07458+55
7 Aug 2026, 03:15403no change
7 Aug 2026, 03:07403first reading

Engagement

8 posts held, back to 23 June 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 8 posts for this entry, the most recent from 12 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

12 Jul 2026, 13:07 UTC21 viewsread 7 August 2026
Forwarded from @lzalinsoha

THE SEQUEL TO 這四年中文圈Telegram圈最大的犯罪小說 中共同路人源自於洛克伍德詐騙網站與郭文貴 Flynn Networok。 disclam: 真的Flynn可能被保護或是白帽子double agent, 只是用Flynn 代表這個間諜網 中共同路人篇 陰謀圈總論 國際大爆料 黑川DS粉絲淚目系列 extras: 李⭐️中⭐️安人生終  馬來西亞王群光醫生之死的真相及後果 王醫生交通謀殺+三峽交通恐攻 中共同路人、綠蛆鶄蟾,假荷蘭五毛最終真相 笑死!TG一群宅男魯蛇性騷女同夥! 笑死!Epstein黑函勒索 TG反針version! 台灣大罷免的陰謀 同仁Archive 簡體 中文TG圈这四年内最空前精彩的犯罪小说 認同= 轉發到FB X 等 不要訂閱

27 Jul 2025, 17:08 UTC118 viewsread 7 August 2026
Forwarded from @lzalinsohaPhoto

給需要這訊息的人: 這次台灣大罷免的陰謀 最初陰謀目的:軍事法/戒嚴 引發台海 完成網上農場文章流傳的台海戰爭預言。 國會過半後,賴清德像南韓總統2024啟動軍事法/戒嚴,最後人口滅絕,統一或台灣綠共蔣家永遠執政。 evidence: 法輪功等民運媒體在煽動2027 青鳥側翼八炯: 國會DPP過半為了軍事法/戒嚴 但, 這個計劃因為川普回來被破壞, 不實際。 最實際最近的目的:阻止川普美援,擺爛,轉移焦點一年 逃避關稅 理由:川普獲勝、就職、關稅etc 最實際的目的。 目的無非是,利用智障青鳥等DPP測益敗壞台獨與親美親西方勢力的印象名聲,為之後DS落敗後添加川普等人對台灣援助的困難挑戰。幫助華國國民黨納粹勢力後DS時代在台灣復辟。 這完全就是低級黑小明 @djhxiaoming 高雄南蠻廖理哥 @LeoLiau 等人小屁孩舉止敗壞反針陰謀圈,滲透台獨親西方派後敗壞名聲,DPP version。

20 Jul 2025, 21:09 UTC32 viewsread 7 August 2026
Forwarded from @lzalinsohaPhoto

理哥照片真實性?! 根據離譜太太的貼文,這個照片是2020 四月在他個人FB頁(不是那兩個fans pages) 還因此被肉搜關了這個帳號。 卻有在高雄的照片+說吉要告某人=在台灣 當時他的人設是在美國準備轉學到荷蘭 完全說中人設假的 已被證實特地改荷蘭時間自稱回台灣忘記改 荷蘭五毛平日造假荷蘭時間

12 Jul 2025, 16:52 UTC11 viewsread 7 August 2026
Forwarded from @lzalinsohaPhoto

某人最近從荷蘭回到了台灣(自稱) 目前先不說他狗急跳牆又說了什麼謊。 他自稱他回來後立馬被網軍威脅 照理他回台灣手機時間會同步當地時間,他自稱回來被威脅,因此採取的證據內的時間是在荷蘭的時間!🤩🤩(原文還是2022的發文) 這叫做弄巧成拙?平日他都是人在台灣,刻意改成荷蘭時區在假造人設? 我沒聽過誰在當地過著外國的時間科科 所謂的自爆 王醫生交通謀殺+三峽交通恐攻 中共同路人、綠蛆鶄蟾,假荷蘭五毛最終真相

30 Jun 2025, 12:20 UTC16 viewsread 7 August 2026
Forwarded from @lzalinsohaPhoto

獨家!地球谷疑似累犯理哥的小編! 恭喜  t.me/InfoWarsFormosa  回歸祖國祖歸宗。為了尋根資訊戰開了FB粉絲頁直播分享他們認祖歸宗的喜悅,大概就是6/28到不知道什麼時候。https://www.facebook.com/RUSUAtruth 可是很奇怪!同時認真每天寫文發文的地球谷在他們直播前消失停編輯了好幾天?! 該不會這因為他們是理哥的共同小編編輯部,而旅行到中國山西的就是他們?! 而照片中這個像是在做化療的人,就是他們地球谷小編的一個人?! 這非常可能就是真相!他們和廖理哥共同經營FB Line Telegram等等! 所以那些直播是用電腦直播播放事先做好的訪問,那些FB粉專上的照片都已經好幾天前就拍好了! 可能性  1)他們這些香港人在香港 2)他們是在台灣的香港人 這裡還給理哥一個公道,他不是不知道豬哥亮死了 而是當時地球谷的小編讀到豬哥亮的老新聞,天真地用理哥的理觀點粉專發了文

23 Jun 2025, 05:10 UTC47 viewsread 7 August 2026
Forwarded from @lzalinsohaPhoto

證實!假老外帳號=路權嘎抓廖理哥 www.facebook.com/Maria.Chiara.Berti.1997 telegram @LeoTTwn 被揭露後神速關帳號。 一個老外還會讀中文圈telegram?科科 高雄土著廖理哥的FB分身 王醫生交通謀殺+三峽交通恐攻 中共同路人、綠蛆鶄蟾,假荷蘭五毛最終真相

Showing the 8 most recent of 8 posts we hold for @New_Spongebaoo. 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.

Forward network

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.

Mentions

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.

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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“高雄南蠻廖理歐涉入三峽恐攻” (@New_Spongebaoo), 458 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/New_Spongebaoo.

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.