Telegram RegisterThe public register of Telegram
Telegram profile photo for бурда: о том, что было

Channel

бурда: о том, что было

@burda_art

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

244subscribers

+15 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002920142231
TypeChannel
Username@burda_art
CreatedBetween 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live2 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/burda_art

Growth

229244236.56 August 2026 — 229 subscribers7 August 2026 — 229 subscribers14 August 2026 — 234 subscribers20 August 2026 — 238 subscribers2 September 2026 — 244 subscribers6 August 20262 September 2026
5 measurements spanning 27 days, net +15. 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 227–246 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Sept 2026, 21:08244+6
20 Aug 2026, 03:56238+4
14 Aug 2026, 00:46234+5
7 Aug 2026, 03:00229no change
6 Aug 2026, 14:08229first reading

Engagement

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

Reaction mix

229 reactions across 9 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5413691265973781671229100.0%

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

Measured over the 9 most recent posts we hold, published 28 July 2026 to 4 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

4 Aug 2026, 17:58 UTC609 views29 reactionsread 7 August 2026
Photo

ребятки #бурда #арт

custom 541369126597378167129

3 Aug 2026, 14:07 UTC88 views33 reactionsread 7 August 2026
Forwarded from @migingerPhoto

✨ очень здоровская картинка вышла. может, уйдет на обложку комикса где-нибудь онлайн #бурда #арт

custom 541369126597378167133

2 Aug 2026, 14:55 UTC139 views19 reactionsread 7 August 2026
Photo

я почти отстрелялась от всего, ожидайте

custom 541369126597378167119

31 Jul 2026, 18:28 UTC162 views26 reactionsread 7 August 2026
Photo

🤩 франкенштейн au 🤩 #бурда #арт #своп #комикс #au #реф

custom 541369126597378167126

31 Jul 2026, 18:25 UTC161 views21 reactionsread 7 August 2026

все еще считаю самой лучшей аушкой по бурде хеллоуинскую - просто петя взял и воссоздал себе двух дружбанчиков на поводу, потому что ему было очень одиноко в большом замке по какой-то причине мне очень нравится концептуально франкштейн-штуки.. kinda kinky i guess а еще свопки с этой аушкой??? быстро разлетались несколькими партиями? и потом люди искали их в обменниках.. ну я там наряды им здоровские придумала чего уж

custom 541369126597378167121

30 Jul 2026, 23:05 UTC198 views38 reactionsread 7 August 2026
Photo

что-то думала июль будет прорывным по контенту, а в итоге слегла из-за работы #бурда #арт #заметки

custom 541369126597378167138

29 Jul 2026, 22:33 UTC199 views12 reactionsread 7 August 2026

напоминаю, у здешнего тгк есть анонимка (в закрепе среди хештегов)! вы туда можете слать всякие вопросики.. > : )

custom 541369126597378167112

29 Jul 2026, 19:25 UTC210 views34 reactionsread 7 August 2026
Photo

время нежности автор #бурда #фанарт

custom 541369126597378167134

28 Jul 2026, 16:19 UTC181 views17 reactionsread 7 August 2026
Forwarded from @grib_maryam_artPhoto

Не помню когда было нарисовано Лучший мужчина по памяти и умирающими фломастерами В любом случае желаю в каждом доме такого гостя Персонаж минингер #скетчи

custom 541369126597378167117

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

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

“бурда: о том, что было” (@burda_art), 244 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/burda_art.

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.