Channel
@manualjapan
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
20subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003441364381 |
|---|---|
| Type | Channel |
| Username | @manualjapan |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 18 September 2026 |
| On Telegram | t.me/manualjapan |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 02:42 | 20 | -3 |
| 1 Sept 2026, 03:18 | 23 | +1 |
| 16 Aug 2026, 03:49 | 22 | +1 |
| 11 Aug 2026, 14:46 | 21 | no change |
| 7 Aug 2026, 11:32 | 21 | first reading |
20 posts held, back to 8 June 2026 — 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 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
41 reactions across 18 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🐳 | 41 | 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 18 of the 20 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 41 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 8 June 2026 to 7 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.
всем рекомендую! брал курс с полной предоплате всё прошло отлично. админ всегда на связи, отвечает на все вопросы и действительно помогает разобраться. очень много полезной информации, особенно для новичков. отдельный плюс большое количество контактов карго. курс однозначно стоит своих денег!
🐳1
Отличный мануал,заметил большое внимание мелочам,о которых новые ребята не знают.Очевидно стоит и оправдывает свои деньги
🐳2
Четкое обучение, стоит своих денег, все удобно структурировано
🐳1
стоит своих денег, реально годная тема, много полезной инфы и всякого другого, советую
🐳1
Обучение мясо 🔥🔥🔥 каждый день забираю топ Лут с площадок
🐳2
Чёткле обучение.Сделал всё бысро.
🐳2
Все круто, подробно расписано
🐳2
Очень классный мануал. Для старта в ресейле куча информации, рекомендую
🐳2
Крутой мануал, за свою цену много полезной информации
🐳2
Обучение топовое, очень много полезной информации для ресейла и большой плюс - чат со знающими людьми
Хорошее обучение, много инфы. Своих денег стоит
🐳2
прекрасное обучение.помогает, всем советую
🐳3
Showing the 12 most recent of 20 posts we hold for @manualjapan. 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.
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.
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 11 September 2026 — this entry's latest reading, not the date you are reading this.
“GlobalManual отзывы” (@manualjapan), 20 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/manualjapan.
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.