Telegram RegisterThe public register of Telegram
Telegram profile photo for JAPANESE ဇာတ်ကားစုံ

Channel

JAPANESE ဇာတ်ကားစုံ

@japanese6999

Has discussion group

On this record: Topic · Growth · Engagement · Citations · Cite this entry

50,573subscribers

-559 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1003589042071
TypeChannel
Username@japanese6999
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live18 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/japanese6999

Topic

Other / unclassifiable — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 86% 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

50,36851,15450,7617 August 2026 — 51,132 subscribers8 August 2026 — 51,075 subscribers9 August 2026 — 51,034 subscribers10 August 2026 — 51,068 subscribers11 August 2026 — 51,014 subscribers12 August 2026 — 51,014 subscribers12 August 2026 — 51,151 subscribers13 August 2026 — 51,154 subscribers14 August 2026 — 51,111 subscribers16 August 2026 — 50,964 subscribers17 August 2026 — 50,878 subscribers18 August 2026 — 50,870 subscribers19 August 2026 — 50,798 subscribers20 August 2026 — 50,725 subscribers22 August 2026 — 50,611 subscribers24 August 2026 — 50,492 subscribers25 August 2026 — 50,607 subscribers26 August 2026 — 50,649 subscribers27 August 2026 — 50,574 subscribers28 August 2026 — 50,502 subscribers29 August 2026 — 50,453 subscribers30 August 2026 — 50,368 subscribers31 August 2026 — 50,734 subscribers1 September 2026 — 50,857 subscribers2 September 2026 — 50,860 subscribers3 September 2026 — 50,886 subscribers5 September 2026 — 50,818 subscribers8 September 2026 — 50,676 subscribers11 September 2026 — 50,672 subscribers13 September 2026 — 50,686 subscribers14 September 2026 — 50,634 subscribers16 September 2026 — 50,608 subscribers18 September 2026 — 50,573 subscribers50,5737 August 202618 September 2026
33 measurements spanning 42 days, net -559. 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 50,250–51,272 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
18 Sept 2026, 19:1650,573-35
16 Sept 2026, 11:5750,608-26
14 Sept 2026, 14:0050,634-52
13 Sept 2026, 01:3950,686+14
11 Sept 2026, 05:1950,672-4
8 Sept 2026, 08:5650,676-142
5 Sept 2026, 06:4150,818-68
3 Sept 2026, 13:4250,886+26
2 Sept 2026, 07:0450,860+3
1 Sept 2026, 09:3550,857+123
31 Aug 2026, 07:2450,734+366
30 Aug 2026, 06:2750,368-85
29 Aug 2026, 05:3350,453-49
28 Aug 2026, 08:2950,502-72
27 Aug 2026, 06:2750,574-75
26 Aug 2026, 04:5950,649+42
25 Aug 2026, 04:3750,607+115
24 Aug 2026, 04:3750,492-119
22 Aug 2026, 09:2850,611-114
20 Aug 2026, 22:3750,725first reading

Engagement

No public post preview. We read this entry on 12 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Mentions

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

“JAPANESE ဇာတ်ကားစုံ” (@japanese6999), 50,573 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/japanese6999.

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.