Telegram RegisterThe public register of Telegram
Telegram profile photo for 国际部 @GuoJiBu

Channel

国际部 @GuoJiBu

@GuoJiBu

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

377subscribers

-329 since we began measuring on 9 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003771171316
TypeChannel
Username@GuoJiBu
CreatedBetween 1 February 2026 and 5 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live19 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/GuoJiBu

Topic

Other / unclassifiable — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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

377706541.59 August 2026 — 706 subscribers9 August 2026 — 706 subscribers17 August 2026 — 654 subscribers25 August 2026 — 526 subscribers1 September 2026 — 445 subscribers10 September 2026 — 415 subscribers19 September 2026 — 377 subscribers9 August 202619 September 2026
7 measurements spanning 41 days, net -329. 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 328–755 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 08:59377-38
10 Sept 2026, 22:01415-30
1 Sept 2026, 03:26445-81
25 Aug 2026, 01:58526-128
17 Aug 2026, 13:28654-52
9 Aug 2026, 15:33706no change
9 Aug 2026, 11:02706first reading

Engagement

12 posts held, back to 5 July 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 1 page 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 12 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
39s
Average length
39s

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 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤4100.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 2 of the 12 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 12 most recent posts we hold, published 5 July 2026 to 6 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

6 Aug 2026, 19:00 UTC43 viewsread 9 August 2026
Photo

如提示您当前的 Telegram 版本不支持此消息请更新至最新版本的可以请查看此图片

2 Aug 2026, 07:08 UTC113 viewsread 9 August 2026
Photo

📣【招商】诚寻电销团队长、散人、学生团长期合作! 🔥一手通道,独立后台,费率全网可查。 💰不扣量、不跑路、日结秒结。 🚀自带团队有经验者优先,扶持团队月入10W+。 合作共赢,非诚勿扰!

11 Jul 2026, 15:09 UTC317 viewsread 9 August 2026

话术有简单有复杂 女话务优先来 价格美丽 欢迎咨询

11 Jul 2026, 15:04 UTC327 viewsread 9 August 2026
Photo

嫌手机口风险高?快递通知单通过率低?微信IM单价压得太狠?那就来试试我们的 电话回访单 ↗️ 接通率稳在95%+,告别通知单"石沉大海" 💰 单价合理,不用在低价里卷生卷死,让月入上万不再是口号。 达利878公群 🔗 https://t.me/+03mdjh2y1AVlOTQ1 唯一业务员 💬 @xiaoxicaifang 结账记录 💳 https://t.me/Shekimany 猪脚饭聊天群 🍛 https://t.me/+O8J4FTMNZAFhMmM1

11 Jul 2026, 01:31 UTC235 views1 reactionsread 9 August 2026
Photo

此账号不是我本人 账号只有 @xiaoxicaifang @living44 请勿上当受骗

❤1

9 Jul 2026, 01:00 UTC310 viewsread 9 August 2026
Photo

嫌手机口风险高?快递通知单通过率低?微信IM单价压得太狠?那就来试试我们的 电话回访单 ↗️ 接通率稳在95%+,告别通知单"石沉大海" 💰 单价合理,不用在低价里卷生卷死,让月入上万不再是口号。 达利878公群 🔗 https://t.me/+03mdjh2y1AVlOTQ1 唯一业务员 💬 @xiaoxicaifang 结账记录 💳 https://t.me/Shekimany 猪脚饭聊天群 🍛 https://t.me/+O8J4FTMNZAFhMmM1

6 Jul 2026, 12:37 UTC317 views3 reactionsread 9 August 2026
Video

通知单项目(接通就算,纯捡钱) 1.准备两台手机,一台打电话,一台拍打电话的手机。 2.口齿清晰,说话礼貌不坑坑巴巴。 3.接通以后念话术,念完以后等对面回复,他说任何问题一律回复上线联系客服就行,确认对面没问题了再说祝你生活愉快再见。 大量收 男 女话务 散团 能吃量的联系我拉群 接通就算 不会做的 手把手教会,双向联系机器人:@xisxsxbot,我来找你

❤3

Showing the 12 most recent of 12 posts we hold for @GuoJiBu. 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.

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

“国际部 @GuoJiBu” (@GuoJiBu), 377 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/GuoJiBu.

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.