Telegram RegisterThe public register of Telegram
Telegram profile photo for 日本AV|中文字幕|无码高清🔞

Channel

日本AV|中文字幕|无码高清🔞

@AVzwzimu

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

2,527subscribers

+2,493 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003950701286
TypeChannel
Username@AVzwzimu
CreatedBetween 1 April 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded5 October 2026
Last confirmed live16 November 2026
Measurements held20
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/AVzwzimu

Topic

Adult — 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 5 October 2026 and assigned it the closest of 31 fixed categories, at 100% 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 the other topics.

Growth

342,5271,280.56 August 2026 — 34 subscribers15 August 2026 — 44 subscribers23 August 2026 — 116 subscribers31 August 2026 — 733 subscribers8 September 2026 — 849 subscribers17 September 2026 — 953 subscribers3 October 2026 — 1,160 subscribers5 October 2026 — 1,160 subscribers9 October 2026 — 2,251 subscribers14 October 2026 — 2,290 subscribers17 October 2026 — 2,325 subscribers20 October 2026 — 2,362 subscribers23 October 2026 — 2,397 subscribers26 October 2026 — 2,423 subscribers29 October 2026 — 2,456 subscribers1 November 2026 — 2,473 subscribers4 November 2026 — 2,487 subscribers7 November 2026 — 2,495 subscribers10 November 2026 — 2,506 subscribers16 November 2026 — 2,527 subscribers6 August 202616 November 2026
20 measurements spanning 102 days, net +2,493. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Nov 2026, 13:442,527+21
10 Nov 2026, 21:042,506+11
7 Nov 2026, 01:392,495+8
4 Nov 2026, 00:112,487+14
1 Nov 2026, 06:502,473+17
29 Oct 2026, 05:482,456+33
26 Oct 2026, 04:262,423+26
23 Oct 2026, 01:272,397+35
20 Oct 2026, 01:372,362+37
17 Oct 2026, 01:082,325+35
14 Oct 2026, 04:182,290+39
9 Oct 2026, 15:012,251+1,091
5 Oct 2026, 04:361,160no change
3 Oct 2026, 06:411,160+207
17 Sept 2026, 16:01953+104
8 Sept 2026, 19:39849+116
31 Aug 2026, 11:55733+617
23 Aug 2026, 16:26116+72
15 Aug 2026, 06:5744+10
6 Aug 2026, 21:0434first 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.

Mentions

Named by 33 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. The 23 listed below are the most frequent namers; the rest are counted above but not each listed.

Named by

Channels on the register whose posts name this channel's handle.

韩国热舞直播
@nhvjjhg65586 · 200
2 posts
BBIN宝马会♣️CHOICE♣️欧博官网♣️亚星官网
@abg912 · 1,470
1 post
欧博私网🅾️亚星私网🅾️BBIN宝马会私网🅾️CHOICE私网
@agag503 · 1,274
1 post
环球360私网🅰️环球UG私网🅰️利博私网🅰️
@hgq3379 · 920
1 post
利博官网♣️万利官网♣️AG♣️PG♣️
@hqg56 · 1,285
1 post
利博官网高仿 万利官网高仿 BBIN宝马会官网高仿 CHOICE官网高仿
@hqg59 · 1,017
1 post
🅾️皇冠私网🅾️CHOICE私网🅾️环球UG私网🅾️环球360私网
@hqSM231 · 1,443
1 post
全国上门选妃服务
@hutwojsw · 1,277
1 post
Telegram频道订阅 频道推广 频道增粉
@jydffghhhh · 2,051
1 post
环球UG官网🥇环球360官网🥇皇冠官网🥇晨丽官网
@oubo558 · 1,011
1 post
欧博官网🥇亚星官网🥇环球UG官网🥇环球360官网
@oubo579 · 1,019
1 post
环球UG官网🥇环球360官网🥇SOLAIRE官网🥇利博官网
@oubo609 · 1,014
1 post
环球UG官网高仿 环球360官网高仿 欧博官网高仿 亚星官网高仿
@oubo7531 · 1,018
1 post
环球360私网🅰️欧博私网🅰️利博私网🅰️环球UG私网
@oubogf100 · 1,348
1 post
皇冠足球 皇冠代理 皇冠体育 皇冠官网 皇冠开户
@oubonj1 · 1,904
1 post
万利官网|环球官网UG|皇冠体育|AG
@tgch9f · 415
1 post
欧博官网|亚星官网|皇冠体育|AG|
@tgchfq13 · 438
1 post
缅甸果敢老街实体老牌赌场网投代理
@TL16868 · 4,477
1 post
网赌退款-AG百家乐-百家乐技巧-撸极速-出黑分-薅羊毛-上岸-网赌退米
@wdtk8811 · 7
1 post
泰国赌场-新加坡赌场-网络博彩
@yeshi1899 · 19
1 post
Telegram在线粉丝 活跃粉丝 在线会员
@yffhjjkjjjiio · 1,029
1 post
yuenanwaixiuche
@yuenanwaixiuche · 4
1 post
SunPorno熟女欲望
@zhenyanks · 375
1 post

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

“日本AV|中文字幕|无码高清🔞” (@AVzwzimu), 2,527 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/AVzwzimu.

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.