Telegram RegisterThe public register of Telegram
Telegram profile photo for #borjomi1022

Channel

#borjomi1022

@bespokoyztvo

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

226subscribers

-5 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-1001653375356
TypeChannel
Username@bespokoyztvo
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 live31 August 2026
Measurements held4
Confirmed unchanged2 times, most recently 31 August 2026
On Telegramt.me/bespokoyztvo

Growth

226231228.57 August 2026 — 231 subscribers8 August 2026 — 231 subscribers8 August 2026 — 230 subscribers23 August 2026 — 226 subscribers7 August 202623 August 2026
4 measurements spanning 16 days, net -5. 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 225–232 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 16:36226-4
8 Aug 2026, 12:02230-1
8 Aug 2026, 10:05231no change
7 Aug 2026, 12:19231first reading

Engagement

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

Reaction mix

695 reactions across 13 posts, in 15 distinct kinds. The most used accounts for 16.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 530754688732943282311616.7%
custom 53548026128960195947711.1%
custom 5337190193260673754649.21%
custom 5217642596075064695639.06%
custom 5206652638053023189608.63%
custom 5390814178506196716557.91%
🍓476.76%
custom 5307561885355227761446.33%
custom 5380094902208055513426.04%
custom 5224218976984253154304.32%
custom 5424904442036107185284.03%
custom 5233449329854791683263.74%
custom 5379940029982329056243.45%
custom 5303199036101116415152.16%
custom 542962268694906797040.576%

Custom emoji. 14 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 are 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 13 of the 13 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 695 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 14 March 2024 to 27 June 2024, 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

27 Jun 2024, 19:42 UTC≈1,550 views14 reactionsread 8 August 2026
Photo

9:00 PM https://t.me/anxiousday 📄

🍓14

Signed arénda

13 Jun 2024, 14:44 UTC≈1,560 views27 reactionsread 8 August 2026
Video message

Video message, posted without a caption

🍓16custom 52334493298547916836custom 53031990361011164155

Signed arénda

13 Jun 2024, 11:20 UTC≈1,110 views29 reactionsread 8 August 2026
Photo

Photo, posted without a caption

🍓17custom 53031990361011164157custom 52334493298547916835

Signed arénda

26 May 2024, 17:33 UTC≈1,320 views62 reactionsread 8 August 2026
Photo

я не понимаю

custom 539081417850619671655custom 52334493298547916837

Signed arénda

22 May 2024, 09:59 UTC≈1,440 views59 reactionsread 8 August 2026
Photo

Photo, posted without a caption

custom 521764259607506469554custom 52334493298547916835

Signed arénda

21 May 2024, 12:52 UTC≈1,120 views31 reactionsread 8 August 2026
Photo

Photo, posted without a caption

custom 530754688732943282326custom 52176425960750646955

Signed arénda

21 May 2024, 10:58 UTC≈1,080 views17 reactionsread 8 August 2026
File

File, posted without a caption

custom 530754688732943282314custom 53031990361011164153

Signed arénda

20 May 2024, 13:19 UTC≈1,070 views20 reactionsread 8 August 2026

ﮩ٨ـﮩﮩ٨ـ٨ـﮩﮩ٨ـﮩ٨ـﮩﮩ٨ﮩ٨ـﮩﮩ٨ـﮩ٨ـﮩﮩ٨ـ

custom 530754688732943282316custom 52176425960750646954

Signed arénda

18 May 2024, 09:18 UTC≈1,200 views63 reactionsread 8 August 2026
Photo

:(

custom 530754688732943282360custom 52334493298547916833

Signed arénda

21 Apr 2024, 16:17 UTC≈1,810 views66 reactionsread 8 August 2026

Posted without readable text

custom 538009490220805551342custom 537994002998232905624

Signed arénda

13 Apr 2024, 21:01 UTC≈1,940 views129 reactionsread 8 August 2026
Photo

пусть будет

custom 535480261289601959477custom 542490444203610718528custom 522421897698425315424

Signed arénda

27 Mar 2024, 12:42 UTC≈1,710 views86 reactionsread 8 August 2026
Photo

🌟

custom 520665263805302318960custom 530756188535522776120custom 52242189769842531546

Signed arénda

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

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

“#borjomi1022” (@bespokoyztvo), 226 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/bespokoyztvo.

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.