Telegram RegisterThe public register of Telegram
Telegram profile photo for yosshi316

Channel

yosshi316

@Yosshineco

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

131subscribers

+19 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1004217547684
TypeChannel
Username@Yosshineco
CreatedBetween 1 May 2026 and 29 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live12 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 12 September 2026
On Telegramt.me/Yosshineco

Growth

112131121.510 August 2026 — 112 subscribers11 August 2026 — 112 subscribers19 August 2026 — 117 subscribers26 August 2026 — 122 subscribers3 September 2026 — 129 subscribers12 September 2026 — 131 subscribers10 August 202612 September 2026
6 measurements spanning 32 days, net +19. 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 109–134 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Sept 2026, 04:37131+2
3 Sept 2026, 15:58129+7
26 Aug 2026, 15:38122+5
19 Aug 2026, 10:57117+5
11 Aug 2026, 14:24112no change
10 Aug 2026, 21:16112first reading

Engagement

17 posts held, back to 29 July 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 17 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

82 reactions across 11 posts, in 9 distinct kinds. The most used accounts for 29.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52291773363388536032429.3%
custom 52292246024539462612328.0%
custom 52290266130515359871518.3%
custom 534354422371296366656.10%
👻56.10%
custom 534845299767012156033.66%
custom 538676770083808288433.66%
custom 519742940194329683022.44%
custom 522916509997702747122.44%

Custom emoji. 8 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 are Telegram’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 12 of the 17 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 82 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 29 July 2026 to 10 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

10 Aug 2026, 13:59 UTC47 views5 reactionsread 10 August 2026

кто может код от той хауса дать за артик

custom 52292246024539462613custom 53484529976701215602

5 Aug 2026, 22:24 UTC138 viewsread 10 August 2026

Ота на Артик мне скушно любовь формат с ренером/без

5 Aug 2026, 22:12 UTC135 views9 reactionsread 10 August 2026
Photo

Сново оту давайте Перерисовали прошлый реф

custom 52292246024539462619

4 Aug 2026, 14:32 UTC150 views14 reactionsread 10 August 2026
Photo

не стыдно тебе да

custom 52291773363388536038custom 52290266130515359874custom 52292246024539462611custom 53435442237129636661

4 Aug 2026, 11:04 UTC134 views1 reactionsread 10 August 2026

Кто хочет фулл скетчи по 100 руб

custom 52291773363388536031

4 Aug 2026, 09:24 UTC149 views6 reactionsread 10 August 2026
Photo

за артик отдам хочу избавится автор я

custom 52290266130515359876

4 Aug 2026, 08:45 UTC160 viewsread 10 August 2026

у кого есть чернобелые персы я хочу чкрно белых перслнажей пишите сразу с ценой в рублях кроме рубелй могу за персонажец с канала https://t.me/yooshi_perrs

2 Aug 2026, 18:54 UTC156 views2 reactionsread 10 August 2026

Обещанное флуд тут

custom 52292246024539462612

2 Aug 2026, 18:53 UTC279 views3 reactionsread 10 August 2026
Photo

🔠👀👀👀👀👀👀❕❕❕ 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 🌟🌟🌟🌟🌟🌟призы!!!!! ➿1️⃣ место 1️⃣0️⃣0️⃣0️⃣ рублей ➿2️⃣ место 5️⃣0️⃣0️⃣ рублей ➿3️⃣ фулл арт от меня условия!➿➿➿➿➿➿ репост в канал от 10+ или 2 друзьям пруфы репоста скидывайте в комента Нарисовать или сделать анимацию любого формата скетч, полноцвет, 2D-анимация, GIF и вобше што угодно хоть гуро или нсвф-с даными персонажами Персонажи: Doris, Rory, 316, Arma Важно: работа должна быть новой, с

custom 52291773363388536033

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

Forward network

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.

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

“yosshi316” (@Yosshineco), 131 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/Yosshineco.

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.