Telegram RegisterThe public register of Telegram

Channel

1BC Project

@onebc_project

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

111subscribers

+0 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-1001650690109
TypeChannel
Username@onebc_project
DescriptionDance and music project | Ufa | Cover
Created18 May 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held2
On Telegramt.me/onebc_project

Growth

1117 Aug 2026, 19:56 — 111 subscribers9 Aug 2026, 07:02 — 111 subscribers7 Aug 2026, 19:569 Aug 2026, 07:02
2 measurements spanning 1 day. 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 110–112 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 07:02111no change
7 Aug 2026, 19:56111first reading

Engagement

18 posts held, back to 26 April 2025the 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 2 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
125
Videos
68
Links
56

Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
4m 55s
Average length
1m 14s

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

259 reactions across 17 posts, in 13 distinct kinds. The most used accounts for 20.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💋5220.1%
🔥4818.5%
custom 52380810011119532474417.0%
❤‍🔥3513.5%
💘3312.7%
custom 5404651914593836721218.11%
🎉93.47%
😁62.32%
😍41.54%
🤯31.16%
🏆20.772%
👏10.386%
💯10.386%

Custom emoji. 2 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 17 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 259reactions 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 26 April 2025 to 2 June 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

2 Jun 2026, 18:18 UTC162 viewsread 9 August 2026

анонимка: зачем вы подавались на кстар с номером, с которым уже выступали? на самом деле это просто я дурная, потому что не так поняла условие. и почему-то подумала, что нельзя с номером с которым уже именно у них участвовали (вероятно, что я впринципе не дочитала этот пункт) поэтому ничего страшного не произошло. просто моя невнимательность

2 Jun 2026, 10:50 UTC964 views12 reactionsread 9 August 2026
Video

KKParty 31.05.26 🔪BTS - Danger (by 1BC Project) Спасибо всем за вашу очень громкую поддержку!!🩶 И спасибо Диане за лучшие мероприятия!! Для 1BC они имели особенную ценность, наши проекты были здесь с самых первых мероприятий, и ккпати давно успел стать родным. Мы будем очень скучать и вспоминать эти времена с теплотой❤️‍🩹 🤩🤩🤩🤩 🩶отдельно для моих девочек: хоть проект шел не так активно и где-то все еще есть пробел

custom 54046519145938367217💋3🔥1custom 52380810011119532471

30 May 2026, 17:37 UTC385 views10 reactionsread 9 August 2026
Video

♠️Уже завтра мы выступим с новым проектом на KKparty: GOLDEN HOUR !! ➕ 🔪BTS - Danger ➕ ________________________________ Будем рады вашей поддержке!🤩

❤‍🔥3🔥3💘2💋1custom 54046519145938367211

25 Jul 2025, 09:45 UTC≈1,570 views16 reactionsread 9 August 2026

🤩 MV COVER | BTS - SPINE BREAKER by 1BC Project ➡️ https://youtu.be/iv2BARq2Huk?si=xxIEoFj48uq600oE Полное видео уже на нашем YouTube канале. Приятного просмотра!🔥 #btsspinebreaker #1bc

❤‍🔥4custom 52380810011119532473🏆2💋2💘2🔥2😁1

22 Jul 2025, 14:38 UTC≈1,400 views24 reactionsread 9 August 2026
Video

🤩BTS - SPINE BREAKER / MV cover [TEASER]🤩

❤‍🔥7💋4💘4🔥3custom 54046519145938367213custom 52380810011119532472😍1

1 Jun 2025, 19:24 UTC296 views20 reactionsread 9 August 2026
Forwarded from @oxigEntcdtoxisosiskaVideo

✨✨✨✨✨✨ ✨✨✨✨✨✨✨✨✨ наступило 2 июня, а это значит что у нашей рианы день рождения!! 📰📰📰📰📰🔜📝📝📝📝📝📝 мы все безумно рады твоему появлению в нашей команде, надеемся что ты останешься с нами надолго!⭐️ желаем чтобы у тебя сбывались все мечты и все получалось, за что бы ты не бралась, у тебя непременно получится! ❤ с днём рождения, драгоценная😶🎀 можете порадовать своим поздравлением в комментариях! #хеппибез

🔥7💋5💘5❤‍🔥2custom 54046519145938367211

23 May 2025, 12:58 UTC≈1,210 views12 reactionsread 9 August 2026

[Performance | KKParty] Вышло видео нашего выступления, но уже на канале KKParty✨ https://youtu.be/nzZpZxSiFyg?si=7uStWMsxfazU88AH 🤭🤭🤭 #btsineedu #1bc

💋3🔥3🤯3custom 52380810011119532473

16 May 2025, 16:44 UTC244 views3 reactionsread 9 August 2026
Forwarded from @kpop_party_ufaVideo message

Video message, posted without a caption

custom 52380810011119532473

16 May 2025, 16:44 UTC593 views5 reactionsread 9 August 2026

сегодня мы решили сходить на спринт пати частью состава i need u и вышло так, что в итоге мы частично «выступили»🤩

custom 52380810011119532473💋2

8 May 2025, 09:49 UTC≈1,480 views16 reactionsread 9 August 2026

[Performance | KKparty] ✍️Видео с нашим выступлением на KKParty уже на YouTube!🩶 https://youtu.be/z9ZFZZB5oC4?si=uL2PKyOp3qjSmSyp 👆👆👆 #btsineedu #1bc

🔥5❤‍🔥4💋4💘2custom 52380810011119532471

5 May 2025, 13:52 UTC643 views17 reactionsread 9 August 2026
Video

🎀☺️

😁5💋4💘4🔥2💯1custom 52380810011119532471

5 May 2025, 11:05 UTC567 views12 reactionsread 9 August 2026

P.S. А те, кто были на пати и кому понравилось наше выступление, посчитав, что оно подходит под тематику вечеринки, могут проголосовать за нас по данной ссылке🫂: https://forms.yandex.ru/u/68166042e010dbcb60d11332

💋5😍3custom 52380810011119532473🔥1

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

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

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

“1BC Project” (@onebc_project), 111 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/onebc_project.

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.