Telegram RegisterThe public register of Telegram
Telegram profile photo for 军人素材👮🏻‍军人男性套图👮🏻‍军人人物包装【@zhenni138珍妮💘素材】

Channel

军人素材👮🏻‍军人男性套图👮🏻‍军人人物包装【@zhenni138珍妮💘素材】

@Junren_renshe1

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

1,182subscribers

-165 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1003651426308
TypeChannel
Username@Junren_renshe1
CreatedBetween 1 December 2025 and 22 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live31 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 31 August 2026
On Telegramt.me/Junren_renshe1

Growth

1,1821,3471,264.513 August 2026 — 1,347 subscribers13 August 2026 — 1,343 subscribers17 August 2026 — 1,336 subscribers21 August 2026 — 1,332 subscribers24 August 2026 — 1,324 subscribers28 August 2026 — 1,294 subscribers31 August 2026 — 1,182 subscribers13 August 202631 August 2026
7 measurements spanning 18 days, net -165. 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 1,157–1,372 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 10:251,182-112
28 Aug 2026, 04:371,294-30
24 Aug 2026, 18:171,324-8
21 Aug 2026, 00:031,332-4
17 Aug 2026, 14:071,336-7
13 Aug 2026, 23:281,343-4
13 Aug 2026, 07:331,347first reading

Engagement

19 posts held, back to 22 May 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 19 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
13s
Average length
7s

Measured directly from 2 videos 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.

Recent posts

26 Jul 2026, 13:34 UTC21 viewsread 13 August 2026
Photo

(编号sg53) #国内 大学生男 中国人民公安大学 生化日常 自拍照 168张照片 #带博主ig

6 Jul 2026, 06:38 UTC52 viewsread 13 August 2026
Photo

编号 QQ394 #韩国 #军人 生活日常 生活场景丰富 健身 他拍多 旅游照多 军装照一张 曝光度低 粉丝2000+ 1459张照片 186个视频 (带IG)后期可更新

30 May 2026, 15:35 UTC63 viewsread 13 August 2026
Photo

(编号KK595) #新加坡 警察 日常 生活 旅游自拍595张照片视频65个

30 May 2026, 15:35 UTC53 viewsread 13 August 2026
Photo

(编号A124) #泰国 警察 日常 生活 旅游 健身1135张照片视频200个

30 May 2026, 15:35 UTC48 viewsread 13 August 2026
Photo

编号ZS197 生活日常🌟🌟🌟🌟 #泰国 职业 健身教练 肌肉 高尔夫 生活场景丰富 生活日常 旅游 风景 照片962张 视屏388个 (带IG)

30 May 2026, 15:35 UTC90 viewsread 13 August 2026
Photo

编号 P28 成熟男士 生活工作日常 自拍多 职业 #警察 爱健身 图片 180 张 视频 11 个 自拍视频2个 #国内 #有账号

30 May 2026, 15:35 UTC43 viewsread 13 August 2026
Photo

编号ZS196 生活日常🌟🌟🌟🌟 #国内 运动 网球 生活场景丰富 生活日常 旅游 风景 照片1623张 视屏211个 (带小红书)

30 May 2026, 15:35 UTC39 viewsread 13 August 2026
Photo

编号ZS195 生活日常🌟🌟🌟🌟 #台湾 职业 警察 正装 生活场景丰富 生活日常 旅游 风景 照片338张 视屏21个 (带IG)

30 May 2026, 15:35 UTC37 viewsread 13 August 2026
Photo

编号ZS284 生活日常🌟🌟🌟🌟 #新加坡 职业 警察 健身 自拍多 生活场景丰富 生活日常 旅游 风景 照片437张 视屏59个 (带IG)

30 May 2026, 15:35 UTC36 viewsread 13 August 2026
Photo

编号SS36 粉丝数量/曝光量:1W低 素材简介:#泰国 合适35至55岁人设 职业:警察 个人日常分享较全面 不同场景照片丰富 健身 秀身材 户外照 【图片415张 视频35个】 (带IG)

30 May 2026, 15:35 UTC37 views0 reactionsread 13 August 2026
Photo

编号 VX70 #台湾 警察 宝爸 生活场景丰富 自拍多 旅游 风景 生日照 美食 工作日常 带娃日常 曝光度低 粉丝1000+ 1441张照片 139个视频 (带IG)后期可更新

Showing the 12 most recent of 19 posts we hold for @Junren_renshe1. 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 2 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 31 August 2026 — this entry's latest reading, not the date you are reading this.

“军人素材👮🏻‍军人男性套图👮🏻‍军人人物包装【@zhenni138珍妮💘素材】” (@Junren_renshe1), 1,182 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/Junren_renshe1.

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.