Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝒀𝑼𝑲𝑰𝑪𝑯𝑰 𝑷𝑶𝑹𝑻|私を救ってください

Channel

𝒀𝑼𝑲𝑰𝑪𝑯𝑰 𝑷𝑶𝑹𝑻|私を救ってください

@yukichi_port

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

40subscribers

-1 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-1002553092367
TypeChannel
Username@yukichi_port
CreatedBetween 1 March 2025 and 27 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live16 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/yukichi_port

Growth

404140.57 August 2026 — 41 subscribers10 August 2026 — 41 subscribers16 August 2026 — 40 subscribers7 August 202616 August 2026
3 measurements spanning 9 days, net -1. 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 40–41 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 08:0440-1
10 Aug 2026, 18:1541no change
7 Aug 2026, 16:0941first reading

Engagement

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

Reaction mix

234 reactions across 11 posts, in 13 distinct kinds. The most used accounts for 20.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52174950381786400474820.5%
custom 54541723506458223393314.1%
🔥3314.1%
custom 52197233445212149332611.1%
❤‍🔥2611.1%
custom 5283248131327139387187.69%
custom 5427079203021396857166.84%
custom 5424821476152846075125.13%
custom 519752820766595249693.85%
custom 542699710901650250483.42%
custom 519980618960027340720.855%
custom 629864530710207239520.855%
custom 546081315176948104710.427%

Custom emoji. 11 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 11 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 234reactions 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 27 July 2025 to 3 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.

Telegram Stars

Stars received
10
across the posts below
Posts paid on
1
of 15 we hold a reading for · 7%
Most on one post
10
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @yukichi_port. 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 27 July 2025 to 3 May 2026. 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

3 May 2026, 05:01 UTCviews —

𝒀𝑼𝑲𝑰𝑪𝑯𝑰 𝑷𝑶𝑹𝑻|私を救ってください pinned «Here it is https://t.me/whereisheaven_port»

26 Apr 2026, 09:48 UTC43 views2 reactionsread 10 August 2026

Возможно скоро создам новый порт😊

❤‍🔥1🔥1

20 Apr 2026, 07:33 UTC48 viewsread 10 August 2026

Все оформление слетело.Жизнь без тгп слишком сложна.

20 Apr 2026, 07:32 UTC48 views4 reactionsread 10 August 2026
Photo

✨(•˕ •マ ࣪ ˖[ORDER!] ✦ ─ ˗ˋ (•˕ •マ バナーはユキチに注文してね . . ── ࣪✦ ࣪ ˖ 🍄—куку. (?) ✦ ─ ࣪˖ ࣪ (•˕ •マ ࣪ ˖ ── [自分のフォロワーたちが大好き]

🔥3❤‍🔥1

10 Oct 2025, 03:09 UTC180 views11 reactionsread 10 August 2026
Photo

🍓(•˕ •マ ࣪ ˖[PRACTICE!] ✦ ─ ˗ˋ (•˕ •マ 😌 バナーはユキチに注文してね ❌ ❌❌❌❌❌❌. ❌── ࣪✦ ࣪ ˖ 😌-Похоже больше не на баннер а на постер какой то простенький,лан✦ ─ ࣪˖ ࣪ (•˕ •マ ࣪ ˖ ──,⭐❌ ❌[Реакции(?)] 🎀 ❌❌[🎁自分のフォロワーたちが大好き]🎀

🔥4custom 52174950381786400474❤‍🔥2custom 51998061896002734071

9 Oct 2025, 05:57 UTCviews —

Channel name was changed to «𝒀𝑼𝑲𝑰𝑪𝑯𝑰 𝑷𝑶𝑹𝑻|私を救ってください»

9 Oct 2025, 05:43 UTC157 views13 reactionsread 10 August 2026
Photo

⭐️(•˕ •マ ࣪ ˖[PRACTICE!] ✦ ─ ˗ˋ (•˕ •マ 😌 バナーはユキチに注文してね ❌❌❌❌❌❌❌. ❌── ࣪✦ ࣪ ˖ 😣-Быстренько на паре накляпала✦ ─ ࣪˖ ࣪ (•˕ •マ ࣪ ˖ ──,⭐❌ ❌[Реакции(?)] ❌❌[🎁自分のフォロワーたちが大好き]🎀

custom 51975282076659524964custom 52174950381786400472custom 52197233445212149332custom 62986453071020723952❤‍🔥1🔥1custom 51998061896002734071

24 Aug 2025, 01:02 UTCviews —

𝒀𝑼𝑲𝑰𝑪𝑯𝑰 𝑷𝑶𝑹𝑻|私を救ってください pinned «Из за одной ситуации в жизни в итоге ничего не смогла сделать,по уши в долгах, что по заказам что и в рж,так что уйду пока не полегчает ну и пока не решу собственные проблемы,извините те кому я так и не сделала работу»

22 Aug 2025, 06:30 UTC255 views21 reactionsread 10 August 2026

Из за одной ситуации в жизни в итоге ничего не смогла сделать,по уши в долгах, что по заказам что и в рж,так что уйду пока не полегчает ну и пока не решу собственные проблемы,извините те кому я так и не сделала работу

custom 52174950381786400479custom 54541723506458223394custom 52832481313271393873custom 51975282076659524962custom 52197233445212149331custom 54269971090165025041custom 54270792030213968571

Showing the 12 most recent of 19 posts we hold for @yukichi_port. 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 — 547,375 of 1,549,376entries 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

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.

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

“𝒀𝑼𝑲𝑰𝑪𝑯𝑰 𝑷𝑶𝑹𝑻|私を救ってください” (@yukichi_port), 40 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/yukichi_port.

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.