Telegram RegisterThe public register of Telegram

Channel

ANDY中文区推特新闻

@ANDYchinese

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Declared links · Cite this entry

568subscribers

+0 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002268470289
TypeChannel
Username@ANDYchinese
Description📲 Official App: @andybsc_bot 0x01CA78a2B5F1a9152D8A3A625bd7dF5765eeE1D8 https://x.com/andybsctoken https://t.me/andyonbsctoken https://www.andytoken.com/
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/ANDYchinese

Growth

5688 Aug 2026, 03:18 — 568 subscribers8 Aug 2026, 03:32 — 568 subscribers8 Aug 2026, 03:188 Aug 2026, 03:32
2 measurements taken within a single day. 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 567–569 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 03:32568no change
8 Aug 2026, 03:18568first reading

Engagement

19 posts held, back to 5 October 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 pageof 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 2 November 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
611
Videos
65
Links
695

Lifetime counters from Telegram’s own channel header, read 8 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

2 Nov 2025, 11:19 UTC69 viewsread 8 August 2026
Photo

ANDY ON BSC (Twitter) RT @andyonbscarmy: Keep on believing and never give up... $Andy is the ticker!

23 Oct 2025, 11:11 UTC25 viewsread 8 August 2026

‌ANDY ON BSC (Twitter) ‼️Partnership Reveal: ANDY x dMarketplace ($DMP) Two major forces unite 🤝 ANDY AI + EDU-FI innovator from the Boys Club realm dMarketplace ($DMP) the AI-powered Web3 commerce ecosystem Together, they’re merging AI, education, and real-world crypto utility to drive mass adoption across BNB Chain. 🛍️ $ANDY Merch Now Live on dMarketplace! 🔥 Phone Cases, Laptop Sleeves, Tees, Hoodies, Caps Limit…

18 Oct 2025, 02:03 UTC23 viewsread 8 August 2026
Photo

ANDY ON BSC (Twitter) Community too strong. Energy unmatched. Chart looking spicy. Love you all. 💛

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

Citation-graph rank

Citation-graph rank — 1,015,304 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

神之鞭
@GodsofWhip · 8874 posts

Names

Channels on the register whose handles appear in this channel's posts.

BNB Chain
@bnbchain · 76,3391 postdMarketplace - Portal
@dMarketplaceAI · 1161 post

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

“ANDY中文区推特新闻” (@ANDYchinese), 568 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/ANDYchinese.

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.