Channel name was changed to «🔒ꪆ 𝘽𝘼𝙔𝙁𝙀𝙀𝙎 𝙁𝙇𝙊𝙊𝘿:베프스 🍰 ୧ | +24»

Channel
🔒ꪆ 𝘽𝘼𝙔𝙁𝙀𝙀𝙎 𝙁𝙇𝙊𝙊𝘿:베프스 🍰 ୧ | +24
@bayfeesfld24
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
52subscribers
+0 since we began measuring on 27 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003921686610 |
|---|---|
| Type | Channel |
| Username | @bayfeesfld24 |
| Description | ⲃⲗⲁⲇⲉⲗⲉц :: t.me/truegisellecrash ⲥⲟⲃⲗⲁⲇⲉⲗⲉц :: https://t.me/rami_iiiiii ⳝⲩⲥⲧ :: https://t.me/boost/bayfeesfld24 ⳝэύⲫυυⲥⲥ ⲙυⲙυ ава сделано у @HEELIP0RT Брак - @plush_flood1 Братья - @mirael_flood Сестры - @ymfFLD |
| First recorded | 27 September 2026 |
| Last confirmed live | 27 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/bayfeesfld24 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Sept 2026, 21:22 | 52 | no change |
| 27 Sept 2026, 20:47 | 52 | first reading |
Engagement
16 posts held, back to 24 September 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 1 page of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 195.3%
- avg views ÷ 52 subscribers
- Avg views / post
- 102
- 15 posts measured
- Reaction rate
- 3.38%
- reactions ÷ views · ER floor
- Posts in window
- 16
- of 16 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 12 of 15 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 25 September 2026 |
|---|---|
| Posts held | 16 (24 September 2026 – 25 September 2026) |
| Views total | 1,523 |
| Reactions total | 45 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Sept 2026, 21:22 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
- Photos
- 248
- Videos
- 117
- Links
- 125
Lifetime counters from Telegram’s own channel header, read 27 September 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.
- Video runtime
- 33s
- Average length
- 17s
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
45 reactions across 12 posts, in 8 distinct kinds. The most used accounts for 22.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5314359946706458893 | 10 | 22.2% | |
| custom 5253532669945361225 | 8 | 17.8% | |
| custom 5316651285989069728 | 8 | 17.8% | |
| custom 5314385634905856414 | 5 | 11.1% | |
| custom 5330467147808279996 | 5 | 11.1% | |
| custom 5375577541505486000 | 4 | 8.89% | |
| custom 5343635642091870147 | 3 | 6.67% | |
| custom 5314374841653041353 | 2 | 4.44% |
Custom emoji. Every row above is a 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 12 of the 16 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 45 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 24 September 2026 to 25 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.
Recent posts
Sticker, posted without a caption
bayfees flood закрывается.🤩 ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ не думала, что до этого дойдёт.. но, к сожалению, да. это было сложное решение для меня. после того, как жизель ушла с роли владельца, я поняла, что не справлюсь сама. после ухода жизель ушла мока, админ по чату, и я поняла, что флуд уже невозможно спасти. поэтому я приняла решение закрыть его. как бы я не хотела этого осознавать, но да — всё закончилось в один ден…
custom 52535326699453612253custom 53143599467064588932custom 53166512859890697282custom 53304671478082799961custom 53436356420918701471
Sticker, posted without a caption
ребята, я ухожу из роли владельца... я думала днями и ночами, и решила что у меня нету времени вести флуд, поэтому будет вести совлд рами, всю должность я даю ей, писать все тоже ей, по поводу союза также ей!! вы были милыми зайки!!!😭 буду помнить об этом флуде в котором находились милые участники, милые союзы, спасибо вам что заключали союзы именно с нами!! но, всегда наступает конец, и вот, я ухожу с роли владельца…
custom 52535326699453612252custom 53143599467064588932custom 53143748416530413532custom 53143856349058564141
ребята, я уж не знаю что делать, многие люди выходят со флуда, многие остаются поддержать у нас кризис какой то если честно происходит, я не знаю что делать.. шанс идти дальше очень мало, темболее владелец(я) очень занята, что даже нету времени на рпт... я не знаю как еще продолжать.. я боюсь это говорить ноо... мы возможно закроемся... #BFSrp
custom 52535326699453612251custom 53143856349058564141
🤩🌟 ɯυɳы пթ𐐫фυⲗᧉʋ🤩 🤩 🤩 🤩 🤩 🤩 🤩 🤩 🤩 🤩 ყсл𐐫вuя 🌟 🤩𑄙1. пеթеслɑть эт𐐫т п𐐫ст в ʋнф𐐫 🤩𑄙2. п𐐫дпυскɑ , թк 🤩𑄙3. скթuн թк в к𐐫мм , ყкɑзɑть ɑвყ 🤩ᧉслu нɑд𐐫🤩 ⚡️ ⚡️ 🤩 🤩 🌟🤩 🤩 🤩 🤩 🤩🤩 16🤩16
custom 52535326699453612251custom 53166512859890697281custom 53755775415054860001
правила союзов изменились, если будут разрывы то пишите @ikffkl » #clvrp #сзрп
custom 53143599467064588931custom 53143856349058564141custom 53166512859890697281
! ! 𝗻۪𝝴ꭐ꯭ 𝘃𝝸๋𝗱𝝴𑄝ֺ # 🌆 —————————— U ´꓃ ` U 𝗶𝗱: trend ᧉⅾı๋𝘁𐐫𝗿ִ: minnie 𝘁𝘁 lı๋𝗻𝗸ֹ —> клик #кнтрп + рк
custom 53143599467064588931custom 53166512859890697281custom 53304671478082799961
@Angel_of_shadows1 скип
custom 53143856349058564141custom 53436356420918701471custom 53755775415054860001
ᅟ. ☾ ݁ ᯓ ˖ 𝐑ed 𝐉u𝐢ce nɑѵıgɑtᎥ𑄝ꪀ | +084 ' ( ၴႅၴ𓇼 💙 블랙핑크 rꫀd juicꫀ | · b𑄝𑄝sт ◠ L𑄝𑄝k, here are the r𑄝lꫀs 🪪 𑄝nly вᥙsy r𑄝lꫀs 바쁜 역할만 해당 ᅟᅟгᥙlꫀs ينظر 🪙 - : ︵⏝ p𐐼тꫀꪀִt 𐙚 𐐼ðмıns Nizz × гꫀst グリー 🪭 ᯓ 〜 검은색・ピンク |ᥴlꫀaηinĝ 𑇛 ݁ ᩧ TᎥкt𑄝k: ⟡ ᥙꪀᎥoꪀִ المرجان L𝔦nꫀs ᪃ ๋ ࣭ ꫂ طرب jennie ⭐
custom 52535326699453612251custom 53143599467064588931custom 53436356420918701471
🎀🎀🎀🎀🎀🔤ссᨵׁׅׅцꭎɑׁׅцꭎꭎ 🎀🎀🎀от:: ᧉнᧁׁжყнɑׁׅ ɑׁׅყⲧᧁׁоթꪒɑׁйⲧ ❤ 🎀 ⲧемɑׁׅ:: какой вы клип кпоп песни? ➿ 🤩 ➿ • ➿ 🤩 ➿ • ➿ 🤩 ➿ • ➿ 🤩 🧸 ყƈꪒоϐꭎя:: О1. подписка на инфо (проверяется) О2. рп в инфо // скинуть 3 друзьям (скрин в комм, сз не надо) О3. скинуть аву и юз О4. ждать!! ➿ 🤩 ➿ • ➿ 🤩 ➿ • ➿ 🤩 ➿ • ➿ 🤩 🎀🎀🎀🎀🎀ⲙеƈⲧɑׁׅ:: 11 // 11 🧸
custom 53143856349058564141custom 53304671478082799961custom 53755775415054860001
Showing the 12 most recent of 16 posts we hold for @bayfeesfld24. 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
Names
Channels on the register whose handles appear in this channel's posts.
@chisiflood · 1072 postsᴀɴɢᴇʟ ᴏꜰ ꜱʜᴀᴅᴏᴡs info
@Angel_of_shadows1 · 3331 postпереходник
@kaefell · 11 postᵖ²⁰ʈmᥱ.թᥣᴜડꚕ fᥣ𑄝𑄝𝕕.INFO
@plush_flood1 · 1761 postРП В ЛС 𝐫𝐞𝐝_𝐣𝐮𝐢𝐜𝐞 〽️ ⁱⁿᶠᵒ
@red_juice · 1761 postСоюзы.
@red_juice_Flood · 81 postSeasons flood || info
@seasonsok · 1701 post𑣲 귀.𝗬𝗔𝗠𝗙𝗜 𝖥𝖫𝖣 🔒
@ymfFLD · 731 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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“🔒ꪆ 𝘽𝘼𝙔𝙁𝙀𝙀𝙎 𝙁𝙇𝙊𝙊𝘿:베프스 🍰 ୧ | +24” (@bayfeesfld24), 52 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/bayfeesfld24.
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.