聚隆高端今日上班女孩的相册二维码 👆 👆 👆
Channel
历城区聚隆高端
@julonggaoduan1
On this record: Growth · Engagement · Posts · Citations · Cite this entry
53subscribers
+8 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003442381737 |
|---|---|
| Type | Channel |
| Username | @julonggaoduan1 |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/julonggaoduan1 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 09:39 | 53 | +1 |
| 8 Sept 2026, 14:36 | 52 | +1 |
| 23 Aug 2026, 00:57 | 51 | +4 |
| 16 Aug 2026, 08:03 | 47 | +2 |
| 10 Aug 2026, 15:16 | 45 | no change |
| 8 Aug 2026, 11:17 | 45 | first reading |
Engagement
5 posts held, back to 14 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 5 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
#济南 #历城 #聚隆广场 05年舞蹈生 艺名 晴天 • 年龄 :21 • 身高 :175 体重 :95斤 • 胸围 :36B 安徽头牌 超火 南方女孩 舞蹈生 🉑一字马 超值 💰价格15张 •唯一客服 @Tanhuakefu1
#济南 #聚隆广场 07年妹子初下海 艺名 熙酱 • 年龄 :19 • 身高 :164 体重85斤 • 胸围 : 36C 第一次做这行 超粉嫩 抢先体验 💰价格 10张 •唯一客服 @Tanhuakefu1
#济南 #历城区 #聚隆高端 05年济南首开 艺名 噜噜 • 年龄 :21岁 • 身高 :165 体重90斤 • 胸围 :36B 纯欲天花板 短期兼职 💰价格15张 •唯一客服 @Tanhuakefu1
#济南 #历城 #聚隆广场 绝对超值 艺名 云妹 • 年龄 :23 • 身高 :165体重93斤 • 胸围 :36C 💰价格 15张 •唯一客服 @Tanhuakefu1
Showing the 5 most recent of 5 posts we hold for @julonggaoduan1. 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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“历城区聚隆高端” (@julonggaoduan1), 53 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/julonggaoduan1.
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.