Telegram RegisterThe public register of Telegram
Telegram profile photo for 关于 mokeyjay

Channel

关于 mokeyjay

@about_mokeyjay

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

21subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001171736272
TypeChannel
Username@about_mokeyjay
Created9 November 2019measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live16 August 2026
Measurements held2
On Telegramt.me/about_mokeyjay

Growth

217 August 2026 — 21 subscribers11 August 2026 — 21 subscribers7 August 202611 August 2026
2 measurements spanning 4 days. 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 20–22 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 15:0221no change
7 Aug 2026, 20:0421first reading

Engagement

4 posts held, back to 9 November 2019the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 4 posts for this entry, the most recent from 24 January 2020. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
1

Lifetime counters from Telegram’s own channel header, read 11 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.

Recent posts

9 Nov 2019, 13:32 UTC714 viewsread 11 August 2026

你可以叫我小紫、mok 或者 猴子 频道主 @mokeyjay 日常频道 @mokeyjay_channel 普通插画收藏夹 @mokeyjay_illustration R18插画收藏夹 @mokeyjay_r18_illustration 照片收藏夹 @mokeyjay_photo 甜品日记 @mokeyjay_dessert 讨论群组: https://t.me/+Gwhvp_11RGk4YjEx 博客: https://mok.moe 微博: https://weibo.com/mokeyjay 推特: https://twitter.com/ttmokeyjay 邮箱: [email protected] 二次元壁纸包: https://mok.moe/p/acg-wallpaper 更多关于我的介绍:https://mok.moe/about

Showing the 4 most recent of 4 posts we hold for @about_mokeyjay. 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.

Mentions

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

“关于 mokeyjay” (@about_mokeyjay), 21 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/about_mokeyjay.

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.