что это, огоооо, скорее залетаем😱😱😱
Signed yànix
Channel
@jgugfijh
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
30subscribers
+1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001927831426 |
|---|---|
| Type | Channel |
| Username | @jgugfijh |
| Created | 31 July 2023 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/jgugfijh |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 09:14 | 30 | +1 |
| 11 Aug 2026, 04:47 | 29 | no change |
| 6 Aug 2026, 10:06 | 29 | first reading |
10 posts held, back to 31 July 2023 — 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 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 10 posts for this entry, the most recent from 30 April 2024. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 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.
84 reactions across 5 posts, in 20 distinct kinds. The most used accounts for 14.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🥴 | 12 | 14.3% | |
| custom 5221998216899207250 | 9 | 10.7% | |
| ❤ | 9 | 10.7% | |
| ❤🔥 | 9 | 10.7% | |
| 💋 | 8 | 9.52% | |
| custom 5224340812321528425 | 6 | 7.14% | |
| custom 5224373140540365191 | 5 | 5.95% | |
| custom 5346295021417014236 | 4 | 4.76% | |
| custom 5222261605768633909 | 3 | 3.57% | |
| custom 5224669536233463123 | 3 | 3.57% | |
| custom 5463080752767836464 | 3 | 3.57% | |
| 🔥 | 3 | 3.57% | |
| custom 5224298944980327656 | 2 | 2.38% | |
| custom 5224497320929795043 | 2 | 2.38% | |
| custom 5222038052720876577 | 1 | 1.19% | |
| custom 5222428048636256063 | 1 | 1.19% | |
| custom 5224186176319005123 | 1 | 1.19% | |
| 💅 | 1 | 1.19% | |
| 💘 | 1 | 1.19% | |
| 💯 | 1 | 1.19% |
Custom emoji. 12 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 5 of the 10 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 84reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 31 July 2023 to 30 April 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.
что это, огоооо, скорее залетаем😱😱😱
Signed yànix
львовские закрываются. мне очень жаль, что так получается но я совсем перегорел, а тянуть на просто надо, я не хочу. спасибо всем, что были с нами, чат останется, потому что отпускать этих ребяток я не хочу, не могу обещать, что мы вернемся, но такая возможность есть. союзы разрываются. мужья навсегда наши. не хочу писать что-то большое, потому что нет слов, но так надо. патент и название остается за нами, за свое …
Signed yànix
💚вьюсу больше не наливаем.
custom 52222616057686339093custom 52243408123215284253custom 52246695362334631233custom 52220380527208765771custom 52243731405403651911custom 52244973209297950431
Signed yànix
за оформление благодарим @incantost.
Signed yànix
Video, posted without a caption
Signed yànix
— 28.01.2024.— в этот день Львовские дарят Атлантиде свое горячее африканское сердце, сязывая узами теплого и понимающего брака. мы обещаем, что с нами вам будет хорошо и никак иначе, ценить, хранить этот брак, вкладывать в него душу всегда останется самым главным аспектом в нашей семейной жизни, любимые. — Lvovskiye ❤️🔥 Atlantis —
custom 54630807527678364643custom 53462950214170142362custom 52224280486362560631custom 52241861763190051231custom 52243408123215284251custom 52244973209297950431
А у льва есть то, ради чего он должен убивать — его маленькие львята, что ждут отца-охотника.
❤🔥3🥴3custom 52219982168992072503❤2💘1custom 52243731405403651911
Signed yanix lvsk dnvr.
💚lvovskiye f'm. •» administration•» rules union › chat •» union list Yanis•» union list Views •» bot•» family •» archives•» patent инициал •» lvsk прем •» #lvskfm
custom 52219982168992072505❤4❤🔥4💋4🥴3custom 52243731405403651913custom 52243408123215284252💅1
патент на название "львовские" придумано нашей семьей и официально закреплено за нами с 15 февраля 2022 года. увидев на просторах вирта такое же название, у нас есть все полномочия попросить сменить его, в случае отказа и неприемлемого поведения конфликт будет выложен на публику для дальнейшего разбирательства, подключая свою аудиторию. • так же тематика с животным - львом,закреплена за нашим кланом,мы единственные …
🥴6💋4❤3❤🔥2🔥2💯1custom 52219982168992072501custom 52242989449803276561
Channel created
Showing the 10 most recent of 10 posts we hold for @jgugfijh. 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 — 757,318 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
@jgugfijh named 3 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“lvovskiye fam” (@jgugfijh), 30 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/jgugfijh.
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.