Telegram RegisterThe public register of Telegram
Telegram profile photo for 萝莉🧑‍🎓 @j3ppp

Channel

萝莉🧑‍🎓 @j3ppp

@j3pppllxs

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

3subscribers

+1 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1004413253653
TypeChannel
Username@j3pppllxs
CreatedBetween 1 June 2026 and 29 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live11 October 2026
Measurements held3
Confirmed unchanged2 times, most recently 11 October 2026
On Telegramt.me/j3pppllxs

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 3 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 why it has no browse page of its own yet.

Growth

232.513 August 2026 — 2 subscribers14 August 2026 — 2 subscribers30 September 2026 — 3 subscribers13 August 202630 September 2026
3 measurements spanning 48 days, net +1. 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 2–3 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Sept 2026, 19:373+1
14 Aug 2026, 07:482no change
13 Aug 2026, 14:472first reading

Engagement

10 posts held, back to 29 July 2026 — the 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 10 posts for this entry, the most recent from 29 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
4h 24m
Average length
26m 30s

Measured directly from 10 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

29 Jul 2026, 20:56 UTC30 viewsread 14 August 2026
Video

推特极品婴儿肥白嫩福利姬【小水水】犯错的实习生用蜜穴留在公司的技巧

29 Jul 2026, 20:56 UTC30 viewsread 14 August 2026
Video

网红反差女神【唐可可】【可爱萝莉】毕业洗礼之白丝“穴”生肉体侍奉

29 Jul 2026, 20:56 UTC29 viewsread 14 August 2026
Video

糖心探花大神【91渣男】超级反差三好学生,诉说自己在白天是学校的焦点人物,晚上出来任人摆布的心酸旅程

29 Jul 2026, 20:56 UTC28 viewsread 14 August 2026
Video

糖心网黄UP主『柚子』断电偷情夜:大屌的诱惑 颜射护肤

29 Jul 2026, 20:56 UTC24 viewsread 14 August 2026
Video

糖心网红UP主『糖心官方君』超美娇嫩萝莉 双马尾JK 过膝白丝 真的是太纯欲了 被各种姿势抓着娇嫩奶子猛干 颜值超高

29 Jul 2026, 20:56 UTC22 viewsread 14 August 2026
Video

网红福利UP主【小野整活部】女友是犯了多大错啊!后入干到腿软,藤条抽屁股求饶越打越狠,踩着头后入简直不当人啊

29 Jul 2026, 20:55 UTC21 viewsread 14 August 2026
Video

网红反差女神【粉色情人】被学姐极品身材榨干最后一滴精液

29 Jul 2026, 20:55 UTC20 viewsread 14 August 2026
Video

推特极品婴儿肥白嫩福利姬【小水水】特殊的加练既然锻炼不达标那就只能用嫩穴来帮助你加练了

29 Jul 2026, 20:55 UTC19 viewsread 14 August 2026
Video

推特网红嫩妹【懒懒猪】为求转正被潜规则 实习生被老板操哭

29 Jul 2026, 20:55 UTC19 viewsread 14 August 2026
Video

网红福利UP主【小野整活部】【完美身材女神!简直是从漫画里走出来的】这极致的身材比例太极品了,而且小穴还这么嫩,第一次射完没爽自己自慰,男主看到后又硬起来搞第二发

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

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

“萝莉🧑‍🎓 @j3ppp” (@j3pppllxs), 3 subscribers as measured 30 September 2026. Telegram Register, tgregister.com/channel/j3pppllxs.

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.