Telegram RegisterThe public register of Telegram
Telegram profile photo for бусинки

Channel

бусинки

@bysinki0

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

158subscribers

+2 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-1003779390038
TypeChannel
Username@bysinki0
CreatedBetween 1 February 2026 and 11 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live16 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/bysinki0

Topic

Local community — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 25 September 2026 and assigned it the closest of 31 fixed categories, at 45% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

1561581577 August 2026 — 156 subscribers8 August 2026 — 156 subscribers16 August 2026 — 157 subscribers16 September 2026 — 158 subscribers7 August 202616 September 2026
4 measurements spanning 40 days, net +2. 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 156–158 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 21:40158+1
16 Aug 2026, 01:48157+1
8 Aug 2026, 18:31156no change
7 Aug 2026, 18:59156first reading

Engagement

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

Reaction mix

87 reactions across 6 posts, in 5 distinct kinds. The most used accounts for 50.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤4450.6%
💘2124.1%
🔥910.3%
❤‍🔥78.05%
😭66.90%

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 6 of the 6 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 87 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 6 most recent posts we hold, published 11 June 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, 14:11 UTC43 views12 reactionsread 8 August 2026
Forwarded from @p34formaPhoto

Собираем себя и свои вечера. Вместе с бусинками лизой х. и кристиной м. составили дайджест событий, ради которых стоит провести эти выходные вне дома пятница, 7 августа ✹ В «Проливе», где щедрые испанские угощения будут чередоваться с латиноамериканской музыкой и неочевидными диджей-сэтами, охлаждаемся танцами 🔥 ✹ Фестиваль «Круто» открывается в двух часах от Москвы ✹ В Открытых студиях Винзавода состоится встреча …

🔥7❤5

8 Aug 2026, 14:10 UTC41 views7 reactionsread 8 August 2026

а еще —> рассказали Соне и Владу из p34 куда намылились в эти выходные 🧼 🧼 🧼

❤4💘3

8 Aug 2026, 14:09 UTC42 views14 reactionsread 8 August 2026
Photo

бусинки снова в строю... выходим из творческого отпуска и продолжаем вещание о повседневности. пока лежали под солнышком — вспомнили наших кумиров, кто тоже находил спасение в будничном. говорят, в эти времена нужно «поливать свой сад» — будем учиться у великих! 🎉

❤7❤‍🔥4💘3

20 Jun 2026, 09:15 UTC108 views19 reactionsread 8 August 2026
Photo

#бусинкадня бусиновская россыпь в новых холстах Виталия Пушницкого из проекта «Земля» для Marina Gisich Gallery

❤10💘7🔥2

12 Jun 2026, 17:15 UTC162 views10 reactionsread 8 August 2026
Photo

с надеждой на дождь и пощаду от жары бусинки планируют свои и ваши🫵🏻 выходные! смотрим, что интересного будет происходить везде и всюду (1-2) главная ассоциация с началом лета — список книжек, которые надо прочесть за эти стремительные три месяца. составлять такой советуем отправляться в Петербург и Казань. на Неве нас ждет гуманитарный фестиваль от нло, в программе которого поэтические чтения, презентации книг, паб…

❤5❤‍🔥3💘2

11 Jun 2026, 13:00 UTC128 views25 reactionsread 8 August 2026
Photo

не идите, а бегите в эту жару смотреть на #бусинкадня: очень разная, но одинаково чудесная Аня Желудь в двух залах AZART (в компании с отменными кондиционерами)

❤13💘6😭6

Showing the 6 most recent of 6 posts we hold for @bysinki0. 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

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

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

“бусинки” (@bysinki0), 158 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/bysinki0.

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.