Telegram RegisterThe public register of Telegram
Telegram profile photo for 马可西亚斯

Channel

马可西亚斯

@goudaddy

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

9,735subscribers

+35 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001352676350
TypeChannel
Username@goudaddy
Description【Telegram漫游指南】 https://t.me/goudaddy/591 【提供资源或合作请联系】 @xmswl
CreatedBetween 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/goudaddy

Growth

9,7009,7359,717.56 August 2026 — 9,700 subscribers7 August 2026 — 9,700 subscribers10 August 2026 — 9,715 subscribers13 August 2026 — 9,721 subscribers16 August 2026 — 9,735 subscribers6 August 202616 August 2026
5 measurements spanning 10 days, net +35. 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 9,695–9,740 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 14:539,735+14
13 Aug 2026, 00:049,721+6
10 Aug 2026, 04:119,715+15
7 Aug 2026, 00:069,700no change
6 Aug 2026, 12:489,700first reading

Engagement

28 posts held, back to 3 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 20 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
14.9%
avg views ÷ 9,735 subscribers
Avg views / post
1,450
21 posts measured
Reaction rate
0.018%
reactions ÷ views · ER floor
Posts in window
21
of 28 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 6 of 21 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 18 August 2026
Posts held28 (3 July 202618 August 2026)
Views total30,470
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Aug 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

Photos
863
Videos
48
Links
786

Lifetime counters from Telegram’s own channel header, read 18 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

5 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 80.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
480.0%
👌120.0%

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 10 of the 28 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 5reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 28 most recent posts we hold, published 3 July 2026 to 18 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.

Recent posts

18 Aug 2026, 05:31 UTC214 viewsread 18 August 2026

【检测到 Live A Hero 维护信息更新】(GMT+9): (不停服) 【故障修正】无法登录游戏 2026/08/18(周二)00:00~01:40期间,因外部服务故障导致登录困难,已处理完毕。 深表歉意。 已发放以太晶石×2作为补偿。 LAH维护详情 #维护 #LAH #index

17 Aug 2026, 02:30 UTC456 viewsread 18 August 2026

【检测到 Live A Hero 维护信息更新】(GMT+9): (非停止) 【问题修正】交流加成在困难・极难难度下未生效 期间限定活动「夏日蒙太奇・光晕」得分挑战的困难・极难难度中,交流加成增益未生效的问题已修复。 本件于2026/08/17 11:05修正。 LAH维护详情 #维护 #LAH #index

16 Aug 2026, 13:16 UTC499 viewsread 18 August 2026

【检测到 LAH 活动更新】(GMT+9): 【活动】夏日蒙太奇·光晕举办! 最终更新:2026/08/06 已公开角色PV。 「希望能找到能解开这个世界之谜的人」 只有英雄与「观测者」能在梦中前往的「梦幻多岛海」。到访此处的人们,被某位青年托付了这样的心愿。 不可思议的体验传闻不断,多元宇宙研究英雄也在追查真相。主张那里是虚拟空间、喜欢分享的技术研究者,与英雄们以及作为操作员的你一同尝试接入实验——眼前却出现了无尽大海的常夏乐园!? 一行人在当地遇见无气力系白帽黑客英雄、某离岛前役所职员,以度假心情热闹探索。前方等待着怎样的真相……但这绝非只是一场「梦」。 提示:通关过往活动「江之岛最终度假村 ~当地英雄大集合!~」后更能享受本活动剧情(未通关也可参加)。 活动概要 2026/07/30(周四)起举办期间限定活动「夏日蒙太奇·光晕」。通过自由任务与营业收集活动道具,可兑换育成道具等。活动期间实施期间限定登录奖励。 举

14 Aug 2026, 07:40 UTC726 views0 reactionsread 18 August 2026

【检测到 Live A Hero 维护信息更新】(GMT+9): 维护内容(非停止) 2026/08/14发布应用版本v4.14.1,对应以下内容。 *【功能改善】任务战斗动作改善* 改善了任务战斗中选择技能时可能出现的卡顿。 *【功能改善】假日任务序章回想功能追加* 期间限定活动「夏日蒙太奇・光晕」的交流地图已追加序章回想按钮。 *【BUG修复】假日任务有时无法回想* 修正了「夏日蒙太奇・光晕」交流地图中,提升交流等级后解锁的假日任务有时无法回想的问题。 LAH维护详情 #维护 #LAH #index

14 Aug 2026, 06:38 UTC723 viewsread 18 August 2026

检测到 Live A Hero jp.co.lifewonders.liveahero 有更新 当前版本号: 4.14.1 旧版本号: 4.14.0 安装包下载: 需等待网站同步更新,XAPK、APKS 等格式的安装包需用 MT管理器 安装。 [APKPure] Live a Hero [APKCombo] Live a Hero #更新 #LAH #index This message was sent automatically with n8n

12 Aug 2026, 06:46 UTC912 viewsread 18 August 2026

【检测到 Live A Hero 维护信息更新】(GMT+9): (非停止) 【表述修正】剧情修正 期间限定活动「夏日蒙太奇・光晕」第4话的部分剧情表述已修正。 本件于2026/08/12 15:30对应完成。 【问题修正】部分SE・语音音量未反映设置 部分角色技能发动演出的音量未反映声音设置的问题已修正。 本件于2026/08/12 15:30对应完成。 LAH维护详情 #维护 #LAH #index

10 Aug 2026, 05:55 UTC≈2,210 views1 reactionsread 18 August 2026

【检测到 Housamo 维护信息更新】(GMT+9): 维护更新 ■时间 2026/08/10(周一)14:51 -期间限定活动「梦之岛的灯笼祭 ~源平Wars的夏之迹~」的道具加成表中,部分角色稀有度标注有误,已修正。 Housamo维护详情 #维护 #Housamo #index

1

7 Aug 2026, 11:02 UTC≈2,190 views0 reactionsread 18 August 2026

【检测到 Housamo 维护信息更新】(GMT+9): 维护通知 ■时间 2026/08/07(周五)14:00~20:00 【注意】维护开始时进行中的任务战斗等,结束后可能无法继续。请提前结束游玩。 •活动对应 (维护中追记) 已实施以下改善及功能追加: •常驻AR转光召唤追加AR装备  ★5 背后的应援  ★5 无尽蓝色夏日  ★4 厨房最前线!  ★4 那份爱超越常暗  ★3 节拍半场! •安德瓦利商店追加卡片 ★4【与光之装备同行】勇者 ★3【米德加德的勇者】勇者 补偿:维护前创建的账号发放转光石×6至消息BOX。(8/7 19:22已发放) Housamo维护详情 #维护 #Housamo #index

6 Aug 2026, 19:26 UTC≈2,130 views0 reactionsread 18 August 2026

【检测到 Housamo 活动更新】(GMT+9): 【期间限定活动】梦之岛的灯笼祭 ~源平大战的夏之痕~ ◆活动时间◆ 【主线任务】2026年08月07日(周五)20:00 ~ 2026年09月04日(周五)13:59 【道具交换期限】2026年08月07日(周五)20:00 ~ 2026年09月11日(周五)23:59 【活动免费任务】2026年08月07日(周五)20:00 ~ 2026年09月04日(周五)13:59 【高难度任务】依次开放 ~ 2026年09月04日(周五)13:59 ※目前仅日文版上线 活动期间开放限定任务,通关可获得交换道具「太三郎的广播体操印章」「夏日回忆胶卷」,并可于交换所兑换奖励。另有高难度任务可挑战。 ◆攻略提示◆ 携带特定AR装备或角色(含泳装皮肤角色)通关,可提升上述道具掉落量。 部分任务掉落「岛长的零花钱」:前10次每个可换100万金币,之后每个可换10万金币(无限次)。活动

6 Aug 2026, 11:06 UTC≈1,030 viewsread 18 August 2026

【检测到 LAH 活动更新】(GMT+9): *【活动】夏日蒙太奇・光晕 举办!* 【最终更新】2026/07/30 已追加活动任务、活动营业及角色情报。 「希望你能找到能揭开这个世界真相的人」 英雄与「观测者」才能在梦中抵达的「梦幻多岛海」。 到访者会被一名青年托付心愿。 多元宇宙研究英雄也在追查真相。 爱分享的技术研究者主张那是虚拟空间,并与英雄及你一同进行接入实验—— 眼前竟是无尽大海的常夏乐园!? 与无气力系白帽黑客英雄、某离岛前公所职员相遇, 一边度假一边探索,前方究竟有怎样的真相…… ——但这绝不仅是「梦」。 【提示】 通关过去活动「江之岛最终度假村 ~当地英雄大集合!~」可更好享受剧情。 未通关也可参加本活动。 *活动概要* 自 2026/07/30(木)起举办期间限定活动「夏日蒙太奇・光晕」。 通过自由任务与营业收集活动道具,可兑换育成道具等。 期间另有限定登录奖励! *举办期间* 2026/07

6 Aug 2026, 09:01 UTC≈1,650 viewsread 18 August 2026

【检测到 Housamo 维护信息更新】(GMT+9): 维护通知 ■时间 2026/08/07(周五)14:00 ~ 20:00(预定) 【注意】维护开始时进行中的任务・战斗等结束后可能无法继续。请提前结束游玩。 - 活动对应 向维护前创建的『东京放学后召唤师』账号发放转光石×6至消息BOX。 Housamo维护详情 #维护 #Housamo #index

5 Aug 2026, 10:00 UTC≈1,800 viewsread 18 August 2026

【检测到 Housamo 活动更新】(GMT+9): 【期间限定活动】梦之岛的灯笼祭 ~源平大战的夏日残迹~ 活动时间 主线任务:2026年08月07日(周五)20:00 ~ 2026年09月04日(周五)13:59 活动道具兑换:2026年08月07日(周五)20:00 ~ 2026年09月11日(周五)23:59 活动自由任务:2026年08月07日(周五)20:00 ~ 2026年09月04日(周五)13:59 高难度任务:依次开放 ~ 2026年09月04日(周五)13:59 活动期间,活动区域将出现期间限定任务「梦之岛的灯笼祭 ~源平大战的夏日残迹~」。 主线剧情自2026年08月07日起陆续更新。 通关后可解锁可重复游玩的活动任务。 另将开放高难度任务,通关可获得道具。 ※目前仅日文版发布。 Housamo活动详情 #活动 #Housamo #index

Showing the 12 most recent of 28 posts we hold for @goudaddy. 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

Citation-graph rank — 439,445 of 1,549,704entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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

“马可西亚斯” (@goudaddy), 9,735 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/goudaddy.

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.