Telegram RegisterThe public register of Telegram

Channel

johatsu

@johatsulive

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

38subscribers

+0 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002718468157
TypeChannel
Username@johatsulive
CreatedBetween 1 June 2025 and 31 August 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live10 August 2026
Measurements held2
On Telegramt.me/johatsulive

Growth

388 August 2026 — 38 subscribers10 August 2026 — 38 subscribers8 August 202610 August 2026
2 measurements spanning 3 days. 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 37–39 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 21:0038no change
8 Aug 2026, 01:4738first reading

Engagement

18 posts held, back to 11 March 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 18 posts for this entry, the most recent from 31 March 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
58
Videos
23
Links
8

Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
2m 37s
Average length
22s

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

60 reactions across 12 posts, in 8 distinct kinds. The most used accounts for 46.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2846.7%
custom 51908494905710008831016.7%
🔥915.0%
😁58.33%
custom 531910240235004874835.00%
👍35.00%
custom 530991941437885136411.67%
custom 532154833468550871211.67%

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 12 of the 18 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 60reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 11 March 2026 to 31 March 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

31 Mar 2026, 06:41 UTC109 views7 reactionsread 10 August 2026
Photo

Photo, posted without a caption

👍3custom 519084949057100088331

31 Mar 2026, 06:37 UTC106 views5 reactionsread 10 August 2026
Photo

Photo, posted without a caption

🔥31custom 51908494905710008831

15 Mar 2026, 15:13 UTC130 views6 reactionsread 10 August 2026
Photo

сделать вам скин на м416 и машину какую-то? 😁 Накидайте варианты, что сделать со Стичем 🤝

5custom 51908494905710008831

15 Mar 2026, 15:05 UTC100 views2 reactionsread 10 August 2026
Video

хочу коллабу со Стичем

1custom 51908494905710008831

15 Mar 2026, 10:12 UTC80 views9 reactionsread 10 August 2026
Video

это я выебываюсь перед тем как в лобби отлететь

😁5🔥3custom 53191024023500487481

14 Mar 2026, 18:05 UTC69 views5 reactionsread 10 August 2026
Video

«20:31. Прибыл Годжо Сатору»

3custom 53191024023500487482

14 Mar 2026, 07:04 UTC63 views8 reactionsread 10 August 2026
Photo

12UC 😭

6🔥1custom 53099194143788513641

13 Mar 2026, 19:20 UTC62 viewsread 10 August 2026
Video

такая стойка нас ждёт, в грядущей соло битве популярности 🥰

13 Mar 2026, 15:39 UTC67 views4 reactionsread 10 August 2026
Photo

эт че за жмых, нормальный?

4

13 Mar 2026, 10:13 UTC58 viewsread 10 August 2026
Photo

60 юси тому, кто мультик угадает

13 Mar 2026, 08:55 UTC56 viewsread 10 August 2026
Photo

приму в дар призовой путь потому что я очень «люблю АНИМЭ»

Showing the 12 most recent of 18 posts we hold for @johatsulive. 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 — 840,437 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.

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

“johatsu” (@johatsulive), 38 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/johatsulive.

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.