不要问在不在,一直营业中,欢迎来盘!😀😀

Channel
引流矩阵|社媒引流|群控采集|社媒矩阵管理软件
@PG_45brcom
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
14,298subscribers
-2,260 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 | -1001690864989 |
|---|---|
| Type | Channel |
| Username | @PG_45brcom |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 30 October 2026 |
| Measurements held | 53 |
| Confirmed unchanged | 1 time, most recently 30 October 2026 |
| On Telegram | t.me/PG_45brcom |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Oct 2026, 02:17 | 14,298 | -21 |
| 29 Oct 2026, 02:01 | 14,319 | -22 |
| 27 Oct 2026, 22:21 | 14,341 | -42 |
| 26 Oct 2026, 20:47 | 14,383 | -19 |
| 25 Oct 2026, 19:25 | 14,402 | -34 |
| 24 Oct 2026, 20:50 | 14,436 | -18 |
| 23 Oct 2026, 23:46 | 14,454 | -23 |
| 23 Oct 2026, 01:08 | 14,477 | -28 |
| 22 Oct 2026, 01:26 | 14,505 | -32 |
| 20 Oct 2026, 19:09 | 14,537 | -12 |
| 19 Oct 2026, 21:44 | 14,549 | -11 |
| 19 Oct 2026, 00:26 | 14,560 | -23 |
| 17 Oct 2026, 23:19 | 14,583 | -42 |
| 17 Oct 2026, 02:37 | 14,625 | -23 |
| 16 Oct 2026, 02:27 | 14,648 | -26 |
| 14 Oct 2026, 23:50 | 14,674 | -29 |
| 13 Oct 2026, 15:00 | 14,703 | -91 |
| 9 Oct 2026, 14:22 | 14,794 | -144 |
| 5 Oct 2026, 05:16 | 14,938 | -169 |
| 28 Sept 2026, 11:38 | 15,107 | first reading |
Engagement
8 posts held, back to 10 April 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 53 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 8 posts for this entry, the most recent from 1 September 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 1m 37s
- Average length
- 1m 37s
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.
Reaction mix
4 reactions across 4 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 100.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 4 of the 8 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 10 April 2026 to 1 September 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
需要联系客服: @vipy66666
❤1
💠Facebook 换全新版本 修复FB新界面 推荐定位 帖子 小组等功能: 1️⃣ 增加 好友筛选直发消息 2️⃣ 增加 好友定位筛选条件 3️⃣ 增加 好友筛选地区条件 4️⃣ 增加 主页帖@好友功能
Photo, posted without a caption
❤1
❗️大家做号时出现红字,明确告诉你们是风控IP(也就是机场问题,换节点或者机场!!), ❗️目前一般的机场,大概率只有香港和台湾节点可以;这个要你们自己多测机场, ❗️机场有测试就先测试,没测试买最低配就行 ,可以百度 谷歌 YouTube 搜 — iplc iepl机场, ❗️自己多测试,不要一个机场用不了了,就说不行了!不要去买打广告的 ,一般是坑的多! 【官方工作室】: @vipy66666
❤1
Photo, posted without a caption
两天引粉效果! #facebook引流软件
❤1
欧洲老户新户不限品、大量供应中 👉👉下户快、充值快👈👈 👉👉户超稳👈👈 联系客服: @vipy66666
Showing the 8 most recent of 8 posts we hold for @PG_45brcom. 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.
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 30 October 2026 — this entry's latest reading, not the date you are reading this.
“引流矩阵|社媒引流|群控采集|社媒矩阵管理软件” (@PG_45brcom), 14,298 subscribers as measured 30 October 2026. Telegram Register, tgregister.com/channel/PG_45brcom.
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.