Photo, posted without a caption

Channel
太阳神【TG引流一站式服务】
@fenjinpd
On this record: Topic · Growth · Engagement · Posts · Posts edited after publishing · Citations · Cite this entry
10,454subscribers
-810 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1002416505463 |
|---|---|
| Type | Channel |
| Username | @fenjinpd |
| Created | 20 December 2024 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 37 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/fenjinpd |
Topic
Marketing & affiliate — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 67% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Oct 2026, 21:16 | 10,454 | -76 |
| 8 Oct 2026, 06:39 | 10,530 | -104 |
| 3 Oct 2026, 20:42 | 10,634 | -133 |
| 25 Sept 2026, 03:19 | 10,767 | -37 |
| 17 Sept 2026, 09:18 | 10,804 | -2 |
| 15 Sept 2026, 09:20 | 10,806 | -2 |
| 13 Sept 2026, 19:15 | 10,808 | -9 |
| 12 Sept 2026, 01:58 | 10,817 | -34 |
| 9 Sept 2026, 16:56 | 10,851 | -7 |
| 6 Sept 2026, 12:39 | 10,858 | -16 |
| 4 Sept 2026, 05:15 | 10,874 | -9 |
| 2 Sept 2026, 15:04 | 10,883 | -32 |
| 1 Sept 2026, 11:46 | 10,915 | -4 |
| 31 Aug 2026, 08:12 | 10,919 | -7 |
| 30 Aug 2026, 08:58 | 10,926 | -16 |
| 29 Aug 2026, 05:46 | 10,942 | -6 |
| 28 Aug 2026, 08:56 | 10,948 | -8 |
| 27 Aug 2026, 08:12 | 10,956 | -8 |
| 26 Aug 2026, 07:11 | 10,964 | -12 |
| 25 Aug 2026, 08:56 | 10,976 | first reading |
Engagement
4 posts held, back to 20 December 2024 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 38 pages of 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 4 posts for this entry, the most recent from 30 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
😃置顶业务列表主营业务点击跳转!!! ❶【TG引流】 TG引流私信/群发引流/强拉活人 ❷【TG号售卖】 TG号/直登号/api/老号批发零售 ❸【TG等多平台源头刷粉网】 TG业务:僵尸粉/浏览量/群在线粉/刷点赞表情/bot启动/ADS消耗/频道评论/投票/封禁举报/会员助推 ④【TG搭建BOT/网页脚本】 承接一切定制bot脚本搭建服务项目 ⑤【老频道/老群组出售】 自选年份带帖子/无帖子 老频道/老群组购买赠送1000僵尸粉 ⑥【群发静态ip】 无限流量/月 自助网站支持续费选购~ ⑦【TG生态商铺】 Socks私人代理/ESIM流量卡/TG账号专卖/小火箭节点 ■私密群发采集🤖:@caijipdbot 全网抓取供需公群帖子优质群发链接 ■公开群发采集🤖:@souchaxbot 爬全网知名索引数据库自带过滤系统 【5年引流经验 总押30W 信誉保证】
当您在使用产品时遇困惑当您对服务有建议客户服务中心始终是您的“即时响应站” 我们覆盖[TG引流/刷粉/协议号/搭建机器人/老群频道/群发器/群发ip/筛选脚本/采集器/会员代开/星星兑换/能量租赁]等多渠道服务响应站,7×[24]小时在线,售后投诉等24小时内反馈解决方案,无论是产品咨询、订单跟进,还是售后问题处理,都能为您提供清晰、高效的解答! 从需求倾听、问题定位到方案落地,我们始终以“解决您的问题”为核心,用耐心化解疑虑,用细致保障体验。选择太阳神,不仅是选择优质产品,更是选择一份“随时找得到靠得住”的服务承诺太阳神客户服务中心以专业,守护每一份信赖! 🥰总押30w持续加押 客服 @dede 🇸🇰天成押金2000U https://t.me/+FtNO75cT56M3NjY1 🇮🇶平安押金1000U https://t.me/+fNxyNJsMx88zMmYx 😃福利来押金2500U https://t.me/…
Channel created
Showing the 4 most recent of 4 posts we hold for @fenjinpd. 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.
Posts edited after publishing
@fenjinpd edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
- First edit seen
- 11 August 2026
- Most recent edit
- 18 August 2026
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.
Mentions
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.
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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“太阳神【TG引流一站式服务】” (@fenjinpd), 10,454 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/fenjinpd.
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.