Telegram RegisterThe public register of Telegram
Telegram profile photo for XBT

Channel

XBT

@xbt001

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

300subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001336629522
TypeChannel
Username@xbt001
Created6 August 2018measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/xbt001

Growth

299300299.56 August 2026 — 300 subscribers6 August 2026 — 300 subscribers7 August 2026 — 299 subscribers14 August 2026 — 300 subscribers6 August 202614 August 2026
4 measurements spanning 8 days. 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 299–300 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 14:38300+1
7 Aug 2026, 02:58299-1
6 Aug 2026, 22:32300no change
6 Aug 2026, 07:26300first reading

Engagement

17 posts held, back to 2 August 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
10.1%
avg views ÷ 300 subscribers
Avg views / post
30.3
17 posts measured
Reaction rate
6.99%
reactions ÷ views · ER floor
Posts in window
17
of 17 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. It is computed over the 8 of 17 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held17 (2 August 20266 August 2026)
Views total515
Reactions total19
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 22:32 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

19 reactions across 6 posts, in 4 distinct kinds. The most used accounts for 42.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5285132037127152291842.1%
custom 5213447602732813642631.6%
custom 5235672194473794817421.1%
custom 583452925131070276415.26%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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

Measured over the 17 most recent posts we hold, published 2 August 2026 to 6 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

6 Aug 2026, 13:18 UTC15 viewsread 6 August 2026
Photo

GC H4 Нужно смотреть на реакцию от текущей области Пока в общем идет резкое восходящее движение, но сейчас цена зажата между областей

5 Aug 2026, 13:56 UTC19 viewsread 6 August 2026
Photo

GC H4 / m30 Сформировалась еще одна область для входа Но сейчас будут новости, так что алярма

5 Aug 2026, 11:02 UTC22 viewsread 6 August 2026
Photo

GC m30 4209 область для потенциальных покупок Посмотрим, будут ли условия для входа

5 Aug 2026, 10:42 UTC23 views2 reactionsread 6 August 2026
Photo

GC H4 / m30 Цена тестирует FVG H4, потенциальная цель 4253 На м30 картина в пользу покупок, но пока нет подходящей области для возможного входа Отмена лонгов - закрытие ниже 4145

custom 52851320371271522912

5 Aug 2026, 10:00 UTC23 views0 reactionsread 6 August 2026

Цена сейчас не у зоны, а у цели. 4232 это пул ликвидности сверху (BSL), старые хаи Входить в лонг здесь = покупать прямо под ликвидностью, которую цена пришла забрать Продавать сейчас = продавать в зону дисбаланса

4 Aug 2026, 08:08 UTC41 views2 reactionsread 6 August 2026
Photo

Да и утро началось с тейка по золоту, чисто 1к2 половиной объема Первая сделка на пропе, хотелось сразу выйти в профитную зону. Так что теперь у меня есть бесплатный риск на одну сделку

custom 52851320371271522911custom 58345292513107027641

3 Aug 2026, 21:04 UTC47 views9 reactionsread 6 August 2026

Ура, я все вывел Уругвайский план сработал

custom 52851320371271522915custom 52134476027328136424

3 Aug 2026, 09:55 UTC43 viewsread 6 August 2026
Photo

Я не брал, в моменте выглядело как будто не особо надежно, хотелось увидеть еще какое-то подтверждение

3 Aug 2026, 08:53 UTC41 viewsread 6 August 2026

H4 Цена сделала свип хая сверху, забрала ликвидность, и пошла вниз формируя имбаланс. Дошла до первого таргета - фрактала Н4, оформила там ложный пробой лоя, развернулась. Текущее восходящее движение перекрыло шортовый FVG полностью - поглощение имбаланса, покупатели вернули контроль. Приоритет лонг, но свеча закрылась с фитилем сверху, значит на 4140-4160 кто-то продает. Пока цена не закрылась выше 4160, приоритет

Showing the 12 most recent of 17 posts we hold for @xbt001. 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 — 532,058 of 1,480,944entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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

“XBT” (@xbt001), 300 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/xbt001.

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.