Telegram RegisterThe public register of Telegram

Channel

JAPANESKYE

@J4p4n353

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

230subscribers

-2 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-1003956991597
TypeChannel
Username@J4p4n353
Created3 June 2026measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 8 August 2026
On Telegramt.me/J4p4n353

Growth

2302322317 Aug 2026, 22:47 — 232 subscribers8 Aug 2026, 10:05 — 232 subscribers8 Aug 2026, 11:52 — 230 subscribers7 Aug 2026, 22:478 Aug 2026, 11:52
3 measurements taken within a single day, net -2. 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 230–232 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 11:52230-2
8 Aug 2026, 10:05232no change
7 Aug 2026, 22:47232first reading

Engagement

7 posts held, back to 3 June 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.

ERR · 30 days
194.9%
avg views ÷ 230 subscribers
Avg views / post
448
4 posts measured
Reaction rate
0.714%
reactions ÷ views · ER floor
Posts in window
4
of 7 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 3 of 4 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held7 (3 June 20266 August 2026)
Views total1,793
Reactions total8
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 10:05 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

35 reactions across 4 posts, in 11 distinct kinds. The most used accounts for 17.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5238225810229320379617.1%
custom 5384595735876501222617.1%
custom 5240211008538041224514.3%
custom 5237914407920490621411.4%
custom 5345983339935330888411.4%
custom 538443317136434652138.57%
custom 523803244650668720225.71%
custom 535749133543778584425.71%
custom 536856518276102390112.86%
custom 543377990175900327912.86%
custom 546308970777467376312.86%

Custom emoji. Every row above is a 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 4 of the 7 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 35reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 7 most recent posts we hold, published 3 June 2026 to 6 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

6 Aug 2026, 20:05 UTC92 views1 reactionsread 8 August 2026

Наборы в чаты закрыты

custom 53459833399353308881

31 Jul 2026, 09:14 UTC349 views3 reactionsread 8 August 2026

Ищем админов по союзам и допов, все расскажем и покажем, писать @JAPANESKYE_bot

custom 52382258102293203793

24 Jul 2026, 09:43 UTC680 views4 reactionsread 8 August 2026
Photo

Photo, posted without a caption

custom 52379144079204906211custom 52382258102293203791custom 52402110085380412241custom 53459833399353308881

16 Jul 2026, 20:57 UTC990 views27 reactionsread 8 August 2026
Photo

Photo, posted without a caption

custom 53845957358765012226custom 52402110085380412244custom 52379144079204906213custom 53844331713643465213custom 52380324465066872022custom 52382258102293203792custom 53459833399353308882custom 53574913354377858442

Showing the 7 most recent of 7 posts we hold for @J4p4n353. 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 — 826,726 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.

Mentions

Named by 4 registered channels — 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.

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.

“JAPANESKYE” (@J4p4n353), 230 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/J4p4n353.

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.