вчетвером это пиздец

Channel
BORZ SHOP
@borzshop1337
On this record: Topic · Growth · Engagement · Posts · Cite this entry
2,534subscribers
+281 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002089770805 |
|---|---|
| Type | Channel |
| Username | @borzshop1337 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/borzshop1337 |
Topic
Memes & entertainment — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 56% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 22:55 | 2,534 | +297 |
| 3 Nov 2026, 13:49 | 2,237 | +87 |
| 31 Oct 2026, 23:05 | 2,150 | +258 |
| 28 Oct 2026, 12:50 | 1,892 | -6 |
| 25 Oct 2026, 18:41 | 1,898 | -12 |
| 22 Oct 2026, 10:27 | 1,910 | -7 |
| 19 Oct 2026, 12:57 | 1,917 | -8 |
| 16 Oct 2026, 17:06 | 1,925 | -10 |
| 14 Oct 2026, 00:16 | 1,935 | -22 |
| 9 Oct 2026, 01:19 | 1,957 | -20 |
| 2 Oct 2026, 04:58 | 1,977 | -68 |
| 16 Sept 2026, 19:21 | 2,045 | -18 |
| 12 Sept 2026, 13:18 | 2,063 | -15 |
| 8 Sept 2026, 15:36 | 2,078 | -33 |
| 3 Sept 2026, 16:41 | 2,111 | -19 |
| 31 Aug 2026, 09:32 | 2,130 | -15 |
| 28 Aug 2026, 03:17 | 2,145 | -12 |
| 24 Aug 2026, 23:08 | 2,157 | -18 |
| 21 Aug 2026, 03:06 | 2,175 | -23 |
| 17 Aug 2026, 17:57 | 2,198 | first reading |
Engagement
19 posts held, back to 12 July 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 19 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
как заебали малолетки сидящие на пвз с друзьями
‼️едет к покупателю
так
рассмотрю покупку опта ветровок горпкор тематики @bidlo32
сегодня скидки
заходите
meetly-date.ru
@Meetly_Date_Bot зайдите потыкайте
ищу монтажера, нужно сделать рекламный ролик до минуты @bidlo32
будем сразу залетать с осенних шмоток
до осени обнов не будет так что пишите по позициям вверху, договоримся
Showing the 12 most recent of 19 posts we hold for @borzshop1337. 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.
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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“BORZ SHOP” (@borzshop1337), 2,534 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/borzshop1337.
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.