Telegram RegisterThe public register of Telegram
Telegram profile photo for Шилим Сумки 🐋

Channel

Шилим Сумки 🐋

@sharpbags

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

5,601subscribers

-64 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001430139857
TypeChannel
Username@sharpbags
CreatedBetween 1 April 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live27 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 27 August 2026
On Telegramt.me/sharpbags

Growth

5,6015,6655,6337 August 2026 — 5,665 subscribers7 August 2026 — 5,665 subscribers7 August 2026 — 5,664 subscribers10 August 2026 — 5,656 subscribers13 August 2026 — 5,648 subscribers17 August 2026 — 5,642 subscribers20 August 2026 — 5,624 subscribers24 August 2026 — 5,605 subscribers27 August 2026 — 5,601 subscribers7 August 202627 August 2026
9 measurements spanning 20 days, net -64. 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 5,591–5,675 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Aug 2026, 09:545,601-4
24 Aug 2026, 07:495,605-19
20 Aug 2026, 13:245,624-18
17 Aug 2026, 10:045,642-6
13 Aug 2026, 15:265,648-8
10 Aug 2026, 11:015,656-8
7 Aug 2026, 20:075,664-1
7 Aug 2026, 06:155,665no change
7 Aug 2026, 06:035,665first reading

Engagement

19 posts held, back to 17 April 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.

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 21 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

301 reactions across 19 posts, in 9 distinct kinds. The most used accounts for 31.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍9431.2%
custom 54609323156370954939230.6%
3812.6%
🔥3411.3%
💯154.98%
🍾123.99%
🐳103.32%
😈41.33%
🤝20.664%

Custom emoji. One 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 count beside it isTelegram’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 19 of the 19 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 301reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 17 April 2026 to 21 July 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

21 Jul 2026, 08:01 UTC≈1,590 views16 reactionsread 12 August 2026
Photo

BTC • возврат в зону 66000$ ✅ идем уверенно к поставленным целям, уровень 66000$ выступает локальным уровнем сопротивления преодолев который движение в зону 75000$ будет ускорено, крипта понемногу восстанавливается, но медленнее чем хотелось бы

👍10🐳3😈3

6 Jul 2026, 16:41 UTC≈2,140 views18 reactionsread 12 August 2026
Photo

BTC • прошло еще 3 недели, почти ничего не изменилось с прошлого поста, в моменте протестировали 60k$, на недельном тф типичная разворотная фигура W, цель движения 75000$ и затем 88500$ • так же по индикаторам загорелось уже 3 лонга и сильнейшая бычья дивергенция • в прошлый раз шорт загорелся на отметке 82500$ на локальном пике и сейчас так же горит лонг на локальном минимуме

💯13🐳32

16 Jun 2026, 14:30 UTC≈2,710 views7 reactionsread 12 August 2026
Photo

BTC небольшой откат получили, теперь снова ожидаю возврат к 67000$ от текущих или 65000$, при закрепе дневного тф не ниже 65000$ тем временем доминация альты прибавила +1%, удерживаем 8.2%

👍7

15 Jun 2026, 16:53 UTC≈2,420 views9 reactionsread 12 August 2026
Photo

цель 67000$ достигнута, предупреждал вас тут, быстрое восстановление в процессе уже, не думаю, что уровень 70000$ выдержит, после небольшого отката так же его пробьем и будем дальше расти

👍9

15 Jun 2026, 11:26 UTC≈2,000 views12 reactionsread 12 August 2026

биткоин плавно подходит к 67000$, привыкайте, теперь будем ликвидировать шортистов пару месяцев, крипте дали передышку, как минимум в бу есть хорошие шансы выйти🤝

10🤝1😈1

15 Jun 2026, 07:50 UTC≈2,060 views6 reactionsread 12 August 2026

а тут можно было и с плечиком х100 зайти 😁 рынок начал свое восстановление, биткоин уже преодолел отметку 65000$, следующая цель 67000$ и затем 70000$, крипта окончила свое падение, будем отрастать уже

👍6

14 Jun 2026, 21:45 UTC≈1,860 views14 reactionsread 12 August 2026
Photo

возврат в зону 65000$ как и говорил вам ранее и да, Ормузский пролив теперь открыт🫡🔥

👍112🍾1

13 Jun 2026, 17:02 UTC≈1,730 views10 reactionsread 12 August 2026
Photo

завтра планируют подписаться соглашение по открытию Ормузского пролива, быть росту рынка🔥 главное, чтобы Трамп не переобулся снова в ближайшие дни ожидаю по биткоину возврат в зону 65000$-67000$

🍾6👍4

7 Jun 2026, 23:21 UTC≈2,480 views17 reactionsread 12 August 2026
Photo

64200$ в моменте 🫡 после закрепа 65100$ на недельном ожидайте рост к 79800$, нормальный рост начнется после 12 июня +- 2 дня (IPO SpaceX)

👍14💯2🤝1

5 Jun 2026, 14:28 UTC≈2,310 views16 reactionsread 12 August 2026
Photo

Как только Сейлор продал 32 биткоина началось падение на -20%, отработка Sell on May?🫣 локально от текущих ожидаю возврат в зону 65000$

👍122🐳2

23 May 2026, 20:50 UTC≈3,210 views17 reactionsread 12 August 2026
Photo

BTC прошло 2 недели с последнего поста, что изменилось ? 1) получили неплохой ожидаемый откат и это хорошо, протестировали успешно 75000$ 2) месяц все равно хорошо закрывается, нужно недельный тф закрыть над 75100$ для продолжения роста 3) самый важный момент - согласовываются моменты по регулированию войны с Ираном, Ормузский пролив будет открыт и это положительно отобразится на крипте в том числе хуже может быт

🔥74🍾3👍3

6 May 2026, 07:39 UTC≈3,080 views24 reactionsread 12 August 2026
Photo

BTC прошел ровно месяц с этого поста закрыли тогда Март и Апрель в плюс и сейчас ждем закрытия Мая тоже в плюс, это уже наш с вами рынок, рынок быков🤝 до сих пор многие шортят - на этом и рост, обратите внимание на агрегированную дельту фандинга, она отрицательная весь рост, пока никто не верит и живем вчерашним днем - мы растем, многие думают-раз падали и вчера было дешево то должно быть еще дешевле, но нет, ситуа

custom 5460932315637095493126🔥6

Showing the 12 most recent of 19 posts we hold for @sharpbags. 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,564,921 of 1,624,904entries 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.

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

“Шилим Сумки 🐋” (@sharpbags), 5,601 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/sharpbags.

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.