Telegram RegisterThe public register of Telegram
Telegram profile photo for Blue White Pins

Channel

Blue White Pins

@bw_pins

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

448subscribers

+17 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-1001786501850
TypeChannel
Username@bw_pins
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live19 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/bw_pins

Topic

Other / unclassifiable — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 57% 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

431448439.57 August 2026 — 431 subscribers8 August 2026 — 431 subscribers16 August 2026 — 441 subscribers24 August 2026 — 444 subscribers31 August 2026 — 446 subscribers19 September 2026 — 448 subscribers7 August 202619 September 2026
6 measurements spanning 43 days, net +17. 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 428–451 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 11:36448+2
31 Aug 2026, 00:54446+2
24 Aug 2026, 13:58444+3
16 Aug 2026, 14:29441+10
8 Aug 2026, 05:18431no change
7 Aug 2026, 15:05431first reading

Engagement

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

What this channel posts

Video runtime
23s
Average length
23s

Measured directly from 1 video 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

25 reactions across 7 posts, in 5 distinct kinds. The most used accounts for 40.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1040.0%
🔥936.0%
🙏416.0%
👏14.00%
😎14.00%

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

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

7 Aug 2026, 07:03 UTC48 viewsread 8 August 2026
Forwarded from @g13studioPhoto

Photo, posted without a caption

Signed Sergey B

6 Aug 2026, 15:24 UTC58 viewsread 8 August 2026
Forwarded from @BoxandDrawPhoto

После небольшого перерыва встречайте - знак «Джокер»!🃏 В руке у него не случайная карта, а козырь с гербом клуба. Это то, за что мы стоим на трибуне в любую погоду и при любом счёте. Взгляд, не выдающий эмоций. Улыбка, за которой уверенность в своей команде, что бы ни показывало табло. Мягкая эмаль, чёткая графика, продуманная деталь в каждой линии. ЗНАК «ДЖОКЕР» 📌 Мягкая эмаль 📏 33,4х40 мм 💰 500₽

Signed Sergey B

5 Aug 2026, 05:21 UTC70 viewsread 8 August 2026
Forwarded from @bristolpubPhoto

🎉🎉ДЕНЬ РОЖДЕНИЯ БРИСТОЛЯ 8 АВГУСТА 19:00 ПАБ БРИСТОЛЬ 🕰 Сбор гостей — с 18:30 🪩Начало — с 19:00 Друзья, вот и настало время как следует отпраздновать день рождения Бристоля! 🎩 Дресс-код — бутлегерский стиль Представьте Англию начала XX века: классические костюмы, жилеты, рубашки, подтяжки, галстуки, кепки в стиле Peaky Blinders, длинные пальто. Для девушек — элегантные платья, брючные костюмы, шляпки, перчатки и

Signed Sergey B

4 Aug 2026, 17:42 UTC87 views5 reactionsread 8 August 2026
Forwarded from @rubinkazanbadgePhoto

Напоминаем о легендарном мероприятии, которое пройдет в Казани 8 августа 2026 года, в баре «Ликёр’s». С 15:00 до 17:00 основная часть встречи, а дальше пока не закончится всё пиво в баре. Общение, значки, игровые футболки, шарфы, матчевые программки, розыгрыш. А для гостей города и любителей граундхоппинга возможность посетить новые стадионы на следующий день после мероприятия. Ждём всех в баре «Ликёр’s» по адресу

👍3🔥2

Signed Sergey B

3 Aug 2026, 15:37 UTC82 views5 reactionsread 8 August 2026
Forwarded from @znachki_i_znakiVideo

Дорогие друзья ❤️ Саша со своей семьей передают всем привет и благодарность 🙏🏻 А еще Саша дарит нам свою небольшую коллекцию значков и мы договорились, что дс с продажи коллекции пойдут в помощь Детскому Онкологическому центру им Димы Рогачева ❤️🙏🏻 Помогайте помогать ❤️

🙏4👍1

Signed Sergey B

30 Jul 2026, 22:06 UTC141 views7 reactionsread 8 August 2026
Forwarded from @ultras_actionPhoto

Серия значков, на которых увековечены самые знаковые пересечения в истории русского околофутбола. От Арбата-1995 до Марселя-2016!

🔥6👍1

Signed Sergey B

30 Jul 2026, 11:50 UTC123 views3 reactionsread 8 August 2026
Forwarded from @Scowls_Badges_GalleryPhoto

📣 Оᴄᴛᴀʙɯиᴇᴄя ϶ᴋɜᴇʍᴨᴧяᴩы нᴀᴄᴛᴏᴧьнᴏй иᴦᴩы ПИНОПОЛИЯ ʙ нᴀᴧичии! ⚫️ иᴦᴩᴏʙᴏᴇ ᴨᴏᴧᴇ ᴄ учᴀᴄᴛниᴋᴀʍи 𝙁𝙖𝙡𝙚𝙧𝙞𝙨𝙩𝙞𝙘𝙨 𝘾𝙤𝙢𝙢𝙪𝙣𝙞𝙩𝙮 ⚫️ ϶ᴋᴄᴋᴧюɜиʙный ɜнᴀчᴏᴋ (ᴛᴏᴧьᴋᴏ ʙ иᴦᴩᴇ) ⚫️ ᴄᴛиᴋᴇᴩᴨᴀᴋ ⚫️ иᴦᴩᴏʙыᴇ ɸиɯᴋи ᴨᴏ инᴛᴇᴩᴇᴄᴀʍ 💥 хᴏᴩᴏɯᴇᴇ нᴀᴄᴛᴩᴏᴇниᴇ ʙ ᴋᴩуᴦу дᴩуɜᴇй 📌 дᴏᴨᴇчᴀᴛᴏᴋ и ᴨᴇᴩᴇʙыᴨуᴄᴋᴀ нᴇ будᴇᴛ Сᴛᴀнь ɸᴀᴧᴇᴩиᴄᴛичᴇᴄᴋиʍ ʍᴀᴦнᴀᴛᴏʍ 💰 Пᴏ ʙᴄᴇʍ ʙᴏᴨᴩᴏᴄᴀʍ и ɜᴀ ᴨᴏᴧныʍ ᴀᴄᴄᴏᴩᴛиʍᴇнᴛᴏʍ: ⚡️ @ScowlSPb

👏1🔥1😎1

Signed Sergey B

28 Jul 2026, 05:37 UTC115 views1 reactionsread 8 August 2026
Forwarded from @rubinkazanbadgePhoto

Фотоотчёт с прошедшей 2-ой Самарской встречи коллекционеров.

👍1

Signed Sergey B

27 Jul 2026, 09:46 UTC139 views2 reactionsread 8 August 2026
Forwarded from @g13studioPhoto

Photo, posted without a caption

👍2

Signed Sergey B

27 Jul 2026, 08:00 UTC99 views2 reactionsread 8 August 2026
Forwarded from @g13studioPhoto

Коллекционеры шагают по России))) Ближайшие Встречи и Слеты в Афишах!! FC для Людей и про Людей!!!!

👍2

Signed Sergey B

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

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

“Blue White Pins” (@bw_pins), 448 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/bw_pins.

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.