Telegram RegisterThe public register of Telegram
Telegram profile photo for 亚瑟业务合作

Channel

亚瑟业务合作

@Jiu87up

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

99subscribers

-4 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1001650277444
TypeChannel
Username@Jiu87up
CreatedBetween 1 December 2021 and 31 May 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live13 October 2026
Measurements held7
Confirmed unchanged1 time, most recently 13 October 2026
On Telegramt.me/Jiu87up

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 27 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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

9910310114 August 2026 — 103 subscribers15 August 2026 — 102 subscribers23 August 2026 — 101 subscribers30 August 2026 — 100 subscribers9 September 2026 — 99 subscribers3 October 2026 — 100 subscribers13 October 2026 — 99 subscribers14 August 202613 October 2026
7 measurements spanning 60 days, net -4. 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 98–104 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Oct 2026, 13:1999-1
3 Oct 2026, 14:17100+1
9 Sept 2026, 05:5899-1
30 Aug 2026, 22:05100-1
23 Aug 2026, 06:33101-1
15 Aug 2026, 19:16102-1
14 Aug 2026, 10:01103first reading

Engagement

19 posts held, back to 26 December 2024 — 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 19 posts for this entry, the most recent from 1 April 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
37s
Average length
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

3 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍3100.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 19 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 3 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 26 December 2024 to 1 April 2025, 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

1 Apr 2025, 01:17 UTC≈1,650 viewsread 14 August 2026
Photo

🩵被销号后的阴影一直心底压抑着,一直聊天焦虑,每天打开软件就是担心再次被销号,号没了资源没了,我更担心目前在合作的伙伴在没有我其他备用联系方式的情况下联系不到我,从而误解为我跑路。 🩵鉴于以上情况,解决办法为启用 @Banshiren 永久用户名 ,(永久用户名存在于Ton钱包里,属于匿名财产/永久资产,虽说也有被销号的风险,但可以用钱包恢复用户名。)比较好记,办事人的拼音。 我的微信昵称也叫办事人, 宗旨是: 受人之托,忠人之事,办事人为您服务。💛 🥰🥰🥰: @BanShiRen 🥰🥰🥰: @Yaseup 😚😚: @Yase_up

31 Mar 2025, 10:05 UTC≈1,360 viewsread 14 August 2026

最近生活琐事太多,烦死了 新渠道那边也是谈了一个月才谈妥,招待费都花光了我的小金库。 明天开工,云搜限量收,隔天回单 不熟的拉担保或过账报单,价格优势,详询💛 这么久了都知道我人是怎么做的,不差事,但就是没钱闹的,之前总拖我第二天结账,我也很难做,老客户结账慢的也不收。

17 Mar 2025, 13:45 UTC≈1,390 viewsread 14 August 2026

回来了,准备研究换个业务方向,重新整理业务内容,来单来单 😚😚: @Yase_up

11 Mar 2025, 06:18 UTC≈1,390 viewsread 14 August 2026

源头直收 (网安出单) ☝️✋🤚🫰 QQ/微信/小红书/哔哩哔哩/soul/钉钉/YY 反查现绑手机号+身份证 注意⚠️: 有手机号给手机号,有身份证给身份证,如果都有就都给。 网安系统进行分析绑定人使用人

4 Mar 2025, 13:07 UTC≈1,330 viewsread 14 August 2026

🩵低端客户全面诠释: 不是穷客户,也不是低价客户,而是只花1块钱,想买2块钱的产品,实现3块钱的效果,享受4块钱的服务,去吹5块钱的牛逼,还要拼命挑毛病,想抵赖掉5毛钱的尾款,再拿2块钱的赔偿 🩵高端客户诠释: 高端客户不是他有钱没钱,而是他认可并愿意花钱去买你的产品与服务。 有些人虽然有钱,但是他就觉得你五块钱的东西只值三块钱,有些人虽然没钱,但是他就觉得你的五块钱的产品值五块钱,甚至值六块七块钱,并且愿意花五块钱去买你的产品 同样一件事,我用的服务方式都是一样的, 同一件事我讲完了所有细节还是没有成交, 同一件事我讲到一半就已经成交了,也省去了很多精力。 我的顾客不区分穷人和富人,他们都是认可我的人,即使拿低价去翘你也不一定能翘走,时间会见证一切 知道你价值的人都是高端用户,不分穷人富人, 不知道你价值的就是低端用户,不分穷人富人

21 Feb 2025, 18:18 UTC≈1,290 viewsread 14 August 2026
Photo

做人,当铭记根本: 不忘恩,是心的温度;不负义,是行的准则。 过河念搭桥之恩,饮水思挖井之情 ,这是做人的本分,更是不可破的规矩。 今天气的失眠,天天劝别人心平气和,到我自己身上就做不到了, 一堆收不上钱的,大账小账总是拖,可我这每次都要全额给渠道结算, 刚才统计了一下,欠款的都是靠谈感情的, 不管了,总之以后散单看心情接,(现在主要对接的就是同行,只有一手业务才有做的心情,) 最起码的要清帐之后再接新单了,我理解你们,你们是真不帮我! 估计你们都没见过业务退款不扣欠款的,让你们见识见识!

7 Feb 2025, 18:03 UTC≈1,230 viewsread 14 August 2026
Photo

😚🧐😁🤪🤪😘🤩☺️🤭🫡 🥰🥰🥰: @Yase_up

30 Jan 2025, 03:15 UTC≈1,330 viewsread 14 August 2026

带头云搜不限量收单, 不熟的拉担保或过账报单💛 项目全开

27 Jan 2025, 18:19 UTC≈1,360 viewsread 14 August 2026

休息两天,30号正常收单,稳定当天隔天回单💛目前一手稳定项目 节后暂定发车回单时间: 工作日下午三点发车,晚九点左右回单 过发车时间的话,我能加就加,加不进去就赶隔天的车。 特殊规则:发车不撤,也不能撤,耐心等,最晚隔天回单。 特殊情况我会特殊私信通知。

25 Jan 2025, 01:12 UTC≈1,390 viewsread 14 August 2026

🩵 带头云搜 ✅在逃违法犯罪一体 ✅吸毒史/失信人 ✅驾驶证/机构法人 ✅名下车/出入境证件 🩵 16头猎魔开/同行询价 已经测试三天,稳定当天隔天回单 (上午的单当天晚上回,下午的单隔天晚上回) 下午3-5点发车,晚10点前回单 🥰🥰🥰: @Yase_up

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

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

“亚瑟业务合作” (@Jiu87up), 99 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/Jiu87up.

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.