😢NFT @tg1413
Channel
@fj4444
@FJ4444
On this record: Growth · Engagement · Posts · Citations · Cite this entry
1subscribers
-1 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002392634712 |
|---|---|
| Type | Channel |
| Usernames | @FJ4444 @kk11111 @leisao @lj9999 @tg1413 @ttcctt @wengdi @wwiiww |
| Created | 22 December 2024 — measured — dated from the channel’s first post |
| First recorded | 14 August 2026 |
| Last confirmed live | 4 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 12 times, most recently 4 September 2026 |
| On Telegram | t.me/FJ4444 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 18:54 | 1 | no change |
| 21 Aug 2026, 13:36 | 1 | no change |
| 21 Aug 2026, 12:58 | 1 | no change |
| 21 Aug 2026, 06:33 | 1 | no change |
| 21 Aug 2026, 01:47 | 1 | no change |
| 21 Aug 2026, 00:15 | 1 | no change |
| 20 Aug 2026, 19:24 | 1 | no change |
| 19 Aug 2026, 05:14 | 1 | -1 |
| 14 Aug 2026, 06:34 | 2 | no change |
| 14 Aug 2026, 01:19 | 2 | no change |
| 13 Aug 2026, 21:15 | 2 | no change |
| 13 Aug 2026, 10:03 | 2 | no change |
| 12 Aug 2026, 04:17 | 2 | first reading |
Engagement
18 posts held, back to 22 December 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 8 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 400.0%
- avg views ÷ 1 subscribers
- Avg views / post
- 4.0
- 2 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 2
- of 18 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 18 (22 December 2024 – 12 August 2026) |
| Views total | 8 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Aug 2026, 06:34 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Recent posts
😢NFT @ttcctt
😢NFT @wwiiww
😢NFT @kk11111
https://fragment.com/username/@kk11111 😢NFT @kk11111
😢NFT @pisao 皮嫂 屁骚 😢NFT @duisao 兑扫 对骚 😢NFT @luesao 略骚 😢NFT @wensao 文嫂 文骚 😢NFT @miaosao 苗嫂 秒扫 秒骚 😢NFT @leisao 雷嫂 😢NFT @kuosao 阔嫂 😢NFT @kuangsao 狂骚 狂扫 😢NFT @qingsao 清扫 情骚 庆嫂 😢NFT @qiaosao 俏嫂 巧嫂 翘骚 😢NFT @niangsao 娘骚 😢NFT @chasao 查扫 叉骚
https://fragment.com/username/@leisao 😢NFT @leisao 雷嫂
😢NFT @leisao 雷嫂
😢NFT @wengdi 翁帝
https://fragment.com/username/@wengdi 😢NFT @wengdi 翁帝
😢NFT @lj9999
https://fragment.com/username/@lj9999 😢NFT @lj9999
Showing the 12 most recent of 18 posts we hold for @FJ4444. 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
Named by 65 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 24 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.
@chasao1 · 32 postsNFT @dishang 帝商 迪尚
@dishang · 22 posts@kuangsao 狂骚
@kuangsao1 · 32 postsNFT @kuosao 阔嫂
@kuosaobot · 22 postsNFT @luesao 略骚
@luesao1 · 22 posts苗嫂 秒扫 秒骚
@miaosaobot · 22 posts@niangsao 娘骚
@niangsao · 12 postsNFT @qingsao 情骚
@qingsao1 · 22 posts@qiongshang 琼商
@qiongshang · 22 posts文嫂 文骚 纹骚
@wensao1 · 42 postsNFT @zhuangdi 庄帝
@zhuangdi1 · 32 posts@zuodi 左帝 佐迪
@zuodi1 · 22 postsNFT @zuolo 左咯
@zuolobot · 22 postsNFT @cangchen 仓辰
@cangchen · 21 postNFT @chengtai 𫍯泰
@chengtai · 31 postNFT @diansuo 电锁
@diansuo · 11 postNFT @dongqie 董惬
@dongqie · 11 postNFT @kangfei 康飞
@kangfei · 21 postNFT @kanniao 看鸟
@kanniao · 11 postNFT @kuojun 扩军
@kuojun1 · 41 postNFT @panzheng 盘整 潘正
@panzheng1 · 31 postnaiqiu奶球saonai骚奶
@qiaosao · 151 post@shangliao 上料
@shangliao1 · 21 post@tuoling 驼铃
@tuoling1 · 21 post
Names
Channels on the register whose handles appear in this channel's posts.
@chasao1 · 32 postsNFT @duisao 兑扫 对骚
@duisaobot · 42 posts@kuangsao 狂骚
@kuangsao1 · 32 postsNFT @kuosao 阔嫂
@kuosaobot · 22 postsNFT @luesao 略骚
@luesao1 · 22 posts苗嫂 秒扫 秒骚
@miaosaobot · 22 posts@niangsao 娘骚
@niangsao · 12 postsNFT @pisao 皮嫂 屁骚
@pisaobot · 62 postsnaiqiu奶球saonai骚奶
@qiaosao · 152 postsNFT @qingsao 情骚
@qingsao1 · 22 posts骚名用户名NFT任选🆔
@tg8tg · 2992 posts文嫂 文骚 纹骚
@wensao1 · 42 posts@congzheng 从政
@congzheng1 · 21 postNFT @dangyong 当勇
@dangyong1 · 31 postNFT @diaoyang 屌样
@diaoyang1 · 21 postNFT @kangxun 康讯
@kangxunbot · 21 postNFT @kuojun 扩军
@kuojun1 · 41 post屈晴 趣情
@quqing_bot · 21 postNFT @saoqiu 骚球
@saoqiu1 · 41 postNFT @shaohen 烧痕 稍狠
@shaohen · 41 postNFT @shaosao 烧骚
@shaosao_bot · 31 post@tuoling 驼铃
@tuoling1 · 21 post@zhaofen 找粉
@zhaofen1 · 41 postNFT @zhuangdi 庄帝
@zhuangdi1 · 31 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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“@fj4444” (@FJ4444), 1 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/FJ4444.
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.