Channel
@sftbfam
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
45subscribers
+0 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001775528363 |
|---|---|
| Type | Channel |
| Username | @sftbfam |
| Created | 25 November 2023 — measured — dated from the channel’s first post |
| First recorded | 14 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/sftbfam |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 04:00 | 45 | no change |
| 14 Aug 2026, 03:50 | 45 | first reading |
3 posts held, back to 25 November 2023 — 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 3 posts for this entry, the most recent from 30 May 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 14 August 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.
822 reactions across 2 posts, in 15 distinct kinds. The most used accounts for 25.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 6048681083807992255 | 210 | 25.5% | |
| custom 5431411927374906173 | 135 | 16.4% | |
| custom 5193056609839887751 | 75 | 9.12% | |
| custom 5071184400260006993 | 65 | 7.91% | |
| custom 5084613633418199991 | 51 | 6.20% | |
| custom 5188682628030546501 | 48 | 5.84% | |
| 💔 | 43 | 5.23% | |
| custom 5312186384017013788 | 36 | 4.38% | |
| custom 4936167782573146917 | 33 | 4.01% | |
| custom 5355289288525236301 | 30 | 3.65% | |
| custom 5116414868357907335 | 22 | 2.68% | |
| custom 5172447776205702031 | 22 | 2.68% | |
| custom 4967504894756914060 | 18 | 2.19% | |
| custom 5174924430442234980 | 18 | 2.19% | |
| custom 5355063695368011135 | 16 | 1.95% |
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 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 2 of the 3 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 822reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 3 most recent posts we hold, published 25 November 2023 to 30 May 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.
🔤oftbox 🤩 266 🩸 Don’t compare your beginning to someone else’s middle 💋 🔤atent 🔤🔤ules🔤🔤oost 💋
custom 5431411927374906173103custom 507118440026000699350custom 518868262803054650136custom 508461363341819999129custom 511641486835790733522custom 517244777620570203122custom 493616778257314691721custom 531218638401701378820
Signed 725
с сегодняшнего дня, мы заявляем о том, что название «софтбокс» принадлежит только нам. если кто-то будет использовать его в качестве название, то мы имеем полное право попросить вас изменить его. кф был создан: 11.11.2023 возобновление патента: 25.11.2023
custom 6048681083807992255210custom 519305660983988775175💔43custom 543141192737490617332custom 508461363341819999122custom 531218638401701378816custom 535506369536801113516custom 507118440026000699315
Channel created
Showing the 3 most recent of 3 posts we hold for @sftbfam. 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 — 199,622 of 1,350,102entries 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.
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.
Named by 1 registered channel — 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.
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“Жабық” (@sftbfam), 45 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/sftbfam.
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.