Channel photo removed
Channel
STSB FESS
@STSBFESS
On this record: Growth · Engagement · Posts · Citations · Cite this entry
113subscribers
-6 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002008402863 |
|---|---|
| Type | Channel |
| Username | @STSBFESS |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 27 August 2026 |
| On Telegram | t.me/STSBFESS |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 14:44 | 113 | -2 |
| 20 Aug 2026, 11:46 | 115 | -3 |
| 13 Aug 2026, 09:04 | 118 | -1 |
| 9 Aug 2026, 04:17 | 119 | no change |
| 6 Aug 2026, 22:27 | 119 | first reading |
Engagement
20 posts held, back to 2 March 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 20 posts for this entry, the most recent from 18 March 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
hi @durov @telegram i would like to convey that, there is no action that violates the terms and conditions of telegram here, i hope, telegram has a wise way, in managing problems, before doing strict action, such as banning/blocking a telegram channel, thank you!
Sticker, posted without a caption
𝐂𝐋𝐎𝐒𝐄 𝐌𝐄𝐍𝐅𝐄𝐒𝐒 »»---------------¤-----------------«« Selamat malam lola! 🐦 Malam yang indah untuk bermimpi nih dan ini juga saatnya minlol pamit ya lola! 🐦 Terima kasih sudah mengirimkan menfess dengan tertib lola! 🐦 Selamat bertemu esok hari dengan semangat baru ya! Good night dari minlol! 🐦 ‧₊𓂃𓂃𓂃𓂃𓂃𓂃𓂃𓂃𓂃𓂃𓂃𓂃𓂃𓂃𓂃₊‧ #menfess © 𝐭.𝐦𝐞/𝐒𝐓𝐒𝐁𝐅𝐄𝐒𝐒
Sticker, posted without a caption
!ciduk terciduk seignour dan carmen dating.
!bucin SUNGHOON CAKEP
!STSB info thr
!bucin love dede aka ❤️
!STSB Hari ini pengen gibah
!STSB Semangat yang ikut lomba, walau banyak hehe nya
Sticker, posted without a caption
Showing the 12 most recent of 20 posts we hold for @STSBFESS. 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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“STSB FESS” (@STSBFESS), 113 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/STSBFESS.
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.