Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝟤𝟦𝗁࿐ (Closed)

Channel

𝟤𝟦𝗁࿐ (Closed)

@Svt24h

On this record: Topic · Growth · Engagement · Reactions · Posts · Polls · Citations · Cite this entry

375subscribers

-38 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1002237725667
TypeChannel
Username@Svt24h
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live12 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 12 September 2026
On Telegramt.me/Svt24h

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 22 September 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

37541339412 August 2026 — 413 subscribers13 August 2026 — 413 subscribers21 August 2026 — 406 subscribers29 August 2026 — 397 subscribers4 September 2026 — 385 subscribers12 September 2026 — 375 subscribers12 August 202612 September 2026
6 measurements spanning 31 days, net -38. 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 369–419 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Sept 2026, 20:17375-10
4 Sept 2026, 23:20385-12
29 Aug 2026, 03:35397-9
21 Aug 2026, 08:34406-7
13 Aug 2026, 15:27413no change
12 Aug 2026, 23:16413first reading

Engagement

19 posts held, back to 4 April 2026the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 2 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

209 reactions across 10 posts, in 5 distinct kinds. The most used accounts for 47.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🍓10047.8%
💘5124.4%
😭3818.2%
🔥199.09%
🤝10.478%

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

Measured over the 19 most recent posts we hold, published 4 April 2026 to 2 August 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

2 Aug 2026, 09:05 UTC115 views41 reactionsread 12 August 2026

اهم، به دلیل یه سری مسائل ترجیح دادم به جای ادامه دادنِ اینجا، برم. ممنون که یه سال همراه 24h بودین و اگه هم تا الان صبر کردین، بازم متشکرم ازتون. :>

🍓34😭6🤝1

Signed yasu

17 Jun 2026, 13:56 UTC272 views16 reactionsread 12 August 2026

ورژن جدید اینجا هم درحال راه اندازیه

🍓16

Signed saya ( junior's simp )

17 Jun 2026, 13:56 UTC271 viewsread 12 August 2026
Forwarded from @SendHarfBot

‌ عه وا سلامممم نیخزحقححسجیحیحثخ

Signed saya ( junior's simp )

17 Jun 2026, 13:54 UTC282 views18 reactionsread 12 August 2026
Photo

من یه شاپی زدم که توش کلا از کیپاپ و کیدراما و انیمه و مانهوا و تایلند و .. این حرفا فتوکارت، پولاروید، فتوچارم، برچسب و جاسوییچی و این حرفا می‌زنم :< خوشحال می‌شم اگه یه سر بزنین و بیاین و این حرفا دیگه :<< @Indigoshop0_0

💘17🍓1

Signed saya ( junior's simp )

17 Jun 2026, 13:52 UTC245 views19 reactionsread 12 August 2026

اهم بچه‌ها *تکوندن تار عنکبوتا

🔥19

Signed saya ( junior's simp )

2 Jun 2026, 05:32 UTC344 views10 reactionsread 12 August 2026

:((( دورت بگردم :(( ایشالا به زودی برمی‌گردم :((

🍓10

Signed saya~

2 Jun 2026, 05:32 UTC314 viewsread 12 August 2026
Forwarded from @SendHarfBot

‌ منظورت چیه که تو رو یادمون رفته وقتی من هنوز منتظرتم🥺 تو بری کی میخواد برای من سونهون ناز بنویسه آخه🤧😭 اینا به کنار اون موقع دیگه سایا رو ندارممممنینژپینینیپیدین😭😭

Signed saya~

1 Jun 2026, 07:56 UTC305 viewsread 12 August 2026

عایا دورت بگردم من عزیزدلمی :(((🤩🤩

Signed saya~

1 Jun 2026, 07:56 UTC299 viewsread 12 August 2026
Forwarded from @SendHarfBot

‌ همیشه به فکرت بودم یاس، خیلی دلم برای حرفات و نوشته‌هات تنگ شده🥺 امیدورام کنکور و نهاییت رو عالی بدی🫶🏼💋

Signed saya~

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

1 Jun 2026, 07:11 UTCAnonymous Poll73 voters

بگین ببینم

  1. اینجارو به امان خدا ول کنم و کلوزد بزنم و کلا برم "آیا اصلا کسی مونده که به 24h دقت کنه؟"5%
  2. چنل جدید بزنم و مرتب تر اونجا ادامه بدم "آیا کسی هست که بیاد؟"97%

The shares total 102%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 19 most recent posts we hold, published 4 April 2026 to 2 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Forward network

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 1 registered channel — 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.

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

“𝟤𝟦𝗁࿐ (Closed)” (@Svt24h), 375 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/Svt24h.

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.