Telegram RegisterThe public register of Telegram
Telegram profile photo for 晴天社区&加密货币订阅频道

Channel

晴天社区&加密货币订阅频道

@qingtian_btc

On this record: Growth · Engagement · Reactions · Posts · Cite this entry

1,982subscribers

+7 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001620723854
TypeChannel
Username@qingtian_btc
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 10 September 2026
On Telegramt.me/qingtian_btc

Growth

1,9711,9831,9777 August 2026 — 1,975 subscribers7 August 2026 — 1,975 subscribers11 August 2026 — 1,976 subscribers14 August 2026 — 1,977 subscribers17 August 2026 — 1,975 subscribers20 August 2026 — 1,982 subscribers24 August 2026 — 1,981 subscribers27 August 2026 — 1,980 subscribers30 August 2026 — 1,979 subscribers2 September 2026 — 1,971 subscribers5 September 2026 — 1,983 subscribers10 September 2026 — 1,982 subscribers1,9827 August 202610 September 2026
12 measurements spanning 34 days, net +7. 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 1,969–1,985 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 15:361,982-1
5 Sept 2026, 22:391,983+12
2 Sept 2026, 06:461,971-8
30 Aug 2026, 03:461,979-1
27 Aug 2026, 07:531,980-1
24 Aug 2026, 04:031,981-1
20 Aug 2026, 12:131,982+7
17 Aug 2026, 15:551,975-2
14 Aug 2026, 18:141,977+1
11 Aug 2026, 01:171,976+1
7 Aug 2026, 20:031,975no change
7 Aug 2026, 16:471,975first reading

Engagement

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

Reaction mix

12 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 58.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
758.3%
👍433.3%
👏18.33%

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 6 of the 18 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 12 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 16 July 2026 to 7 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

7 Aug 2026, 02:42 UTC141 viewsread 7 August 2026

https://x.com/qingtianbtc/status/2085556587075420304?s=20

5 Aug 2026, 02:47 UTC225 views2 reactionsread 7 August 2026

https://x.com/qingtianbtc/status/2084833458426384652?s=20

2

4 Aug 2026, 03:36 UTC289 viewsread 7 August 2026

https://x.com/qingtianbtc/status/2084483554247926164?s=20

3 Aug 2026, 03:39 UTC311 viewsread 7 August 2026

https://x.com/qingtianbtc/status/2084121774137258134?s=20

1 Aug 2026, 08:32 UTC383 views1 reactionsread 7 August 2026
Photo

每个月1号雷打不动给大家发工资 币安现在老用户也可以获得返佣,如果你没绑定返佣,只要90天不交易就能绑定,符合条件用下面链接就能绑

👏1

31 Jul 2026, 05:23 UTC361 views1 reactionsread 7 August 2026

https://x.com/qingtianbtc/status/2083061015403782263?s=20

1

27 Jul 2026, 02:52 UTC465 views3 reactionsread 7 August 2026

https://x.com/qingtianbtc/status/2081573398820552806?s=20

3

21 Jul 2026, 02:24 UTC445 views1 reactionsread 7 August 2026

https://x.com/qingtianbtc/status/2079391958724980958?s=20

1

Showing the 12 most recent of 18 posts we hold for @qingtian_btc. 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 10 September 2026 — this entry's latest reading, not the date you are reading this.

“晴天社区&加密货币订阅频道” (@qingtian_btc), 1,982 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/qingtian_btc.

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.