1 Sept 2025, 02:03 UTC143 viewsread 10 August 2026
✅ 机器人已成功加入频道 (消息来自 @soso)
Channel
IP代理【原生住宅】
@IPUPD
On this record: Growth · Engagement · Posts · Citations · Cite this entry
48subscribers
-1 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 | -1001313250644 |
|---|---|
| Type | Channel |
| Username | @IPUPD |
| Created | 3 January 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 10 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/IPUPD |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 23:47 | 48 | -1 |
| 10 Aug 2026, 12:31 | 49 | no change |
| 7 Aug 2026, 19:52 | 49 | first reading |
Engagement
20 posts held, back to 8 December 2023 — the 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 20 posts for this entry, the most recent from 1 September 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
1 Sept 2025, 02:02 UTCviews —
Channel name was changed to «IP代理【原生住宅】»
1 Sept 2025, 02:02 UTCviews —
Channel photo updated
23 May 2025, 16:46 UTC180 viewsread 10 August 2026
【免费试用限时开启】全球原生住宅IP | 支持TikTok、FB、爬虫稳定使用！ 你是否遇到这些问题： • FB账号一登录就风控？ • TikTok广告投放频繁封户？ • 多账号切换环境总被识别？ • 爬虫封IP太快、成本高？ 核心问题：你缺一个真正“原生”的、稳定的IP环境。 我们能提供什么？ 全球原生住宅代理IP（静态 / 动态 / 4G移动IP） • 真实运营商IP段，非数据中心，平台识别为“真实家庭网络” • 支持60+国家：美国、英国、日本、法国、印度、菲律宾、新加坡等 • 完美适配：TikTok / FB / IG / Google Ads / Amazon / 爬虫任务
25 Jul 2024, 05:44 UTC349 viewsread 10 August 2026
前段时间有个要对接海外路由器资源的老板联系我一下，找不到你了 @IP9966
18 May 2024, 04:22 UTC383 viewsread 10 August 2026
静态住宅IP代理： （国内支持scoks5，http，l2tp，pptp） 中国大陆：四十多个城市，咨询客服购买 亚太地区：香港 台湾 韩国 日本 印度 泰国 越南 新加坡 澳大利亚 马来西亚等 欧洲地区：俄罗斯 荷兰 波兰 法国 西班牙 芬兰 德国 英国 意大利 拉脱维亚 亚美尼亚等 美洲地区：美国 加拿大 巴西 等 国内地区住宅最高带宽可到100m，真实家庭住宅ip 支持全球各地区业务，详情请咨询客服 动态住宅ISP代理： 低于市场各大知名品牌的价格，同样能达到你使用的预期效果 让你花小钱办大事 全球220+国家/地区 不限并发 不限带宽 HTTP/HTTPS/SOCKS5 联系 @IP9966 先测试后购买，IP租赁期内出现质量问题免费更换不限次数
17 Apr 2024, 15:15 UTC311 viewsread 10 August 2026
国内动态ip https://h.shenlongip.com/index?from=seller&did=jg1ZRI
6 Mar 2024, 01:44 UTC296 viewsread 10 August 2026
国内静态IP价格：RMB 家庭住宅：socks5，http协议 ip格式：（wzqbr023.8800.org|2818|cs623|cs623） 👇🏼👇🏼 国内家庭住宅IP：100m带宽—70月卡（直播无压力） 国内家庭住宅IP：5m带宽—40月卡 l2tp，pptp协议（手机vpn直连） ip格式：（ST00530600001 403v2q p21.fjsm4.ip6b.com） 👇🏼👇🏼 带宽1-3m—35月卡 带宽3-5m—50月卡 带宽5-7m—70月卡 数据中心静态：socks5，http协议 ip格式：（36.99.162.33|2018|yd525|5525） 👇🏼👇🏼 共享ip带宽3m—20月卡 独享ip带宽10m—35月卡 海外静态IP价格：RMB 优质住宅IP—40月卡 格式(proxy.hideiqxshlgvjk.com:5050:ip-154.40.43…
29 Feb 2024, 03:08 UTC226 viewsread 10 August 2026
静态住宅IP代理： （国内支持scoks5，http，l2tp，pptp） 中国大陆：四十多个城市，咨询客服购买 亚太地区：香港 台湾 韩国 日本 印度 泰国 越南 新加坡 澳大利亚 马来西亚等 欧洲地区：俄罗斯 荷兰 波兰 法国 西班牙 芬兰 德国 英国 意大利 拉脱维亚 亚美尼亚等 美洲地区：美国 加拿大 巴西 等 国内地区住宅最高带宽可到100m，真实家庭住宅ip 支持全球各地区业务，详情请咨询客服 动态住宅ISP代理： 低于市场各大知名品牌的价格，同样能达到你使用的预期效果 让你花小钱办大事 全球220+国家/地区 不限并发 不限带宽 HTTP/HTTPS/SOCKS5 联系 @IP9966 先测试后购买，IP租赁期内出现质量问题免费更换不限次数
24 Feb 2024, 11:31 UTC183 viewsread 10 August 2026
Photo
国内地区列表
18 Feb 2024, 01:20 UTC188 viewsread 10 August 2026
Photo
闹钟一响，黄金万两
5 Feb 2024, 10:10 UTC165 viewsread 10 August 2026
国内静态IP价格：RMB 家庭住宅：socks5，http协议 ip格式：（wzqbr023.8800.org|2818|cs623|cs623） 👇🏼👇🏼 国内家庭住宅IP：100m带宽—70月卡（直播无压力） 国内家庭住宅IP：5m带宽—40月卡 l2tp，pptp协议（手机vpn直连） ip格式：（ST00530600001 403v2q p21.fjsm4.ip6b.com） 👇🏼👇🏼 带宽1-3m—35月卡 带宽3-5m—50月卡 带宽5-7m—70月卡 数据中心静态：socks5，http协议 ip格式：（36.99.162.33|2018|yd525|5525） 👇🏼👇🏼 共享ip带宽3m—20月卡 独享ip带宽10m—35月卡 海外静态IP价格：RMB 优质住宅IP—40月卡 格式(proxy.hideiqxshlgvjk.com:5050:ip-154.40.43…
Showing the 12 most recent of 20 posts we hold for @IPUPD. 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 — 1,390,634 of 1,481,502entries 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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“IP代理【原生住宅】” (@IPUPD), 48 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/IPUPD.
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.