Telegram RegisterThe public register of Telegram
Telegram profile photo for Run资源分享频道

Channel

Run资源分享频道

@PAOLU_GGG

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

9,171subscribers

+305 since we began measuring on 19 August 2026

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

Register entry

Telegram ID-1001736318920
TypeChannel
Username@PAOLU_GGG
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded19 August 2026
Last confirmed live28 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 28 August 2026
On Telegramt.me/PAOLU_GGG

Growth

8,8669,1719,018.519 August 2026 — 8,866 subscribers19 August 2026 — 8,866 subscribers19 August 2026 — 8,876 subscribers22 August 2026 — 9,012 subscribers25 August 2026 — 9,076 subscribers28 August 2026 — 9,171 subscribers19 August 202628 August 2026
6 measurements spanning 9 days, net +305. 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 8,820–9,217 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Aug 2026, 17:539,171+95
25 Aug 2026, 10:129,076+64
22 Aug 2026, 15:179,012+136
19 Aug 2026, 11:268,876+10
19 Aug 2026, 07:458,866no change
19 Aug 2026, 07:308,866first reading

Engagement

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

ERR · 30 days
34.0%
avg views ÷ 9,171 subscribers
Avg views / post
3,120
8 posts measured
Reaction rate
0.164%
reactions ÷ views · ER floor
Posts in window
8
of 22 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 23 August 2026
Posts held22 (13 March 202623 August 2026)
Views total24,970
Reactions total41
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 15:26 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.

Reaction mix

163 reactions across 22 posts, in 12 distinct kinds. The most used accounts for 51.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
8451.5%
👍3018.4%
😡1710.4%
😭95.52%
😍74.29%
🥰74.29%
🎉21.23%
💩21.23%
🔥21.23%
💋10.613%
😁10.613%
🤡10.613%

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

Measured over the 22 most recent posts we hold, published 13 March 2026 to 23 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

23 Aug 2026, 19:02 UTC≈1,330 views1 reactionsread 28 August 2026
Sticker

Sticker, posted without a caption

👍1

Signed 庞世达

23 Aug 2026, 19:02 UTC≈1,360 views4 reactionsread 28 August 2026

火速给我找个免费/低价生视频ai

👍4

Signed 庞世达

23 Aug 2026, 12:07 UTC≈1,550 views4 reactionsread 28 August 2026

B.AI 前几天开放了免费的DeepSeek-V4-Flash和Hy3 优点:免费 缺点:容易超时,需要挂代理 体验了一下,能用,但是超时比较频繁,真要想用还是推荐搭配DeepSeek Harness,换一个稳定点的AI让它写一个全局可用的模型超时设置插件(因为Github上没有找到类似的插件),设置超时限制,例如可以设置一次响应10s,失败重试30次 这样就不会频繁中断了 具体的提示词可以参考一下我下面写的 帮我写一个全局生效的插件,位置位于设置按钮上方,名称是模型超时设置,点击弹出一块窗口 具体的功能是可以设置每个模型供应商的模型响应以及重试次数限制,要求可以自定义修改每个供应商的模型响应时间和超时重试次数,例如10s响应,30次重试 (点击复制) 提示词可能不完善,后续可根据个人需求进行调试 #AI #免费 #羊毛

4

17 Aug 2026, 19:05 UTC≈2,810 views13 reactionsread 28 August 2026
Sticker

Sticker, posted without a caption

😭9👍3🤡1

Signed 庞世达

17 Aug 2026, 01:49 UTC≈3,060 views3 reactionsread 28 August 2026

基元律动目前已上DeepSeek-Pro-0813 与0731一样,与官网高峰期定价相同 想薅的嫌麻烦的可以闲鱼搜索基元律动相关关键词,68元key低至一块钱一个 #AI #基元律动

👍3

7 Aug 2026, 14:09 UTC≈5,170 views4 reactionsread 28 August 2026

【Shaft2批量下载Pixiv画师作品】 这是一个相较于原版UI更美观的Pixiv第三方软件 除了UI比较亮眼之外,还有着批量下载/批量收藏画师作品的功能 点进画师主页,选择画廊/小说,右上角三个点,选择批量下载/批量收藏即可 不过还是建议用小号进行批量下载,避免账号被封禁 ▷ 开源地址 ◁ ▷ 软件下载 ◁ #Pixiv #工具 #批量下载

4

5 Aug 2026, 10:16 UTC≈5,200 views6 reactionsread 28 August 2026
Photo

【基元律动无限白嫖68额度账号】 因为基元律动前阵子开启了邀请拉新,拉一个人双方都可以获得68的API额度。 (当然,现在已经结束了,又重新上了一个拉新活动,但这次需要额外下载软件,增加了一定的门槛,不建议) 传言是为了向领导献业绩开启的拉新活动,但不管怎样,这次拉新活动的门槛极低,活动力度之大,导致滋生了很多的拉新业务,这也就导致大部分86接码软件的号池90%的号码都注册基元律动了,这些闲置的拉新账号内大概率都还会有68额度的API 由此,可以通过D1等86接码软件来接码再次登陆这些账号获取API_Key,这也就达到可以无限白嫖额度的目的 本来是没必要分享的(不是sol我用着咳嗽),因为在这个拉新活动开始的时候,deepseekv4-flash正式版已经更新了,但基元律动又不是中转的官方API,也就里面的glm5.2有点吸引力了。但今天听说基元又新上了deepseek-v4-flash0731,也就是正式版,这才觉得有

3👍3

3 Aug 2026, 19:06 UTC≈4,490 views6 reactionsread 28 August 2026
Sticker

Sticker, posted without a caption

6

Signed 庞世达

29 Jul 2026, 15:31 UTC≈4,560 views6 reactionsread 28 August 2026
Forwarded from @sszn_fxFile

适用于: Deepseek-v4-flash Deepseek-v4-pro 建议使用官方api,部分第三方中转站以求合规可能会上违禁词检测 使用方法:复制内文本首字发送即可 1M的上下文长度注意总结 #Deepseek #破甲 #AI

4👍2

19 Jul 2026, 08:06 UTC≈6,070 views7 reactionsread 28 August 2026
File

本次AI编写借助到的Skills 这是 Google Android 官方推出的 AI Agent Skills 包,专门用于帮助 AI(如 Claude、Gemini、Cursor 等)更好地开发 Android APK 应用 这个skills更新频率挺高的。 ▷ Github地址 ◁ #Skills #Android

😍61

19 Jul 2026, 07:57 UTC≈5,690 views10 reactionsread 28 August 2026
File

【一个安卓端的MCP工具箱】 花了一个小时用AI写的,有着60+的MCP工具。 使用过程中遇到的问题可在本帖下方进行反馈 现在的A用来I做一些小功能的软件很实用,大大降低了编程门槛,本次使用到的构建工具为Android Code Studio MCP_Run 是一款运行在 Android 设备上的 MCP(Model Context Protocol)协议服务器。 它采用 Streamable HTTP 传输协议,绑定 127.0.0.1 本地回环地址,让Rikkahub 等 MCP 客户端能够通过标准协议调用你手机的各类系统能力。 (文本介绍也是AI写的😋) ▷ 软件源码 ◁ ▷ Skills ◁ #Android #MCP

7🎉2😍1

27 Jun 2026, 10:14 UTC≈7,800 views10 reactionsread 28 August 2026
Photo

MT管理器最新版更新了MCP功能,体验了一下,还是挺好用的,适合小白,一键连接本地Agent,并且支持局域网 之前在自己手机上用Termux简单搭建了一个只用来访问处理本地文件,没有MT的APK MCP这么多功能,平时用来处理一些文件,写一些小功能的apk还是很有帮助的😋 如果你也想体验,下载MT管理器最新版,点侧边栏的APK MCP功能项,右上角的帮助手册,里面写的很详细,手机端的Agent工具推荐RikkaHub 如果遇到问题,可以在本帖下方留言 (遇到报错,功能不懂的问一下AI基本都能知道答案,如果想要自己搭建MCP,国内的各种视频网站搜索一下就有很多参考示例) #杂谈

8🥰2

Showing the 12 most recent of 22 posts we hold for @PAOLU_GGG. 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 — 198,044 of 1,628,524entries 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.

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

Named by 1 registered channel — 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.

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

“Run资源分享频道” (@PAOLU_GGG), 9,171 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/PAOLU_GGG.

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.