Telegram RegisterThe public register of Telegram
Telegram profile photo for 星河001通知频道

Channel

星河001通知频道

@fv088

2 usernames

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

2,500subscribers

-132 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1002231028806
TypeChannel
Usernames@fv088 @xinhe080
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live19 September 2026
Measurements held13
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/fv088

Topic

Ecommerce storefront — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 86% 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

2,5002,6322,56612 August 2026 — 2,632 subscribers12 August 2026 — 2,629 subscribers15 August 2026 — 2,620 subscribers18 August 2026 — 2,604 subscribers21 August 2026 — 2,598 subscribers24 August 2026 — 2,579 subscribers27 August 2026 — 2,575 subscribers30 August 2026 — 2,563 subscribers3 September 2026 — 2,540 subscribers7 September 2026 — 2,527 subscribers11 September 2026 — 2,518 subscribers15 September 2026 — 2,515 subscribers19 September 2026 — 2,500 subscribers12 August 202619 September 2026
13 measurements spanning 38 days, net -132. 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 2,480–2,652 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 11:202,500-15
15 Sept 2026, 08:572,515-3
11 Sept 2026, 22:172,518-9
7 Sept 2026, 19:382,527-13
3 Sept 2026, 00:542,540-23
30 Aug 2026, 13:572,563-12
27 Aug 2026, 16:042,575-4
24 Aug 2026, 16:272,579-19
21 Aug 2026, 10:052,598-6
18 Aug 2026, 15:122,604-16
15 Aug 2026, 20:242,620-9
12 Aug 2026, 16:572,629-3
12 Aug 2026, 12:482,632first reading

Engagement

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

Recent posts

11 Aug 2026, 18:44 UTC74 viewsread 12 August 2026
Photo

每天不定时补货 全网美卡质量天花板 📱📱 xinhe001.lol/shop/

9 Aug 2026, 15:11 UTCviews —

星河001通知频道 pinned «https://smsapis.com/api/get_sms 链接不来码的每天凌晨12点准时来 中午12点后就会停 理解一下很快就会恢复正常 网站有很多其他链接的号子正常使用»

9 Aug 2026, 15:10 UTC126 viewsread 12 August 2026

https://smsapis.com/api/get_sms 链接不来码的每天凌晨12点准时来 中午12点后就会停 理解一下很快就会恢复正常 网站有很多其他链接的号子正常使用

7 Aug 2026, 06:10 UTC200 viewsread 12 August 2026

https://smsapis.com/api/get_sms? 这个链接开头不来码的晚点试试 是正常风控

6 Aug 2026, 18:29 UTC206 viewsread 12 August 2026

重点:【上号建议】 1、安卓要双清刷机 苹果要多清几次 但是苹果不太容易清理干净 (可网上自行找机型教程 别再用非洲设备上号了) 不然QQ易死难上 2、账号不要切换,不要频繁搜其他Q号 3、QQ号有带地区的用爱加速跳转对应IP上号更稳

6 Aug 2026, 18:29 UTC182 viewsread 12 August 2026
Photo

网站补了一些 每天都在不定时补货中 永久不断货 量大可私信我 一切用号要求都能满足 网站 xinhe001.lol/shop/

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

“星河001通知频道” (@fv088), 2,500 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/fv088.

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.