Telegram RegisterThe public register of Telegram
Telegram profile photo for Young Bullets crew

Channel

Young Bullets crew

@youngbulletscrew

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

290subscribers

-3 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001852521695
TypeChannel
Username@youngbulletscrew
Created5 October 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded8 August 2026
Last confirmed live9 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/youngbulletscrew

Growth

2892932917 August 2026 — 293 subscribers8 August 2026 — 293 subscribers24 August 2026 — 289 subscribers9 September 2026 — 290 subscribers2907 August 20269 September 2026
4 measurements spanning 32 days, net -3. 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 288–294 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 06:15290+1
24 Aug 2026, 17:19289-4
8 Aug 2026, 08:15293no change
7 Aug 2026, 20:04293first reading

Engagement

18 posts held, back to 23 July 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 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 18 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
5m 17s
Average length
40s

Measured directly from 8 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

232 reactions across 17 posts, in 17 distinct kinds. The most used accounts for 33.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥7733.2%
6728.9%
😁219.05%
❤‍🔥166.90%
🤣125.17%
🎉93.88%
🐳83.45%
👍41.72%
😍41.72%
🤩41.72%
🤯31.29%
💘20.862%
👏10.431%
💋10.431%
😇10.431%
😴10.431%
🦄10.431%

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 18 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 232 reactions 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 23 July 2026 to 8 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

8 Aug 2026, 00:23 UTC61 views1 reactionsread 8 August 2026
Forwarded from @oneofall7Photo

Подогреваем мощно Знакомьтесь три Маэстро, музыкальные монстры🔥🔥🔥 Встречайте на Один из Всех🏆🥇 1. DJ JOHNNY ALOUD (Young bullets crew. г. ЮЖНО-САХАЛИНСК) Наш незаменимый человек, без которого не обходится ни одно Сахалинское мероприятие по брейкингу. Всеми известный и любимый♥️🙌🏻‼️👍🏻 2. DJ SWEDE (г. ЮЖНО-САХАЛИНСК) Победитель рег этапа KARDO’7 в номинации PARTY KILLER MIX Постоянный участник локальных и межрегионал

🔥1

7 Aug 2026, 06:08 UTC106 views9 reactionsread 8 August 2026
Video

Святой Дмитрий😊😄🤣🥇

5😁3😍1

5 Aug 2026, 06:43 UTC101 views9 reactionsread 8 August 2026
Forwarded from @oneofall7Photo

Ну что Лентос снова летит на Сахалин 🔥🔥🔥🔥🔥 Lentos — голос, который качает танцполы страны. Если вы хоть раз были на крупных хип-хоп ивентах, то наверняка слышали этот драйв. Lentos — это не просто МС, это человек, который живет культурой уже больше 15 лет. Будучи участницей дуэта Lentos&Dым и ярким представителем сибирской школы, она давно переросла рамки региональной сцены и стала одной из самых востребованных веду

🔥72

4 Aug 2026, 12:11 UTC128 views11 reactionsread 8 August 2026
Video

Ариша и Кокос 😄🤦🏻🤣 с братом фотка не получается😄

❤‍🔥8👍3

31 Jul 2026, 04:54 UTC195 views0 reactionsread 8 August 2026
Forwarded from @oneofall7Photo

Наш постоянный гость и МС Moovy_A — легенда хабаровского брейкинга! Если вы в теме дальневосточного хип-хопа, то это имя не нуждается в представлении. Moovy_A — один из самых ярких и техничных би-боев Хабаровска. За его плечами не просто годы тренировок, а статус одного из сильнейших танцоров региона. Moovy_A — это тот случай, когда опыт встречается с безумной энергетикой. Сегодня он не только «разрывает» танцпол

30 Jul 2026, 11:45 UTC193 views10 reactionsread 8 August 2026

Уже 4 кандидата😊 1. Олега 2. Карман 3. Пума 4. Минги 5. Кто следующий? 🔥🔥🔥

8🔥2

30 Jul 2026, 11:44 UTC283 views27 reactionsread 8 August 2026
Photo

Горячие новости Поздравляем Минги с присуждение Кандидата Мастера Спорта по Брейкингу👍🏻💪🏼 гордимся 🙌🏻🙌🏻🙌🏻

14🔥13

29 Jul 2026, 08:50 UTC181 views19 reactionsread 8 August 2026
Video

Песочный брейк 😊😄

😁14🤩4🤣1

28 Jul 2026, 05:21 UTC180 views21 reactionsread 8 August 2026
Video

Минги привет👋👋👋

🔥96🤣3😍2😇1

27 Jul 2026, 11:13 UTC201 views39 reactionsread 8 August 2026
Video

Минги, Пума, Олега, Кокос, Некит, Эль Пекеньо, Кирямбо, Карман, Юран- Чупа прилетел ♥️🙌🏻 Как вам состав?🔥🔥🔥🔥

🔥23❤‍🔥75👏1💋1💘1🤣1

27 Jul 2026, 04:51 UTC185 views3 reactionsread 8 August 2026
Video

Уничтожить Эль Пекеньо 🤣🤣🤣

🤣2👍1

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

Forward network

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.

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

“Young Bullets crew” (@youngbulletscrew), 290 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/youngbulletscrew.

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.