Telegram RegisterThe public register of Telegram
Telegram profile photo for 青楼 港珠澳花魁榜 @qlql

Channel

青楼 港珠澳花魁榜 @qlql

@qlqlfs

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

7,230subscribers

+502 since we began measuring on 2 September 2026

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

Register entry

Telegram ID-1001439627974
TypeChannel
Username@qlqlfs
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded2 September 2026
Last confirmed live11 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/qlqlfs

Growth

6,7277,2306,978.52 September 2026 — 6,728 subscribers2 September 2026 — 6,728 subscribers7 September 2026 — 6,727 subscribers11 September 2026 — 7,230 subscribers2 September 202611 September 2026
4 measurements spanning 10 days, net +502. 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 6,652–7,305 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 19:177,230+503
7 Sept 2026, 14:176,727-1
2 Sept 2026, 02:006,728no change
2 Sept 2026, 01:456,728first reading

Engagement

13 posts held, back to 25 August 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.

ERR · 30 days
10.0%
avg views ÷ 7,230 subscribers
Avg views / post
725
12 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
13
of 13 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 1 September 2026
Posts held13 (25 August 20261 September 2026)
Views total8,705
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Sept 2026, 02:00 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.

What this channel posts

Video runtime
2s
Average length
2s

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.

Recent posts

1 Sept 2026, 19:38 UTC1 viewsread 2 September 2026

🎟 抽奖标题: 青楼娱乐会员活动 中奖者联系 @qlql 领取会员 消耗积分: 100 积分 满人开奖满99人 参与关键词: 月上柳梢头,相约到青楼 已参与: 0人 🎁 奖品列表: TG会员一个月 X 999 参与要求: ➕加入 - 青楼 全球总部交流群 @qlql └ 💬 发言数大于 100 条 ➕加入 - 青楼 广佛花魁榜 @qlql ➕加入 - 青楼 深莞惠花魁榜 @qlql ➕加入 - 青楼 港珠澳花魁榜 @qlql

Signed 柳如烟

1 Sept 2026, 12:15 UTC1 viewsread 2 September 2026

#频道互推 #相似推荐 ------------------------------ 📢 天津烟雨楼 📢 广州~粤苑 📢 裸聊自慰直播网红 📢 珠海#澳门#深圳95T4 📢 深圳无忧修车 📢 裸聊直播自慰 📢 郑州紫儿 📢 佳佳1v1视频陪聊(可验证) 📢 青楼 昆明花魁榜 @qlql 📢 青楼 石家庄花魁榜 @qlql ------------------------------ ☁️ 互推入口:@sooo

Signed 极搜🔍中文搜索@JISO

1 Sept 2026, 08:12 UTC2 viewsread 2 September 2026
Photo

青楼花魁地区导航 点击下方开始探花

Signed 青楼 · 同城探花@qlql

31 Aug 2026, 08:12 UTC4 viewsread 2 September 2026
Photo

青楼花魁地区导航 点击下方开始探花

Signed 青楼 · 同城探花@qlql

30 Aug 2026, 08:12 UTC3 viewsread 2 September 2026
Photo

青楼花魁地区导航 点击下方开始探花

Signed 青楼 · 同城探花@qlql

29 Aug 2026, 08:12 UTC3 viewsread 2 September 2026
Photo

青楼花魁地区导航 点击下方开始探花

Signed 青楼 · 同城探花@qlql

28 Aug 2026, 08:12 UTC4 viewsread 2 September 2026
Photo

青楼花魁地区导航 点击下方开始探花

Signed 青楼 · 同城探花@qlql

27 Aug 2026, 08:12 UTC7 viewsread 2 September 2026
Photo

青楼花魁地区导航 点击下方开始探花

Signed 青楼 · 同城探花@qlql

26 Aug 2026, 08:12 UTC≈2,170 viewsread 2 September 2026
Photo

青楼花魁地区导航 点击下方开始探花

Signed 青楼 · 寻花问柳@qlql

25 Aug 2026, 15:22 UTC≈2,170 viewsread 2 September 2026

🤫🤫🤫🤫🤫🤫🤫🤫🤫🤫 珠海(第二页) 😮琳儿😮雪梨😮桐桐😮 😮依诺😮糖果😮张雪😮 😮筱蔓儿

25 Aug 2026, 14:59 UTCviews —

青楼 港珠澳花魁榜 @qlql pinned «🤫🤫🤫🤫🤫🤫🤫🤫🤫🤫 香港 😮»

25 Aug 2026, 14:57 UTC≈2,170 viewsread 2 September 2026
Photo

😮艺名: 露露 😮位置: 中山 😮学费: 800p 😮类型:😃😃 😮电报: @luluya45 😮频道:t.me/xiayu4288 😮验证方式:😀😀😀😀😀

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

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

“青楼 港珠澳花魁榜 @qlql” (@qlqlfs), 7,230 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/qlqlfs.

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.