Telegram RegisterThe public register of Telegram
Telegram profile photo for Stylefactor_ru

Channel

Stylefactor_ru

@Stylefactor_ru

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

388subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001578752540
TypeChannel
Username@Stylefactor_ru
CreatedBetween 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live23 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 23 August 2026
On Telegramt.me/Stylefactor_ru

Growth

387388387.57 August 2026 — 388 subscribers8 August 2026 — 388 subscribers16 August 2026 — 387 subscribers23 August 2026 — 388 subscribers7 August 202623 August 2026
4 measurements spanning 16 days. 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 387–388 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 23:03388+1
16 Aug 2026, 05:28387-1
8 Aug 2026, 06:03388no change
7 Aug 2026, 23:42388first reading

Engagement

7 posts held, back to 13 October 2023the 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 7 posts for this entry, the most recent from 29 January 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
56m 02s
Average length
56m 02s

Measured directly from 1 video 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

83 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 72.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
6072.3%
🔥2226.5%
👍11.20%

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 4 of the 7 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 83reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 7 most recent posts we hold, published 13 October 2023 to 29 January 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.

Recent posts

29 Jan 2024, 11:53 UTC988 views18 reactionsread 8 August 2026
Video

✨Эфир о новостях Стильного клуба✨ Новые мероприятия, тарифы, стоимость и бонусы для участников🔥

🔥18

20 Oct 2023, 07:21 UTC≈1,430 viewsread 8 August 2026

Назначили первую встречу на понедельник на 17:00. Но многие пишут нам, что не успевают с работы, переходите на канале/ голосуйте, в какое время сможете успеть, мы открыты для вас 😁🌺

20 Oct 2023, 07:20 UTC≈1,110 viewsread 8 August 2026

Друзья, подписывайтесь на канал клуба- в понедельник первая тематическая встреча клуба, записывайтесь! Расскажу о чем клуб, какие в нем возможности, перспективы, прелести и Польша для Вас😊❤️

19 Oct 2023, 17:13 UTC≈1,010 views5 reactionsread 8 August 2026
Photo

Photo, posted without a caption

4🔥1

13 Oct 2023, 20:28 UTC904 views27 reactionsread 8 August 2026
Photo

Друзья, подвала в гостях в новом шоуруме наших друзей Бренда Eveester. Всё самое интересное примерила. Спрашивайте, расскажу, поделюсь советами 😊🫶

25👍1🔥1

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

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

“Stylefactor_ru” (@Stylefactor_ru), 388 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/Stylefactor_ru.

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.