更新 Telegram 至 12.5.0 后可以点开群信息,给自己添加标签。(需要管理开启相关权限)
❤19👍1
Channel
@godaddynsfw
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
32,206subscribers
+55 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001215043254 |
|---|---|
| Type | Channel |
| Username | @godaddynsfw |
| Description | 直男群的NSFW频道 狗爹汉化组官方 【Telegram漫游指南】 https://t.me/goudaddy/591 群友推荐的瑟琴频道都整理到最下面的【隐藏秘籍】里喽😉 【提供资源或合作请联系】 @xmswl |
| Created | Between 1 March 2018 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/godaddynsfw |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 03:15 | 32,206 | +3 |
| 14 Aug 2026, 13:53 | 32,203 | +5 |
| 13 Aug 2026, 01:48 | 32,198 | +3 |
| 12 Aug 2026, 01:58 | 32,195 | +12 |
| 11 Aug 2026, 03:01 | 32,183 | +1 |
| 10 Aug 2026, 00:03 | 32,182 | -2 |
| 9 Aug 2026, 00:51 | 32,184 | +15 |
| 7 Aug 2026, 23:13 | 32,169 | +14 |
| 6 Aug 2026, 21:15 | 32,155 | +4 |
| 6 Aug 2026, 12:46 | 32,151 | first reading |
14 posts held, back to 26 March 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 24 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 14 posts for this entry, the most recent from 1 March 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 16 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.
Measured directly from 1 video 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.
558 reactions across 14 posts, in 13 distinct kinds. The most used accounts for 58.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 324 | 58.1% | |
| 😍 | 60 | 10.8% | |
| 👍 | 56 | 10.0% | |
| 🤩 | 34 | 6.09% | |
| 🫡 | 24 | 4.30% | |
| 👀 | 20 | 3.58% | |
| 🥰 | 15 | 2.69% | |
| 👻 | 10 | 1.79% | |
| 🤣 | 6 | 1.08% | |
| 😁 | 5 | 0.896% | |
| 🎉 | 2 | 0.358% | |
| 🆒 | 1 | 0.179% | |
| 🔥 | 1 | 0.179% |
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 14 of the 14 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 558reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 26 March 2025 to 1 March 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.
更新 Telegram 至 12.5.0 后可以点开群信息,给自己添加标签。(需要管理开启相关权限)
❤19👍1
「狼人布魯諾」模型發表! 由 @Ross 監製、跟 @devilstudio8902 合作的模型終於完成了! 布魯諾或是大狼人的粉絲請不要錯過! 更多資訊及預訂預計下週一公布! “Werewolf Bruno” Figure Reveal! The figure Ross produced in collaboration with Devil Studio is finally complete! Fans of Bruno or big werewolves, don’t miss this! More information and pre-order details will be announced next Monday! via. X #推广 #模型 #index
😍60❤53🤣6👍3🤩2
【下面这个频道被盗,不要点击里面的链接】 潘之兽の圣域 https://t.me/Panka1zz/ 新频道 新潘之兽の圣域: https://t.me/Pankazz2 另外,伪造的官方账户开始使用 跳转文本 代替 假网址,不要相信任何私聊你的信息。 #盗号 #index
❤21👀20👍5
近日 Telegram 大量账户被盗,不要相信任何私聊你的号。 #盗号 #index
❤63🫡24👻6😁4
近日 Telegram 大量账户被盗,不要相信任何私聊你的号。 #盗号 #index
❤21😁1
👉DDB汉化屋 男同向游戏汉化 “DDB自制汉化 频道链接:https://t.me/+iFr8yLYQZaA0ZTQ1 讨论群组:https://t.me/+NVch-FhLqY81NzJl 频道内所有内容均为AI翻译的汉化调整版本 转发请记得注明出处哦 *欢迎反馈游戏bug *如果有想要翻译的游戏也可以在讨论组提出要求 文件遇到解压密码请尝试gamemale” 👉【TG群组及频道推荐】 (btsrk特供版) #推荐 #index
❤41🎉1
第二本为AI上色 #沙豆狼汉化 #index
❤40🥰9👍2
Photo, posted without a caption
❤19🥰2
#沙豆狼汉化 #index
❤8
Photo, posted without a caption
🤩32❤11
👉水瓶道 多是男男向漫画汉化 “放点自己汉化的东西” 👉【TG群组及频道推荐】 (btsrk特供版) #推荐 #index
👍9❤7🔥1
👉新·酥米饼频道 漫画翻译 “有什么感兴趣但没被汉化的漫画可以直接在这里说,如果对上电波就可以帮忙翻,而且如果对自己参与喜欢的漫画的嵌字这件事有兴趣的话也可以找我” 👉【TG群组及频道推荐】 (btsrk特供版) #推荐 #index
👍11❤9🥰2🎉1
Showing the 12 most recent of 14 posts we hold for @godaddynsfw. 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.
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.
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.
@godaddynsfw named 1 handle 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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“马可西亚斯-NSFW” (@godaddynsfw), 32,206 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/godaddynsfw.
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.