Любитель SSO pinned «Во-первых с наступившим всех с новым годом! Ну во-вторых мои гоблины, последние месяцы времени вообще не хватает на ведение канала и написания обзоров по тому, что очень основательно начал заниматься сракбольной командой, канал скорее всего либо перестанет…»

Channel
Любитель SSO
@Ambassador_SSO_arhiv
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
148subscribers
+0 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002447868870 |
|---|---|
| Type | Channel |
| Username | @Ambassador_SSO_arhiv |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/Ambassador_SSO_arhiv |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 02:29 | 148 | no change |
| 14 Aug 2026, 02:17 | 148 | first reading |
Engagement
13 posts held, back to 24 November 2025 — 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 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 13 posts for this entry, the most recent from 6 January 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 12m 53s
- Average length
- 6m 27s
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
59 reactions across 12 posts, in 4 distinct kinds. The most used accounts for 69.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5312365097606212791 | 41 | 69.5% | |
| 🤔 | 8 | 13.6% | |
| ❤🔥 | 7 | 11.9% | |
| custom 5312456116553149443 | 3 | 5.08% |
Custom emoji. 2 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 12 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 59reactions 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 24 November 2025 to 6 January 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
Во-первых с наступившим всех с новым годом! Ну во-вторых мои гоблины, последние месяцы времени вообще не хватает на ведение канала и написания обзоров по тому, что очень основательно начал заниматься сракбольной командой, канал скорее всего либо перестанет функционировать, либо улетит в небытие, другого исхода я пока не вижу Ну, а если подводить итоги 25 года, то очень много было пройдено, много было написано обзоро…
❤🔥7
Я хочу купить корсет и поставить передний плет от прошки
custom 53123650976062127914
Наглядное фото разницы размеров облегченного и стандартного плейтбегов к корсетному бронежилету STRIKE
custom 53123650976062127914
Так как бывают разные задачи и оперативная обстановка может меняться, нас попросили разработать уменьшенный передний плейтбег к корсетному бронежилету STRIKE. У нас есть идея продавать как готовые сборки с уменьшенным передним плейтбегом, так и продавать передний плейтбег отдельно для тех сотрудников, кто ранее приобретал STRIKE и захочет уменьшить профиль жилета. Планируем запуск производства в январе.
custom 53123650976062127915
Еще одно видео,которое мы обещали вам показать по нашему плакарду!
custom 53123650976062127914
Как и обещали в пятницу - выкладываем небольшое видео по новому жилету PHOENIX 2.0
custom 53123650976062127914
Ахуеть
custom 53124561165531494433
Рады представить вам КАПы для корсета. Они уже добавлены на сайт и идут комплектами по две подушки меньшего и большего размеров - для возможности настроить их расположение специально под вашу анатомию!
custom 53123650976062127913
Добрый день! Фото установки "Варвара" на "Феникс" прикрепляю. На выставке были показаны концепты, в том числе и камербанды на "Феникс" , пока они на тестах, информация будет после их окончания.
custom 53123650976062127914
Интересно, что раньше произойдет, я выпущу обзор на слик или ССО выпустят наколенники на КОМБАТ Х?
🤔8
Photo, posted without a caption
custom 53123650976062127917
Showing the 12 most recent of 13 posts we hold for @Ambassador_SSO_arhiv. 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 — 1,365,178 of 1,550,220entries 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.
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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“Любитель SSO” (@Ambassador_SSO_arhiv), 148 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/Ambassador_SSO_arhiv.
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.