Channel
@bladesgosoft
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Cross-platform identity · Cite this entry
6,726subscribers
+151 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002297074302 |
|---|---|
| Type | Channel |
| Username | @bladesgosoft |
| Description | быть или не быть, вот в чем вопрос |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 31 October 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 31 October 2026 |
| On Telegram | t.me/bladesgosoft |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 81% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Oct 2026, 15:46 | 6,726 | +8 |
| 28 Oct 2026, 06:25 | 6,718 | -1 |
| 24 Oct 2026, 20:01 | 6,719 | +7 |
| 21 Oct 2026, 10:50 | 6,712 | +8 |
| 18 Oct 2026, 02:16 | 6,704 | +10 |
| 15 Oct 2026, 05:39 | 6,694 | -1 |
| 12 Oct 2026, 12:20 | 6,695 | +18 |
| 6 Oct 2026, 00:57 | 6,677 | +82 |
| 28 Sept 2026, 14:20 | 6,595 | +8 |
| 15 Sept 2026, 10:16 | 6,587 | -4 |
| 11 Sept 2026, 17:57 | 6,591 | +9 |
| 6 Sept 2026, 23:19 | 6,582 | -5 |
| 1 Sept 2026, 22:56 | 6,587 | -7 |
| 30 Aug 2026, 00:08 | 6,594 | +1 |
| 27 Aug 2026, 08:35 | 6,593 | +2 |
| 24 Aug 2026, 12:37 | 6,591 | +3 |
| 20 Aug 2026, 20:57 | 6,588 | +2 |
| 17 Aug 2026, 19:15 | 6,586 | -11 |
| 15 Aug 2026, 03:03 | 6,597 | +7 |
| 11 Aug 2026, 18:12 | 6,590 | first reading |
25 posts held, back to 28 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 12 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 3 November 2026 |
|---|---|
| Posts held | 25 (28 July 2026 – 3 November 2026) |
| Views total | 30,710 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Nov 2026, 16:51 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 3 November 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.
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.
4,570 reactions across 17 posts, in 6 distinct kinds. The most used accounts for 52.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2,409 | 52.7% | |
| custom 5420618481286548656 | 852 | 18.6% | |
| custom 5224334515899482142 | 537 | 11.8% | |
| custom 5195081863013609757 | 327 | 7.16% | |
| custom 5246974774575377783 | 248 | 5.43% | |
| custom 5318890892390572293 | 197 | 4.31% |
Custom emoji. 5 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 17 of the 25 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 4,570 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 25 most recent posts we hold, published 28 July 2026 to 3 November 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.
с приходом осени у этого канала сначала отцвели комментарии, затем случился листопад, а вместе с ним упала и шляпа, которую вы мне подарили. теперь, когда стало совсем холодно, реакции скрылись под толстым слоем опавших листьев и инея.
Photo, posted without a caption
никакого смысла 🚶🏼♀️🏗👹🗡 by аня и сима
в активном поиске легенды: адекватного музыкального юриста для регулярной работы с андеграундной сценой. вдруг, среди вас есть такие? напишите: [email protected]
Photo, posted without a caption
Video message, posted without a caption
Video message, posted without a caption
‘аутичные люди не умеют дружить’ также вы с бро в каком-то японском селе спустя 15 лет ждете электричку
жаль, что это случается раз в миллениум
custom 519508186301360975774custom 522433451589948214234❤26custom 53188908923905722934
как приятно написать что-то красивое
❤112custom 542061848128654865638custom 524697477457537778319custom 53188908923905722936
I started going to a climbing gym here and 1) it’s located inside a castle 2) it has a vegetable garden in the backyard
❤167custom 542061848128654865662custom 519508186301360975733custom 522433451589948214210
солнечное затмение. напомнило ‘день независимости’. страшно. иду домой босиком. туфли натерли ноги.
custom 5224334515899482142110❤87custom 542061848128654865636custom 531889089239057229311
Showing the 12 most recent of 25 posts we hold for @bladesgosoft. 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.
We recorded 2 posts on @bladesgosoft as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
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.
Named by 4 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.
| Label | Soft Blade |
|---|
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 31 October 2026 — this entry's latest reading, not the date you are reading this.
“soft blade (FKA depth and clarity)” (@bladesgosoft), 6,726 subscribers as measured 31 October 2026. Telegram Register, tgregister.com/channel/bladesgosoft.
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.