Telegram RegisterThe public register of Telegram

Channel

bóshān

@boshan_brew

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

79subscribers

+0 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002115385199
TypeChannel
Username@boshan_brew
DescriptionЗавариваем чай по вторникам в пространстве бара Путч • Бот для записи на чайные встречи @boshan_brew_bot • По вопросам и предложениям пишите в чат или в Direct Messages inst: https://instagram.com/boshan_brew
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held2
On Telegramt.me/boshan_brew

Growth

798 August 2026 — 79 subscribers9 August 2026 — 79 subscribers8 August 20269 August 2026
2 measurements spanning 2 days. 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 78–80 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 19:4579no change
8 Aug 2026, 03:4779first reading

Engagement

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

What this channel posts

Photos
379
Videos
59
Links
84

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
13s
Average length
7s

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

32 reactions across 6 posts, in 7 distinct kinds. The most used accounts for 40.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54225395084888882191340.6%
custom 5434136100576716279618.8%
custom 5404634163494030437515.6%
👻39.38%
26.25%
🗿26.25%
custom 521987256456997216613.13%

Custom emoji. 4 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 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 32reactions 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 16 May 2026 to 1 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

1 Jun 2026, 12:42 UTC232 views10 reactionsread 9 August 2026
Photo

Закрытие третьего сезона «бошань» Официально завершаем камерный сезон 2026. Спасибо бару Путч за гостеприимство. Спасибо всем нашим гостям за участие. До новых встреч! 𓆏

custom 54225395084888882197custom 54046341634940304373

31 May 2026, 08:15 UTC184 views6 reactionsread 9 August 2026
Photo

Закрытие сезона 📍Первым открыли блин шу пуэра от фабрики Гу Ча Юань из Мэнхая — Гунтин Юй Инь 2013 года. Рядовой шу на каждый день. Во вкусе — классические древесно-ореховые ноты и сладковатое послевкусие. 📍Вторым пробовали белый в разломе 350 гр. блина от фабрики Ли Да из Фудина — Шоу Мэй 2022 года. Отличный белый чай с цветочно-фруктовыми нотами, сладостью мёда и приятной кислинкой. Сырьём для такого чая служат л

custom 542253950848888821942

25 May 2026, 12:52 UTC≈1,220 views2 reactionsread 9 August 2026
Photo

bóshān pincha #45 Вторник, 26 мая! Закрытие сезона! Встречаемся в баре Путч, завариваем два чая: • шу пуэр — Цяо Му Гунтин 熟普洱 2013 (Миндальное дерево) • белый — Шоу Мэй Лида 寿眉 2022 (Брови долголетия) Начало — 20:00 ⧗ Цена — 300 ₽ Кол-во гостей — 6 ☻ Запись — @boshan_brew_bot Где нам, дуракам, чай пить!

custom 54225395084888882192

24 May 2026, 08:57 UTC124 views5 reactionsread 9 August 2026
Photo

Красный aka чёрный 📍Первым заваривали Чжень Шань Сяо Чжун — китайский красный копчёный чай, в Европе часто известный как Лапсанг Сушонг. Во вкусе — дымность, печённость, чернослив, сладость. Сяо Чжун прославился благодаря своему уникальному методу обработки — копчению с использованием сосновых дров. 📍Вторым заваривали Дарджилинг — индийский чёрный чай, выращенный в окрестностях одноименного города в северной горной

custom 54341361005767162793👻2

18 May 2026, 12:42 UTC≈1,380 views4 reactionsread 9 August 2026
Photo

bóshān pincha #44 Вторник, 19 мая! Встречаемся в баре Путч, завариваем два чая: • красный — Чжэн Шань Сяо Чжун 正山小种 (Лапсанг Сушонг) • чёрный — Дарджилинг Начало — 20:00 ⧗ Цена — 300 ₽ Кол-во гостей — 6 ☻ Запись — @boshan_brew_bot Пейте чай неторопливо и непринуждённо — иногда это отдых, иногда это практика

custom 54341361005767162793👻1

16 May 2026, 07:15 UTC101 views5 reactionsread 9 August 2026
Photo

Писающий мальчик и фабричный пуэр 📍Первым заваривали шу пуэр от фабрики Мэнхай Да И — V93, партия 2009 года. Во вкусе — баланс сладости, древесных и ореховых нот со сливочным послевкусием. 📍Вторым пробовали шу пуэр от фабрики Хайвань — Лао Тун Чжи 7578 («Старый товарищ»), 2021 года. Во вкусе — так же эталонный баланс древесно-ореховых нот, небольшой горчинки травяного бальзама и сладкого послевкусия. Фабричный пуэ

🗿2custom 54046341634940304372custom 52198725645699721661

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

Citation-graph rank

Citation-graph rank — 258,923 of 1,345,403entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

“bóshān” (@boshan_brew), 79 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/boshan_brew.

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.