股票 盈透证券(Interactive Brokers)股票交易数据 - 75万
Channel
德国
@blao00020
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
9subscribers
+0 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002586935085 |
|---|---|
| Type | Channel |
| Username | @blao00020 |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 2 |
| On Telegram | t.me/blao00020 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 16:31 | 9 | no change |
| 13 Aug 2026, 16:18 | 9 | first reading |
Engagement
18 posts held, back to 15 November 2025 — 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 18 posts for this entry, the most recent from 28 December 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 186
- Links
- 35
Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Recent posts
财富管理 顶级本土私人银行财富管理集团(MetzlerPrivateBank) - 643万
银行 国际私人银行(UBSDeutschland) - 656万
求职 求职数据 - 477万
车主 车主信息 - 389万
信用卡 信用卡用户 - 394万
股票 证券 股票盈透证券IBKR股票经纪账户条含余额(大于5万欧) - 52万
银行 金融 德意志银行(Deutsche Bank AG)金融产品投资数据 - 73万
德国 银行 Volksbank 储蓄 与 投资 类 账户 数据 - 65万 已筛选 优质 数据
德国 德意志交易所(Deutsche Börse) 贵金属( 黄金 白银 钯金 铂金 ) 投资 数据 - 73万
德国(HugoBoss) 高消费 奢侈品 服装 个人 信息 - 829万
德国(Wempe) 顶级 珠宝 腕表 个人 关注 用户 - 870万
Showing the 12 most recent of 18 posts we hold for @blao00020. 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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“德国” (@blao00020), 9 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/blao00020.
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.