Telegram RegisterThe public register of Telegram
Telegram profile photo for 夜玖源码分享

Channel

夜玖源码分享

@YJYMFX

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

3,998subscribers

+240 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002714629108
TypeChannel
Username@YJYMFX
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live3 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 3 September 2026
On Telegramt.me/YJYMFX

Growth

3,7583,9983,8788 August 2026 — 3,758 subscribers8 August 2026 — 3,758 subscribers8 August 2026 — 3,760 subscribers12 August 2026 — 3,778 subscribers15 August 2026 — 3,822 subscribers18 August 2026 — 3,848 subscribers20 August 2026 — 3,884 subscribers24 August 2026 — 3,915 subscribers27 August 2026 — 3,943 subscribers30 August 2026 — 3,982 subscribers3 September 2026 — 3,998 subscribers8 August 20263 September 2026
11 measurements spanning 25 days, net +240. 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 3,722–4,034 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Sept 2026, 00:083,998+16
30 Aug 2026, 14:153,982+39
27 Aug 2026, 12:083,943+28
24 Aug 2026, 20:173,915+31
20 Aug 2026, 21:453,884+36
18 Aug 2026, 05:523,848+26
15 Aug 2026, 16:253,822+44
12 Aug 2026, 02:323,778+18
8 Aug 2026, 20:553,760+2
8 Aug 2026, 18:303,758no change
8 Aug 2026, 18:173,758first reading

Engagement

20 posts held, back to 29 July 2026the 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 8 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
39s
Average length
39s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

60 reactions across 19 posts, in 2 distinct kinds. The most used accounts for 90.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍5490.0%
🤔610.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 19 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 60 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 29 July 2026 to 8 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.

Recent posts

8 Aug 2026, 14:34 UTC182 views4 reactionsread 8 August 2026
Video

我的模型好看吗🤓

👍4

Signed 上杉绘梨衣

7 Aug 2026, 12:36 UTC409 views2 reactionsread 8 August 2026
Forwarded from @BYBX666File

Caesar内核ui.zip

👍2

Signed 上杉绘梨衣

7 Aug 2026, 03:11 UTC541 views1 reactionsread 8 August 2026

破14k免费泛滥😁

👍1

Signed 上杉绘梨衣

7 Aug 2026, 03:11 UTC538 views2 reactionsread 8 August 2026

频道破14k泛滥10G源码 https://t.me/BYBX666

👍2

Signed 上杉绘梨衣

7 Aug 2026, 02:59 UTC544 views3 reactionsread 8 August 2026
Photo

出售此UI要的联系 @Qingxue866

👍3

Signed 上杉绘梨衣

6 Aug 2026, 12:05 UTC808 views8 reactionsread 8 August 2026
File

密码 台独狗死全家

👍8

Signed 上杉绘梨衣

6 Aug 2026, 07:50 UTC667 views4 reactionsread 8 August 2026
Photo

出售此源码联系 @Qingxue866

👍4

Signed 上杉绘梨衣

5 Aug 2026, 09:57 UTC731 views2 reactionsread 8 August 2026
Forwarded from @GMNB8File

修复频道跳转错误

👍2

Signed 上杉绘梨衣

5 Aug 2026, 04:15 UTC739 viewsread 8 August 2026
Forwarded from @GMNB8File

更新1.30.26805版本 ①部分内容分开减少单个文件体积 ②对接socket输入法 ③修复ui上的自瞄类xy调节相反 ④修复屏幕旋转后自瞄相反

Signed 上杉绘梨衣

4 Aug 2026, 01:17 UTC883 views2 reactionsread 8 August 2026
Forwarded from @BYBX666File

泛滥频道 https://t.me/BYBX666

👍2

Signed 上杉绘梨衣

Showing the 12 most recent of 20 posts we hold for @YJYMFX. 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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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 1 registered channel — 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.

Names

Channels on the register whose handles appear in this channel's posts.

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

“夜玖源码分享” (@YJYMFX), 3,998 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/YJYMFX.

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.