Telegram RegisterThe public register of Telegram
Telegram profile photo for ⌗𝘉𝘰𝘰𝘴𝘧𝘦𝘳 𝘤𝘰𝘯𝘧𝘦𝘴𝘴𝘪𝘰𝘯ᵕ◡

Channel

⌗𝘉𝘰𝘰𝘴𝘧𝘦𝘳 𝘤𝘰𝘯𝘧𝘦𝘴𝘴𝘪𝘰𝘯ᵕ◡

@boosfercf

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

12subscribers

+0 since we began measuring on 6 October 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004317183904
TypeChannel
Username@boosfercf
Descriptionза вопросами в соо канала @takeboosfercf_bot -тейки https://t.me/boost/boosfercf -буст
Created26 September 2026 — measured — dated from the channel’s first post
First recorded6 October 2026
Last confirmed live6 October 2026
Measurements held2
On Telegramt.me/boosfercf

Growth

126 Oct 2026, 06:47 — 12 subscribers6 Oct 2026, 07:22 — 12 subscribers6 Oct 2026, 06:476 Oct 2026, 07:22
2 measurements taken within a single day. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 11–13 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Oct 2026, 07:2212no change
6 Oct 2026, 06:4712first reading

Engagement

14 posts held, back to 26 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
930.8%
avg views ÷ 12 subscribers
Avg views / post
112
13 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
14
of 14 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 5 October 2026
Posts held14 (26 September 2026 – 5 October 2026)
Views total1,452
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Oct 2026, 07: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
8
Links
5

Lifetime counters from Telegram’s own channel header, read 6 October 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.

Recent posts

5 Oct 2026, 11:02 UTC3 viewsread 6 October 2026
Forwarded from @in_hsr_fd_hatePhoto

👻💚💚 🥹 in hsr fd hate .. 🎁 🥹 🤩десь вы можете высказать весь свой гнев по поводу персонажей / заданий / ивентов / локаций / фанатов чего то или кого то и т.д rules takebot mp adm

5 Oct 2026, 10:51 UTC3 viewsread 6 October 2026
Forwarded from @oliverscornerfpedfPhoto

⬜≡;- ꒰ 🌟 ꒱ — Пᴩиʙᴇᴛиᴋ! Мᴇчᴛᴀᴧ ᴏ ᴛᴏʍ, чᴛᴏбы ᴨᴏᴧучиᴛь ϶ᴄᴛᴇᴛичный ϶ʍᴏдɜиᴨᴀᴋ ᴄ Кᴧ϶ᴩ? — ﴾ 🌟 ﴿ ⬜⬜Иᴧи жᴇ ᴛᴇбᴇ инᴛᴇᴩᴇᴄнᴏ, ᴋᴀᴋ ɜʙучиᴛ Миᴄᴄ Циᴩᴋуᴧь? — ⁠「🌟 」 ⬜⬜⬜── ⊹₊˚‧︵‿₊୨ 🌟 ୧₊‿︵‧˚₊⊹ ── ⬜: ̗̀➛ ꒰ ✦ — Тᴏᴦдᴀ, ᴛᴇбᴇ ᴄюдᴀ! Зᴀхᴏди быᴄᴛᴩᴇᴇ, ⬜⬜Уᴦᴏᴧᴏᴋ Оᴧиʙᴇᴩᴀ ужᴇ ɜᴀждᴀᴧᴄя ᴛᴇбя!! — ✦ ꒱ 𓏴𓏴 ⬜⬜⬜── ⊹₊˚‧︵‿₊୨ 🌟 ୧₊‿︵‧˚₊⊹ ── ⬜╰┈➤ Нᴀʙиᴦᴀция 🗒 Рᴇᴋʙᴇᴄᴛы — 🎀 ˎˊ˗ ⬜⬜⬜⬜⬜cr: ZS2ZOMBIE on 📱

30 Sept 2026, 15:55 UTC37 viewsread 6 October 2026
Photo

∘₊✧──────✧₊∘ 𓏵‌.::администрация 01.::Ампл/Ампли-[🎪🎰] she/her::влд 02.::Вайнона-[🪷] she/her::впшер ∘₊✧──────✧₊∘

30 Sept 2026, 15:28 UTC32 viewsread 6 October 2026
Photo

∘₊✧──────✧₊∘ 𓏵‌.правила тейков 01.::ставьте оформу блин нафиг,пожалуйста #take ⏤͟͟͞͞☆ 𓏵‌.𝘣𝘰𝘰𝘴𝘧𝘦𝘳.𝘤𝘧⥤@takeboosfercf_bot кликабельно!! 02.::мы не выкладываем тейки с бб 03.::оставлять свой тгк/юз в тейках МОЖНО!!!!!!! 04.::под тв/кв обязательно ставить кровь,яркие цвета,вспышки и тп 05.::тейки,содержащие прем эмодзи не присылайте,оно слетит 06.::если Ваш тейк не выложили через 24 часа,продублируйте его 𓏵‌.правила ч…

26 Sept 2026, 11:59 UTC32 viewsread 6 October 2026
Photo

∘₊✧──────✧₊∘ 𓏵‌.::MP POST✶ 1.::порог 0+ 2.::не поддерживаем каналы,с которыми делаем вп 3.::можем отказаться от вп,умолчав причину 4.::повторное вп через 3 дня 5.::промежуток между вп 5 минут 6.::не делаем вп с кф на аморальные темы,с шок и 18+ контентом,личные каналы,рейд,флуды и т.п 7.::dni::база+хейтеры бусфера/майнкрафта,бб ⌗предлагать вп под постом ⌗ртшить это ∘₊✧──────✧₊∘

26 Sept 2026, 11:09 UTC52 viewsread 6 October 2026
Photo

∘₊✧──────✧₊∘ 𓏵‌.::𝘕𝘈𝘝𝘐𝘎𝘈⃝𝘛𝘐𝘖𝘕꙰☆ ⌗𝘳𝘵 𝘱𝘰𝘴𝘵 ☻ ⌗𝘮𝘱 𝘱𝘰𝘴𝘵 ⌗𝘢𝘥𝘮𝘪𝘯𝘪𝘴𝘵𝘳𝘢𝘵𝘪𝘰𝘯 67 ⌗𝘣𝘰𝘰𝘴𝘵 ★ ⌗𝘳𝘶𝘭𝘦𝘴 ∘₊✧──────✧₊∘

Showing the 12 most recent of 14 posts we hold for @boosfercf. 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

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

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 6 October 2026 — this entry's latest reading, not the date you are reading this.

“⌗𝘉𝘰𝘰𝘴𝘧𝘦𝘳 𝘤𝘰𝘯𝘧𝘦𝘴𝘴𝘪𝘰𝘯ᵕ◡” (@boosfercf), 12 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/boosfercf.

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.