Telegram RegisterThe public register of Telegram

Channel

наночка убежище

@uefna

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

46subscribers

+0 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1003474052658
TypeChannel
Username@uefna
CreatedBetween 1 November 2025 and 8 January 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live14 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/uefna

Growth

4614 Aug 2026, 01:35 — 46 subscribers14 Aug 2026, 21:08 — 46 subscribers14 Aug 2026, 01:3514 Aug 2026, 21:08
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 45–47 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 21:0846no change
14 Aug 2026, 01:3546first reading

Engagement

19 posts held, back to 8 January 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 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 29 May 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
2m 51s
Average length
17s

Measured directly from 10 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

93 reactions across 13 posts, in 7 distinct kinds. The most used accounts for 22.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52742205610425343252122.6%
custom 52694581466859018051819.4%
🕊1516.1%
💋1111.8%
custom 51884264504112091661010.8%
💘1010.8%
custom 533479339964606510788.60%

Custom emoji. 4 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 13 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 93reactions 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 8 January 2026 to 29 May 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

29 May 2026, 04:56 UTC115 views7 reactionsread 14 August 2026

https://t.me/milka_2oo9 ребяточки подпишитесь на мой телеграмм канал, там мое еблище, мне будет очень приятнооо 🥰

💘3💋2🕊2

29 May 2026, 04:51 UTC93 views7 reactionsread 14 August 2026
Forwarded from @babychkayaVideo

с днем рождения мою нанусичку WLW💕 cc mblless

💋3💘2🕊2

10 May 2026, 15:00 UTC300 views8 reactionsread 14 August 2026
Video

у моей дэвушки дэнь рождэния всэм привэт 2 id idk 1 rm amb1ix

💋3💘3🕊2

29 Mar 2026, 18:27 UTC329 views7 reactionsread 14 August 2026
Video

как всегда опоздала с трендом рм: тт сс: mblless

🕊4💋2💘1

21 Feb 2026, 18:29 UTC217 views3 reactionsread 14 August 2026
Forwarded from @babychkayaVideo

моя dream girl rm amarvllis cc mblless

💋1💘1🕊1

15 Feb 2026, 19:46 UTC486 views22 reactionsread 14 August 2026
Video

ну привет )) #edit ас: tt scp: ic3peach сс: mblless

custom 52694581466859018057custom 52742205610425343257custom 53347933996460651076custom 51884264504112091662

15 Feb 2026, 14:09 UTC139 views3 reactionsread 14 August 2026
Forwarded from @whlovrVideo

— я зависим от тебя как от допинга-допинга 🫀😘 cc we1kse ac chawerl all mine :: sdt любимки мои <3 + detishki / #sdt

custom 51884264504112091661custom 52742205610425343251custom 53347933996460651071

11 Feb 2026, 18:53 UTC175 views7 reactionsread 14 August 2026
Video

эдит парадеевич и кореш смотреть онлайн #edit id: tt scp: baby_milkk cc: mblless

custom 52694581466859018054custom 52742205610425343253

26 Jan 2026, 18:13 UTC187 viewsread 14 August 2026

канал превратился в фанклуб бэйбички пора удалять

26 Jan 2026, 18:02 UTC367 views4 reactionsread 14 August 2026
Video

люблю мою влв подругу #edit cc: mblless sdt: my stupid ho

custom 52742205610425343254

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

Citation-graph rank

Citation-graph rank — 1,044,181 of 1,480,688entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

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

“наночка убежище” (@uefna), 46 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/uefna.

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.