Telegram RegisterThe public register of Telegram
Telegram profile photo for @ᅠ ᅠwheepy !

Channel

@ᅠ ᅠwheepy !

@wheepy_hbsmp

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

21subscribers

+5 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1004469861973
TypeChannel
Username@wheepy_hbsmp
CreatedBetween 1 June 2026 and 9 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live18 September 2026
Measurements held7
Confirmed unchanged2 times, most recently 18 September 2026
On Telegramt.me/wheepy_hbsmp

Growth

16242011 August 2026 — 16 subscribers11 August 2026 — 18 subscribers11 August 2026 — 18 subscribers18 August 2026 — 23 subscribers25 August 2026 — 24 subscribers31 August 2026 — 23 subscribers10 September 2026 — 21 subscribers2111 August 202610 September 2026
7 measurements spanning 30 days, net +5. 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 15–25 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 07:0021-2
31 Aug 2026, 23:3823-1
25 Aug 2026, 13:0924+1
18 Aug 2026, 15:2723+5
11 Aug 2026, 19:1618no change
11 Aug 2026, 16:2818+2
11 Aug 2026, 02:4716first reading

Engagement

20 posts held, back to 9 August 2026 — 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 page of 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 20 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

103 reactions across 16 posts, in 11 distinct kinds. The most used accounts for 28.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52108134821103180282928.2%
custom 53955089471279180302827.2%
custom 5908913562276862813109.71%
custom 591138418208434449598.74%
custom 529881304556321983065.83%
custom 541379721852201331954.85%
custom 529851261689583021643.88%
🏆43.88%
👀43.88%
custom 532105406125916276832.91%
❤10.971%

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

Measured over the 20 most recent posts we hold, published 9 August 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

11 Aug 2026, 13:18 UTC18 views2 reactionsread 11 August 2026

* supp: эта пометка значит, что остальные персонажи не могут прочитать сообщения

custom 52108134821103180282

11 Aug 2026, 13:17 UTC18 views6 reactionsread 11 August 2026

#messagenotfound ᅠ ᅠя даже не знаю звучат ли мои мысли членораздельно потому что я реально не понимаю типа. почему. зачем. он даже ничего не добился

custom 52108134821103180282custom 52985126168958302162custom 53955089471279180302

11 Aug 2026, 13:17 UTC18 views7 reactionsread 11 August 2026

#messagenotfound ᅠ ᅠ😕 типа ... он вообще серьёзно?? настроил бомба - моего друга!! - против меня, убедил его притворяться веммбу а также таргетить моих друзей, а потом сам же его и убил. ..... на моих глазах. ещё и стал говорить МНЕ что он якобы пытался со мной поговорить. если в его глазах 'поговорить' это убивать всех моих друзей, то ..???ок?? wtf ? он буквально признался что убил Войди, а затем еще языком чесал ч…

custom 52108134821103180283custom 52985126168958302162custom 53210540612591627681custom 53955089471279180301

11 Aug 2026, 13:17 UTC17 views7 reactionsread 11 August 2026

#messagenotfound * ᅠ ᅠ😕 я жаловался что на том сервере тихо, но здесь оказалось ещё хуже даже не могу понадеяться, что кто-нибудь вернётся потому что из-за Зессаро все мертвы. и он тоже мёртв. 🌟🌟🌟🌟🌟🌟... вместо нормального разговора он решил перебить весь сервер. правда, на что он вообще надеялся? что я не узнаю о его идиотском плане?? а главное, всё из-за ревности он мог бы просто сказать мне. я считал его другом

custom 53955089471279180303custom 53210540612591627682custom 52108134821103180281custom 59113841820843444951

11 Aug 2026, 09:25 UTC18 views2 reactionsread 11 August 2026

ᅠ ᅠчто-то я грустинку словил

custom 53955089471279180302

11 Aug 2026, 08:06 UTC18 views2 reactionsread 11 August 2026

ᅠ ᅠ🌟 а что на моем сервере......

custom 53955089471279180302

11 Aug 2026, 08:05 UTC17 views8 reactionsread 11 August 2026

ᅠ ᅠ🌟 доброе утро ??? походил, вещи понакрафтил по возможности... (особенно оружие ибо не хочу умирать по загадочным обстоятельствам) брожу пока что без цели. тут так тихо, что даже напрягает чутка yk. вот на моеем сервере

custom 52108134821103180283custom 52988130455632198302custom 59113841820843444952👀1

9 Aug 2026, 20:58 UTC17 views8 reactionsread 11 August 2026

ᅠ ᅠ🌟 здесь очень красиво а ещё это место выглядит так будто здесь можно добыть хорошие ресурсы ... этим я и займусь

custom 52108134821103180284🏆2custom 54137972185220133192

9 Aug 2026, 19:52 UTC17 views6 reactionsread 11 August 2026

ᅠ ᅠи всё ещё поднимаюсь* я очень устал босс

custom 53955089471279180303custom 52988130455632198302custom 52108134821103180281

9 Aug 2026, 19:51 UTC18 views7 reactionsread 11 August 2026

ᅠ ᅠ🌟 пока я поднимался, мне пришло сообщение (которое я наверное должен был получить чуток пораньше) вот и оно: Привет, Випи! Добро пожаловать на наш сервер Holy Blood SMP! Этот блог был создан специально под тебя - мы чутка изучили твои cookie (или как их) и подобрали тот стиль, который бы тебе понравился при создании блога. Я - ᒲ||ᓭℸ ‌╎ᓵ ⎓ꖎ𝙹∴ᒷ∷ - его владелец и я использую только те данные, которые находятся в обще…

custom 59089135622768628133🏆2custom 52108134821103180282

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

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.

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

“@ᅠ ᅠwheepy !” (@wheepy_hbsmp), 21 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/wheepy_hbsmp.

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.