Telegram RegisterThe public register of Telegram
Telegram profile photo for Cheque Centre

Channel

Cheque Centre

@xUSDBot

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

6,652subscribers

-303 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002298260142
TypeChannel
Username@xUSDBot
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 live30 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/xUSDBot

Growth

6,6526,9556,803.58 August 2026 — 6,955 subscribers8 August 2026 — 6,955 subscribers8 August 2026 — 6,942 subscribers11 August 2026 — 6,885 subscribers15 August 2026 — 6,837 subscribers18 August 2026 — 6,791 subscribers21 August 2026 — 6,768 subscribers25 August 2026 — 6,725 subscribers27 August 2026 — 6,694 subscribers30 August 2026 — 6,652 subscribers8 August 202630 August 2026
10 measurements spanning 22 days, net -303. 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 6,607–7,000 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 11:276,652-42
27 Aug 2026, 20:476,694-31
25 Aug 2026, 05:436,725-43
21 Aug 2026, 18:376,768-23
18 Aug 2026, 18:236,791-46
15 Aug 2026, 09:176,837-48
11 Aug 2026, 13:136,885-57
8 Aug 2026, 15:226,942-13
8 Aug 2026, 11:006,955no change
8 Aug 2026, 10:566,955first reading

Engagement

21 posts held, back to 29 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 8 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
1.17%
avg views ÷ 6,652 subscribers
Avg views / post
78.0
1 post measured
Reaction rate
11.5%
reactions ÷ views · ER floor
Posts in window
1
of 21 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 August 2026
Posts held21 (29 May 202611 August 2026)
Views total78
Reactions total9
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken20 Aug 2026, 04:28 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

343 reactions across 20 posts, in 20 distinct kinds. The most used accounts for 32.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
11132.4%
🖕4112.0%
🤣4112.0%
👍298.45%
😁288.16%
🤬185.25%
🔥144.08%
🤡123.50%
👀92.62%
💋92.62%
🍌51.46%
🤨51.46%
🥰51.46%
👏41.17%
🙏41.17%
👎30.875%
🫡20.583%
🆒10.292%
🌭10.292%
💯10.292%

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

Measured over the 21 most recent posts we hold, published 29 May 2026 to 11 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

1 Jun 2026, 01:50 UTC379 views18 reactionsread 20 August 2026

Good morning 🌞😴🌄

🖕7🤨5💋4🌭1🆒1

31 May 2026, 08:36 UTC944 views19 reactionsread 20 August 2026

💰 Рыночный ордер #230607545 на покупку BNB 🪙 был исполнен по цене 4885.68637184 USDT 🪙 😁 Итого получено: 6.70207801 BNB 🪙 🪙 Средний курс: 722.42000000 USDT 🪙 🥹 Ставка комиссии: 0,00%

🖕9🔥4😁42

30 May 2026, 13:28 UTC≈1,920 views50 reactionsread 20 August 2026

Ducks from Bangladesh with fake members are exhausting our check capacity.🤬

😁17🤣14🤡5🤬5🍌4👍31🖕1

29 May 2026, 21:04 UTC≈5,350 views20 reactionsread 20 August 2026

https://t.me/TradeTON?start=Cheque-GAMl30qmQXi

🤬9🤡7😁21🖕1

29 May 2026, 20:23 UTC≈5,080 views24 reactionsread 20 August 2026

https://t.me/boost/xUSDBot Boost our channel :)

🤣15💋5🥰3🖕1

29 May 2026, 20:08 UTC≈4,480 views11 reactionsread 20 August 2026

Cooperation proposal to create joint cheque is accepted. If you are a group or channel administrator, you can create a joint cheque with us.

🔥82🍌1

29 May 2026, 19:57 UTC≈3,900 views38 reactionsread 20 August 2026

Maybe we should post your checks for free at @xUSDBot?? 🙂‍↕️

23👀9🤬4💯1🖕1

29 May 2026, 19:56 UTC≈3,260 views23 reactionsread 20 August 2026

Maybe you should start a giveaway?

👍184🖕1

Showing the 12 most recent of 21 posts we hold for @xUSDBot. 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 — 999,072 of 1,627,068entries 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.

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

“Cheque Centre” (@xUSDBot), 6,652 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/xUSDBot.

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.