Channel
@japanese_clan
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
2subscribers
+0 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001649564107 |
|---|---|
| Type | Channel |
| Username | @japanese_clan |
| Description | наш любимый создатель: @lixmuw админ: @ufufjdh админ по союзам: @leeknowkd админ по нью: @alfredwilson админ по активу чата: @Niksa474 убедительная просьба создателю НЕ ПИСАТЬ. он вам всё равно никогда не ответит... |
| Created | Between 1 December 2021 and 12 June 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/japanese_clan |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 23:45 | 2 | no change |
| 14 Aug 2026, 23:32 | 2 | first reading |
17 posts held, back to 12 June 2022 — 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 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 13 June 2022. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 14 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.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 1 | 100.0% |
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 1 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 1 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 12 June 2022 to 13 June 2022, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
доброго времени суток. прошу прощение за такой не актив или не все репосты. в общем, я принял решение уйти с поста, как админа по союзами, так как на данный момент у меня не хватает времени на все репосты и мое здоровье ухудшилось. союзы все разрываются, прошу прощения ещё раз. спасибо вам❤ #JPCLrepost
👍1
Signed |рест| 리노. † 🇷🇺
@dedminop не добавляйте, больно агрессивный #репост_𝐁𝐄𝐋𝐈𝐙𝐀𝐑𝐃
Signed .
сегодня и завтра выходной от рп, всем приятных выходных! #репост_𝐁𝐄𝐋𝐈𝐙𝐀𝐑𝐃
Signed .
все союзы разрываются. канал закрывается. #𝐤𝐞𝐮𝐥𝐚𝐞𝐧𝐛𝐞𝐥𝐢_𝐫𝐩
Signed .
Что с вами? @empiretanner. Юз поменяли или закрылись? В любом случае жду до завтра. Свяжитесь со мной в лс @fvwkx. #翻訳肛門性交_repost
Signed .
сдаю кф славянам, без животных и детей, молодой паре!!!! #翻訳肛門性交_repost
Signed .
пр ребят у нас сегодня была лютейшая чистка, поэтому мы хотим новеньких активных челиков в нашем прекрасном коллективе. пишите, не стесняйтесь котеки @sullily #翻訳肛門性交_repost
Signed .
Сегодня рп от меня (@fvwkx) не будет. Завтра сделаю за два дня. #翻訳肛門性交_repost
Signed .
ребят у нас в кф много девочек которые ищут себе сп го к нам #翻訳肛門性交_repost
Signed .
рп от меня @sullily завтра, личные причины #翻訳肛門性交_repost
Signed .
дорогие союзники, если ваш клан/кф/семья планирует закрыться на летнее время или я вообще не ебу по каким еще причинам, то пожалуйста, предупреждайте НОРМАЛЬНО. вы думаете у нас нет никаких дел, помимо того, чтобы искать юзеры админов, с которыми был заключен союз и юзеры каналов? молча отписаться и удалить канал - глупо. так вот, если у вас в планах закрыться в ближайшее время, то напишите либо админам, либо в комм…
Signed .
Что с вами @empiretanner? Юз поменяли? Свяжитесь со мной в лс, жду до понедельника. @fvwkx #翻訳肛門性交_repost
Signed .
Showing the 12 most recent of 17 posts we hold for @japanese_clan. 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.
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.
Named by 2 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.
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.
@japanese_clan named 4 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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“𝙅𝘼𝙋𝘼𝙉𝙀𝙎𝙀 𝘾𝙇𝘼𝙉” (@japanese_clan), 2 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/japanese_clan.
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.