Telegram RegisterThe public register of Telegram

Channel

Pov :

@un_f10

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

199subscribers

+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-1002645078069
TypeChannel
Username@un_f10
Descriptionلا يـوجـد نـص مـُعـبر . @U9IUI
CreatedBetween 1 March 2025 and 5 June 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/un_f10

Growth

1997 Aug 2026, 16:22 — 199 subscribers8 Aug 2026, 11:33 — 199 subscribers7 Aug 2026, 16:228 Aug 2026, 11:33
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 198–200 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 11:33199no change
7 Aug 2026, 16:22199first reading

Engagement

19 posts held, back to 5 June 2025the 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 19 posts for this entry, the most recent from 17 June 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
22
Videos
6
Links
3

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

Reaction mix

1,172 reactions across 17 posts, in 10 distinct kinds. The most used accounts for 34.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💘40734.7%
custom 576719264666983392820617.6%
custom 587737460810501868816213.8%
custom 593174730063951063815413.1%
custom 5888992430216190114675.72%
custom 5265214925155889614665.63%
custom 5233261897481992251574.86%
custom 5767245466177639817221.88%
custom 5323411465728715749181.54%
custom 5327911187000604722131.11%

Custom emoji. 9 of the rows above are 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 areTelegram’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 17 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 1,172reactions 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 5 June 2025 to 17 June 2025, 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
432
across the posts below
Posts paid on
16
of 19 we hold a reading for · 84%
Most on one post
129
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @un_f10. 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 19 most recent posts we hold for this entry, published 5 June 2025 to 17 June 2025. 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

17 Jun 2025, 21:38 UTC297 viewsread 8 August 2026
Forwarded from @hhhuhl

روليت فائز 25 نجمه الشرط تشترك هنا : @Just_Arisa1 عدد المشاركين : 57 روليت سراب

Signed مؤمل

17 Jun 2025, 18:14 UTC310 viewsread 8 August 2026
Forwarded from @COOORAN

مُسابقة سريعة يم منتظر الفائز : 250 نجمة ⭐️ رشق : طرد بسِرعه النجمة بالقناة : 2x النجمة بالخاص : 3x تريد تشارك؟ اسمك هنا @TwdeBOT

Signed 𝖢𝖺𝗌𝗌𝖾𝗅 𝖲𝗉𝗂𝖽𝖾𝗋

13 Jun 2025, 12:45 UTC≈1,170 views103 reactions7 Starsread 8 August 2026

وأقبلَ العيدُ بالأفراحِ مُنتشيًا ‏يا فرحةَ العيدِ زوري كل أحبابي

custom 593174730063951063871custom 588899243021619011432

Signed 𝘿𝙚𝙫

13 Jun 2025, 11:31 UTC≈1,130 views118 reactions6 Starsread 8 August 2026
Photo

Photo, posted without a caption

custom 593174730063951063883custom 588899243021619011435

Signed 𝘿𝙚𝙫

12 Jun 2025, 02:12 UTC≈1,250 views47 reactionsread 8 August 2026

حلوي الجديد 1-ابقى ثابت بلقناه يوميه روليت واوعدك راح تفوز 2-شيل الكتم عم القناه حبي 3-دز قناتك اردها الك ❤ @Rioso_bot

💘21custom 576724546617763981714custom 532341146572871574912

12 Jun 2025, 00:18 UTC≈1,150 views64 reactions5 Starsread 8 August 2026
Photo

Photo, posted without a caption

💘50custom 57672454661776398178custom 53234114657287157496

Signed 𝘿𝙚𝙫

9 Jun 2025, 18:28 UTC≈1,680 views81 reactions20 Starsread 8 August 2026

فَتًى جَاهَدَ الدُّنْيَا وَجَاهَدَ أَهْلَهَا ‏وَفِي نَفْسِهِ لَمْ يَدْرِ كَيْفَ يُجاهدُ

custom 587737460810501868881

9 Jun 2025, 18:19 UTC≈1,660 views81 reactions10 Starsread 8 August 2026
Photo

Photo, posted without a caption

custom 587737460810501868881

9 Jun 2025, 00:25 UTC≈1,400 views46 reactions45 Starsread 8 August 2026

من ذا الذَي أغواكَ عن متاهاتِ حُبي ورمَيتني بسيف هجركَ وأضعتني

custom 576719264666983392846

Signed ⌯ ˹𝘿𝙚𝙫˼

9 Jun 2025, 00:10 UTC≈1,430 views54 reactions34 Starsread 8 August 2026
Photo

Photo, posted without a caption

custom 576719264666983392854

Signed ⌯ ˹𝘿𝙚𝙫˼

8 Jun 2025, 18:10 UTC≈1,340 views42 reactions53 Starsread 8 August 2026

لا يُغريك هذا النور لاتَقترب نارٌ أنا فيِ موطنٍ رثٍ خَرِب

custom 576719264666983392842

8 Jun 2025, 18:09 UTC≈1,330 views64 reactions38 Starsread 8 August 2026
Photo

Photo, posted without a caption

custom 576719264666983392864

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

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

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

“Pov :” (@un_f10), 199 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/un_f10.

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.