📈💪 🟢 Купить токен BXTR 🥷 Chat Holders 🥷 🖤 @bxtrcoin

Channel
BAXTER
@BAXTERok
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
112subscribers
+1 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 | -1002238716004 |
|---|---|
| Type | Channel |
| Username | @BAXTERok |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/BAXTERok |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 09:57 | 112 | +1 |
| 9 Aug 2026, 06:47 | 111 | no change |
| 6 Aug 2026, 22:41 | 111 | first reading |
Engagement
18 posts held, back to 10 July 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 18 posts for this entry, the most recent from 26 October 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 42s
- Average length
- 21s
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
50 reactions across 9 posts, in 13 distinct kinds. The most used accounts for 14.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5303321455553963962 | 7 | 14.0% | |
| custom 5285428484359866875 | 6 | 12.0% | |
| custom 5294157382618728769 | 6 | 12.0% | |
| custom 5294059556148629720 | 4 | 8.00% | |
| 👍 | 4 | 8.00% | |
| custom 5283220686486130421 | 3 | 6.00% | |
| custom 5285082129607186772 | 3 | 6.00% | |
| custom 5303152826547985241 | 3 | 6.00% | |
| custom 5465184436339372102 | 3 | 6.00% | |
| 🔥 | 3 | 6.00% | |
| 😁 | 3 | 6.00% | |
| 🤝 | 3 | 6.00% | |
| ❤ | 2 | 4.00% |
Custom emoji. 8 of the rows above are 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 9 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 50reactions 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 10 July 2025 to 26 October 2025, 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
Проект временно заморожен ❄️ Переехали сюда BXTR 🟢
custom 52832206864861304213custom 53031528265479852413custom 53033214555539639623🔥1
Sticker, posted without a caption
custom 52854284843598668753custom 52940595561486297203custom 52941573826187287693👍1
🎁 Started Gifts Giveaway! Details: Subscribe: @cryptowpx, @whiterpro, @wpcoinx Deadline: 17.10.2025 08:17 UTC Rewards: Stellar Rocket #317 Requirements: • Only Premium Users Participants can now join this giveaway. Good luck!
custom 52850821296071867723🤝1
⚡ Больше 2000 крипто трейдеров покончили с собой из-за падении рынка 📉
Ракета 🚀 Купить на Blum 🥷 BAXTER • • CHAT 🥷 🪙Sol 📱 Хвиттер 📈 DYOR 💰Tonviewer 🥷 Tonscan
custom 52854284843598668752custom 52941573826187287692❤1😁1custom 54651844363393721021
Крупнейшая капитуляция в истории крипторынка 📉 За последние 24 часа с рынка вынесло 1 618 240 трейдеров, а общий объём ликвидаций достиг $19,13 млрд — такого не было даже во время краха FTX или ковидного обвала Ликвидировало буквально всех лонгистов — минута молчания в их честь Реальная сумма может быть ещё выше: Binance фиксирует только один ордер на ликвидацию в секунду, так что часть сделок просто не попадает в…
custom 53033214555539639622custom 52940595561486297201
🍷 Если Pump.Fun создаст форк, Solana потеряет свыше 20% активности. 📖По данным Coingecko, за последние 24 часа PumpFun обработал 7,63 млн транзакций (28,5% от 26,81 млн транзакций Solana). Согласно Jupiter, платформа занимает 90,7% рынка выпуска токенов Solana с торговым оборотом $946 млн и 391,000 торговых адресов. Это составляет 19% от общего DEX-оборота Solana ($4,97 млрд) и 17% от активных адресов (2,3 млн). 📖П…
🐸 Plush Pepe за 120 000 $ Пользователь @smash_direct продал свою Plush Pepe Cozy Galaxy на Getgems за 39 000 TON (≈118 820 $). — PlushPepe-1847 Ранее он купил её за 2000 Stars (=30 $) — чистая прибыль за 279 дней составила 118 790 $, или ≈396 000% от изначальной цены. 🥷@cryptowpx
Portals и их тех.поддержка (@portals_sup) Нам пишут: - ещё 12 августа были отправлены «десять» подарков на маркет, до сих пор в поддержке решают вопрос. А вот ракету #316 так же умудрились где-то перехватить и потерять с 2 сентября, тоже решают вопрос. Уровень маркета номер один 😁 Как думаете вернут подарки через несколько лет или вот-вот ща-ща @monk @borz 🤡
Будни трейдера 😎 🪙 Купить WP ❤️ Portals 🥷 WP chat 💲 Tonnel ⭐️ SPLIT 🤖 Полезные боты 🖼 MRKT 🖼 EarlyGifts
👍3
$BAXTER жив 📈🥷 Купить на Blum BAXTER • • CHAT 🥷 🪙Sol 📱 Хвиттер 📈 DYOR 💰Tonviewer 🥷 Tonscan
❤1custom 52854284843598668751custom 53033214555539639621custom 54651844363393721021
Showing the 12 most recent of 18 posts we hold for @BAXTERok. 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 — 676,363 of 1,176,251entries 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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 3 registered channels — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
“BAXTER” (@BAXTERok), 112 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/BAXTERok.
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.