
Channel
Learning Japanese from zero
@japaneseresources
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,843subscribers
+127 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001081609866 |
|---|---|
| Type | Channel |
| Username | @japaneseresources |
| Created | Between 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 29 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/japaneseresources |
Topic
Education — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 99% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 02:58 | 5,843 | +1 |
| 11 Sept 2026, 08:16 | 5,842 | +12 |
| 6 Sept 2026, 15:39 | 5,830 | +15 |
| 2 Sept 2026, 11:33 | 5,815 | +1 |
| 30 Aug 2026, 14:44 | 5,814 | +9 |
| 29 Aug 2026, 22:58 | 5,805 | no change |
| 27 Aug 2026, 18:24 | 5,805 | +6 |
| 24 Aug 2026, 13:53 | 5,799 | +21 |
| 21 Aug 2026, 05:46 | 5,778 | +21 |
| 18 Aug 2026, 09:03 | 5,757 | +10 |
| 15 Aug 2026, 00:06 | 5,747 | +15 |
| 11 Aug 2026, 20:53 | 5,732 | +7 |
| 9 Aug 2026, 06:43 | 5,725 | +9 |
| 6 Aug 2026, 00:19 | 5,716 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@Learn_Japanese · 29,005
Telegram ranks this channel #2 of 67 here — alongside 66 others — read 9 September 2026
@japanesefreedashboard · 25,024
Telegram ranks this channel #7 of 83 here — alongside 82 others — read 15 September 2026
@zawyenaing54 · 26,442
Telegram ranks this channel #33 of 56 here — alongside 55 others — read 12 September 2026
@mrmostafaawad · 106,991
Telegram ranks this channel #46 of 74 here — alongside 73 others — read 17 August 2026
@wildlifechannal · 31,397
Telegram ranks this channel #58 of 60 here — alongside 59 others — read 6 September 2026
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“Learning Japanese from zero” (@japaneseresources), 5,843 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/japaneseresources.
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.