Sticker, posted without a caption

Channel
STREETFESS!
@StreetFess
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Cite this entry
11,208subscribers
+2,272 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1003443673260 |
|---|---|
| Type | Channel |
| Username | @StreetFess |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 4 September 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 4 September 2026 |
| On Telegram | t.me/StreetFess |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Sept 2026, 23:39 | 11,208 | +117 |
| 3 Sept 2026, 09:33 | 11,091 | +93 |
| 2 Sept 2026, 06:22 | 10,998 | +83 |
| 1 Sept 2026, 02:46 | 10,915 | +121 |
| 31 Aug 2026, 00:14 | 10,794 | +122 |
| 29 Aug 2026, 22:24 | 10,672 | +81 |
| 28 Aug 2026, 22:26 | 10,591 | +97 |
| 28 Aug 2026, 00:34 | 10,494 | +57 |
| 27 Aug 2026, 02:45 | 10,437 | +84 |
| 26 Aug 2026, 05:26 | 10,353 | +115 |
| 25 Aug 2026, 05:54 | 10,238 | +65 |
| 24 Aug 2026, 04:42 | 10,173 | +366 |
| 20 Aug 2026, 09:39 | 9,807 | +144 |
| 17 Aug 2026, 16:28 | 9,663 | +446 |
| 14 Aug 2026, 06:57 | 9,217 | +147 |
| 10 Aug 2026, 21:58 | 9,070 | +112 |
| 7 Aug 2026, 16:09 | 8,958 | +22 |
| 6 Aug 2026, 18:02 | 8,936 | first reading |
Engagement
500 posts held, back to 6 August 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 37 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 1.26%
- avg views ÷ 11,208 subscribers
- Avg views / post
- 141
- 440 posts measured
- Reaction rate
- 4.06%
- reactions ÷ views · ER floor
- Posts in window
- 440
- of 500 held
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. It is computed over the 67 of 440 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 500 (6 August 2026 – 2 September 2026) |
| Views total | 61,997 |
| Reactions total | 418 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 02:15 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.
What this channel posts
- Video runtime
- 1m 22s
- Average length
- 21s
Measured directly from 4 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
436 reactions across 62 posts, in 9 distinct kinds. The most used accounts for 59.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 258 | 59.2% | |
| 🔥 | 106 | 24.3% | |
| ❤🔥 | 25 | 5.73% | |
| 🤩 | 15 | 3.44% | |
| 🍓 | 11 | 2.52% | |
| ☃ | 7 | 1.61% | |
| 😢 | 7 | 1.61% | |
| 🐳 | 6 | 1.38% | |
| 🆒 | 1 | 0.229% |
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 74 of the 500 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 436 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 500 most recent posts we hold, published 6 August 2026 to 2 September 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.
Telegram Stars
- Stars received
- 2
- across the posts below
- Posts paid on
- 1
- of 500 we hold a reading for · 0.2%
- Most on one post
- 2
- single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @StreetFess. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 500 most recent posts we hold for this entry, published 6 August 2026 to 2 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Recent posts
🦅 . Whoop, it's time to close. Massive thanks to every-Roadies who joined and spent time hanging out, sharing ideas, and keeping the menfess alive throughout my shift. If there is any mistake from my shift, feel free to reach out @StreetComplaintBot we'll sort it out. And, don’t forget to check our mates at @CortisFess & @TreasuresFess. That's all for now, see you on the next shift.
Sticker, posted without a caption
#Streetz .dd bingung kok tiba-tiba di gift sama epic gift rewards
#Streetz malu kali typo diliat banyak orang 😂🤣😡🤣😂🤣😜🤣😂🤣😜🤣😂🥺😜🥺😡😂🥺😜🥺😡🥶😢🤣😜🥶😢😒👎😢✌️😒🥺😎🤣😒😢🤣😒🥶😂🥺😜😂🤣😜🤣😂🤣😜🤣😂😜🤣😂🤣😜🤣😂🤣😜🤣😡😜🤣 gajadi tidur karna malu
#Streetz sbnrnya kalau kita pinter memanfaatkan SDS ( sumber daya setan ) kita bisa loh nyuruh nyi blorong buat membasmi hama tikus?yakan kan dpt 50:50 tu dia kenyang terus petani tenang
#Streetz sfm. @noqrris aku, masih sayang kamu. selalu. maafin aku ya... kalau kamu cari aku, jangan sungkan, aku masih disini buat kamu... kamu bilang kamu takut buat ditinggal bukan? aku ga akan ninggalin kamu sampe kamu sendiri yang ninggalin aku... i loved you, sayang...
#Streetz . sepi, lemes amat dies
#Streetz orang ganten mau tidur
#Streetz sorry sengaja dipencet, info aja sih kalo misalnya capek ada tempat bersandar, lu pada pasti gak ada :Vv
#Streetz kenapa kotak itu segiempat jb. tapi tau kan kalau semua kotak itu segiempat, tapi nggak semua segiempat itu kotak. kotak itu bentuk yang punya 4 sisi sama panjang dan 4 sudut siku-siku, sedangkan segiempat tuh semua bentuk yang punya 4 sisi, termasuk kotak, persegi panjang, layang-layang, trapesium, dll.
#Streetz eh kalian lucu banget kayak ulet teh pucuk
Showing the 12 most recent of 500 posts we hold for @StreetFess. 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.
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
Named by 5 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.
Names
Channels on the register whose handles appear in this channel's posts.
@cortisfess · 8,28821 postsTREASURES FESS.
@TreasuresFess · 6,41421 postsAHYELUDE.
@AHYELUDE · 5,0061 post𝒜 llurora⋆˚꩜。
@allurora · 1,7501 postVILENS: The Alter–Hero.
@babbymonster · 1,3871 postBellinors Familia: Crystal Sway of Regal Winglights. 🦚
@Bellinors · 13,3171 postCANOIRE
@canoires · 2,3131 postCASADITION.
@CASADITIONS · 1,2771 postChisthorn: Dew Of Falling Arrows.
@chisthorn · 1,7531 postdain ecstasy: lucky charm machine ✿˖°
@dainstasy · 3,4211 postFREEUNSUBS — Dain to the Rescue.
@dairescue · 1,0771 postENAMOURE: Starlit Sinners ♡
@Enamouries · 3,2341 postFlairmoné: Heartflicker.exe
@FLAIRMONE · 4191 postHARAMOUR
@haramour · 1,3641 postMAJERLE.
@HouseofMajerle · 3,4691 post.
@kronologipl · 11 postlend me a hand
@lendmeahand · 11 postCW, TW, Tone Tags, and Pronouns.
@ListCWTW · 3,9201 postThe Tale of Mondcroft: Where Every Bunny Belongs.
@Mondcroft · 4,3211 postS(cars)CF
@netwoarks · 11 postRITHELIA: Purely Princess ♡
@rithelia · 2,5041 postShardwhyte: Threads of the Shattered.
@Shardwhyte · 8,1961 postSTREETFESS RULES
@StreetRuless · 161 posthi
@ypiyue · 11 post
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@StreetFess named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 2 posts, 8 August 2026 – 9 August 2026
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 4 September 2026 — this entry's latest reading, not the date you are reading this.
“STREETFESS!” (@StreetFess), 11,208 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/StreetFess.
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.